Searched full:panics (Results 1 – 25 of 116) sorted by relevance
12345
| /kernel/linux/linux-6.6/rust/kernel/sync/ |
| D | locked_by.rs | 17 /// when the caller shows evidence that the 'external' lock is locked. It panics if the evidence
118 /// # Panics
120 /// Panics if `owner` is different from the data protected by the lock used in
150 /// # Panics
152 /// Panics if `owner` is different from the data protected by the lock used in
|
| /kernel/linux/linux-6.6/rust/alloc/ |
| D | raw_vec.rs | 38 /// * Catches all overflows in capacity computations (promotes them to "capacity overflow" panics).
83 /// # Panics
85 /// Panics if the requested capacity exceeds `isize::MAX` bytes.
302 /// # Panics
304 /// Panics if the new capacity exceeds `isize::MAX` bytes.
363 /// # Panics
365 /// Panics if the new capacity exceeds `isize::MAX` bytes.
387 /// # Panics
389 /// Panics if the given amount is *larger* than the current capacity.
569 // ensure that the code generation related to these panics is minimal as there's
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.txt | 4 ramoops provides persistent RAM storage for oops and panics, so they can be
49 (defaults to 2: log Oopses and Panics). This can be set to INT_MAX to
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | ramoops.rst | 12 crashes. It works by logging oopses and panics in a circular buffer. Ramoops
42 ``enum kmsg_dump_reason``. For example, to store both Oopses and Panics,
43 ``max_reason`` should be set to 2 (KMSG_DUMP_OOPS), to store only Panics
|
| D | pstore-blk.rst | 147 ``enum kmsg_dump_reason``. For example, to store both Oopses and Panics,
148 ``max_reason`` should be set to 2 (KMSG_DUMP_OOPS), to store only Panics
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | ramoops.rst | 12 crashes. It works by logging oopses and panics in a circular buffer. Ramoops
40 ``enum kmsg_dump_reason``. For example, to store both Oopses and Panics,
41 ``max_reason`` should be set to 2 (KMSG_DUMP_OOPS), to store only Panics
|
| D | pstore-blk.rst | 144 ``enum kmsg_dump_reason``. For example, to store both Oopses and Panics,
145 ``max_reason`` should be set to 2 (KMSG_DUMP_OOPS), to store only Panics
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 10 ramoops provides persistent RAM storage for oops and panics, so they can be
78 default: 2 # log oopses and panics
|
| /kernel/linux/linux-6.6/rust/alloc/vec/ |
| D | mod.rs | 447 /// # Panics
449 /// Panics if the new capacity exceeds `isize::MAX` bytes.
690 /// # Panics
692 /// Panics if the new capacity exceeds `isize::MAX` bytes.
1013 /// # Panics
1015 /// Panics if the new capacity exceeds `isize::MAX` bytes.
1043 /// # Panics
1045 /// Panics if the new capacity exceeds `isize::MAX` bytes.
1278 // were to panic once (if it panics twice, the program aborts). in truncate()
1496 /// # Panics
[all …]
|
| D | extract_if.rs | 70 // is updated prior and the predicate panics, the element at this in next()
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/misc/ |
| D | pvpanic-mmio.txt | 15 * Bytes 0x0 Write panic event to the reg when guest OS panics.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/misc/ |
| D | pvpanic-mmio.txt | 15 * Bytes 0x0 Write panic event to the reg when guest OS panics.
|
| /kernel/linux/linux-6.6/arch/loongarch/ |
| D | Kconfig.debug | 6 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
|
| /kernel/linux/linux-5.10/arch/loongarch/ |
| D | Kconfig.debug | 6 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
|
| /kernel/linux/linux-6.6/rust/ |
| D | build_error.rs | 22 /// Panics if executed in [const context][const-context], or triggers a build error if not.
|
| /kernel/linux/linux-6.6/fs/btrfs/ |
| D | Kconfig | 97 Enable run-time assertion checking. This will result in panics if
|
| /kernel/linux/linux-5.10/fs/btrfs/ |
| D | Kconfig | 96 Enable run-time assertion checking. This will result in panics if
|
| /kernel/linux/linux-6.6/fs/xfs/ |
| D | xfs_sysctl.h | 53 * xfs_panic_mask bit 0x8 turns the error reports into panics
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | xfs_sysctl.h | 54 * xfs_panic_mask bit 0x8 turns the error reports into panics
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/rust/ |
| D | coding-guidelines.rst | 139 - 虽然这里没有显示，但如果一个函数可能会恐慌，那么必须在 ``# Panics`` 部分描述发
|
| /kernel/linux/linux-5.10/drivers/mtd/ |
| D | mtdoops.c | 41 "set to 1 to dump oopses, 0 to only dump panics (default 1)");
283 /* Panics must be written immediately */ in mtdoops_do_dump()
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | amu.rst | 71 firmware the user may experience panics or lockups when accessing the
|
| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | amu.rst | 71 firmware the user may experience panics or lockups when accessing the
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/vc4/ |
| D | vc4_hvs.c | 960 * VC4 panics when < 2 lines in FIFO. in vc4_hvs_bind()
961 * VC5 panics when less than 1 line in the FIFO. in vc4_hvs_bind()
971 * VC4 panics when < 2 lines in FIFO. in vc4_hvs_bind()
972 * VC5 panics when less than 1 line in the FIFO. in vc4_hvs_bind()
|
| /kernel/linux/linux-6.6/drivers/mtd/ |
| D | mtdoops.c | 41 "set to 1 to dump oopses, 0 to only dump panics (default 1)");
321 /* Panics must be written immediately */ in mtdoops_do_dump()
|
12345