/openbmc/linux/kernel/debug/kdb/ |
H A D | kdb_debugger.c | 123 KDB_FLAG_SET(CATASTROPHIC); in kdb_stub() 125 /* set CATASTROPHIC if the system contains unresponsive processors */ in kdb_stub() 128 KDB_FLAG_SET(CATASTROPHIC); in kdb_stub() 155 KDB_FLAG_CLEAR(CATASTROPHIC); in kdb_stub()
|
/openbmc/linux/lib/ |
H A D | Kconfig.kgdb | 130 int "KDB: continue after catastrophic errors" 135 catastrophic error, i.e. for a panic or oops. 136 When KDB is active and a catastrophic error occurs, nothing extra
|
/openbmc/linux/drivers/infiniband/hw/mthca/ |
H A D | mthca_catas.c | 57 MODULE_PARM_DESC(catas_reset_disable, "disable reset on catastrophic event if nonzero"); 119 mthca_err(dev, "Catastrophic error detected: %s\n", type); in handle_catas() 161 mthca_warn(dev, "couldn't map catastrophic error region " in mthca_start_catas_poll()
|
/openbmc/linux/drivers/thermal/intel/ |
H A D | intel_quark_dts_thermal.c | 94 /* Quark DTS has 2 trip points: hot & catastrophic */ 192 * fields for critical (catastrophic) and hot set trip point in get_trip_temp() 232 * fields for critical (catastrophic) and hot set trip point in update_trip_temp()
|
H A D | intel_pch_thermal.c | 41 #define WPT_CTT 0x0010 /* Catastrophic Trip Point */ 54 #define WPT_TSC_CPDE 0x01 /* Catastrophic Power-Down Enable */
|
/openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
H A D | qcom,dcc.yaml | 14 configuration data or system memory contents during catastrophic failure
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | mlx4.rst | 52 value on the catastrophic buffer, a snapshot will be taken by the driver.
|
/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | platform_message_registry.hpp | 42 "Indicates the operating system was halted due to a catastrophic error.",
|
/openbmc/u-boot/arch/x86/cpu/quark/ |
H A D | quark.c | 189 /* thermal monitor catastrophic trip set point (105 celsius) */ in quark_thermal_early_init() 192 /* thermal monitor catastrophic trip clear point (0 celsius) */ in quark_thermal_early_init()
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-kernel-iommu_groups | 62 system could lead to catastrophic effects (the users might
|
/openbmc/linux/fs/xfs/ |
H A D | xfs_drain.h | 44 * this results in incorrect repairs, which is catastrophic.
|
/openbmc/linux/arch/m68k/fpsp040/ |
H A D | scale.S | 162 | The result exponent is below denorm value. Test for catastrophic 168 blt fix_unfl |if lower, catastrophic unfl
|
/openbmc/qemu/tests/qemu-iotests/tests/ |
H A D | file-io-error | 4 # Produce an I/O error in file-posix, and hope that it is not catastrophic.
|
/openbmc/qemu/tests/tcg/hexagon/ |
H A D | reg_mut.c | 87 * should cause a catastrophic failure. in write_control_registers()
|
/openbmc/linux/drivers/irqchip/ |
H A D | irq-gic-common.c | 79 * non-secure mode, and hence it may not be catastrophic. in gic_configure_irq()
|
/openbmc/docs/designs/ |
H A D | ecc-dbus-sel.md | 44 they become catastrophic faulty memory module.
|
/openbmc/qemu/qapi/ |
H A D | dump.json | 63 # 1. The guest may be in a catastrophic state or can have
|
/openbmc/linux/arch/alpha/kernel/ |
H A D | irq_alpha.c | 186 case 0x219: reason = "IOCHK#, EISA add-in board parity or other catastrophic error"; break; in process_mcheck_info()
|
/openbmc/openbmc/poky/scripts/ |
H A D | patchtest.README | 99 catastrophic if malicious bits or even poorly-handled edge cases aren't
|
/openbmc/linux/include/linux/ |
H A D | kdb.h | 131 #define KDB_FLAG_CATASTROPHIC (1 << 1) /* A catastrophic event has occurred */
|
/openbmc/linux/Documentation/userspace-api/ |
H A D | iommu.rst | 88 catastrophic failures for the users.
|
/openbmc/linux/Documentation/firmware-guide/acpi/ |
H A D | osi.rst | 143 catastrophic failure resulting from the BIOS taking paths that
|
/openbmc/linux/arch/mips/ath25/ |
H A D | ar2315.c | 63 machine_restart("AHB error"); /* Catastrophic failure */ in ar2315_ahb_err_handler()
|
H A D | ar5312.c | 68 machine_restart("AHB error"); /* Catastrophic failure */ in ar5312_ahb_err_handler()
|
/openbmc/linux/drivers/watchdog/ |
H A D | acquirewdt.c | 24 * Systems can always recover from catastrophic conditions that
|