/openbmc/linux/rust/kernel/sync/ |
H A 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
|
/openbmc/linux/rust/alloc/ |
H A 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 …]
|
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-kernel/linux/linux-nuvoton/ |
H A D | gbs.cfg | 34 # Blink BMC fault when kernel panics 39 # Enable pstore(ramoops) to capture kernel panics
|
/openbmc/linux/Documentation/admin-guide/ |
H A 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
|
H A 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
|
/openbmc/linux/Documentation/devicetree/bindings/reserved-memory/ |
H A D | ramoops.yaml | 10 ramoops provides persistent RAM storage for oops and panics, so they can be 78 default: 2 # log oopses and panics
|
/openbmc/linux/rust/alloc/vec/ |
H A 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 …]
|
H A D | extract_if.rs | 70 // is updated prior and the predicate panics, the element at this in next()
|
/openbmc/linux/Documentation/devicetree/bindings/misc/ |
H A D | pvpanic-mmio.txt | 15 * Bytes 0x0 Write panic event to the reg when guest OS panics.
|
/openbmc/linux/arch/loongarch/ |
H A D | Kconfig.debug | 6 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
|
/openbmc/openbmc/meta-security/recipes-security/krill/files/ |
H A D | panic_workaround.patch | 9 # Make sure that Krill crashes on panics, rather than losing threads and
|
/openbmc/linux/rust/ |
H A D | build_error.rs | 22 /// Panics if executed in [const context][const-context], or triggers a build error if not.
|
/openbmc/linux/fs/btrfs/ |
H A D | Kconfig | 97 Enable run-time assertion checking. This will result in panics if
|
/openbmc/linux/fs/xfs/ |
H A D | xfs_sysctl.h | 53 * xfs_panic_mask bit 0x8 turns the error reports into panics
|
/openbmc/qemu/hw/i2c/ |
H A D | microbit_i2c.c | 7 * accelerometer/magnetometer on startup and panics if they are not found.
|
/openbmc/linux/Documentation/translations/zh_CN/rust/ |
H A D | coding-guidelines.rst | 139 - 虽然这里没有显示,但如果一个函数可能会恐慌,那么必须在 ``# Panics`` 部分描述发
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | amu.rst | 71 firmware the user may experience panics or lockups when accessing the
|
/openbmc/linux/drivers/gpu/drm/vc4/ |
H A 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()
|
/openbmc/linux/drivers/mtd/ |
H A 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()
|
/openbmc/linux/arch/mips/bmips/ |
H A D | setup.c | 110 * RAC flush causes kernel panics on BCM6358 when booting from TP1 in bcm6358_quirks()
|
/openbmc/linux/arch/x86/ |
H A D | Kconfig.debug | 230 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
|
/openbmc/linux/Documentation/rust/ |
H A D | coding-guidelines.rst | 155 that happens must be described under a ``# Panics`` section.
|
/openbmc/docs/designs/ |
H A D | bmc-service-failure-debug-and-recovery.md | 138 Crash conditions in the Linux kernel trigger panics, which are handled by kdump 140 lockup conditions can be configured to trigger panics, which in-turn trigger
|
/openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
H A D | sysrq.rst | 156 控制台。(比如 ``0`` ,将使得只有紧急信息,像 PANICs or OOPSes
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | kasan.rst | 101 When it is enabled, KASAN panics the kernel after printing a bug report. 114 Hardware Tag-Based KASAN, ``kasan.fault=panic_on_write`` always panics on
|