| /openbmc/docs/designs/ |
| H A D | nmi-dbus-interface.md | 12 debug data when the host is unresponsive or hung. These systems need the ability
18 There is a situation at customer places/lab where the host goes unresponsive
23 Whenever the host is unresponsive/running, Admin needs to trigger an NMI event
32 fix any issues where they see host hang and unresponsive system.
58 1. Host/OS is hung or unresponsive or one need to take kernel dump to debug some
70 - Note: NMI can be sent to the host in any state, not just at an unresponsive
|
| H A D | bmc-service-failure-debug-and-recovery.md | 57 4. Unresponsive: The service fails to detect it cannot make progress and
58 continues to run but is unresponsive
70 unnecessary, while in the case of a unresponsive service the need to restart
74 unresponsive state can only begin upon receiving external input.
91 external interfaces becoming unresponsive and be viewed as a critical failure of
101 unresponsive to the point that the BMC cannot be recovered except via external
103 the host can detect the BMC is unresponsive on the in-band interface(s), an
117 | Unresponsive | None |
136 | Unresponsive | `hardlockup_panic`, `softlockup_panic` |
166 | 2 | Forceful reboot request | Recovery from unresponsive platform data transport providers…
[all …]
|
| /openbmc/docs/process/ |
| H A D | subproject-maintainership.md | 101 progress when the existing maintainers become unresponsive.
107 While all unresponsive maintainers are problematic maintainers to some extent,
108 it's not true that all problematic maintainers are unresponsive maintainers.
110 progress at the subproject scope in the face of unresponsive maintainers. It
145 accommodate the review load][ed-is-only-human]. While unresponsive maintainers
167 2. An unresponsive maintainer's knowledge of the codebase may age to the point
185 2. Not removing rights of an unresponsive maintainer from the subproject exposes
200 unresponsive maintainer should itself be notable.
207 unresponsive maintainers, beyond recognising that they have met some bar of
264 subproject are unresponsive at the project scope before the TOF may on-board new
[all …]
|
| /openbmc/debug-trigger/ |
| H A D | README.md | 4 unresponsive. When the signal is received it triggers a crash to collect debug
17 system was externally unresponsive.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/ |
| H A D | Create.interface.yaml | 54 when it encounters an error and become unresponsive.
58 it encounters critical failures or unresponsive.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-driver-qat | 36 Description: (RO) Read returns the number of times the device became unresponsive.
57 Returns 0 when device is healthy or -1 when is unresponsive
|
| /openbmc/openbmc/poky/meta/lib/oeqa/utils/ |
| H A D | dump.py | 81 or unresponsive.
111 This helps to end testing when target is really dead, hanging or unresponsive.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Host/ |
| H A D | NMI.interface.yaml | 3 operating system when host is unresponsive or hung.
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/dump/ |
| H A D | debug-trigger_git.bb | 2 DESCRIPTION = "Forcibly crash an unresponsive system to collect debug data"
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/ncftp/ncftp/ |
| H A D | 0001-ncftp-3.2.7-fix-gcc14.patch | 6 Upstream-Status: Inappropriate [unresponsive contact email address]
|
| H A D | 0002-ncftp-3.2.7-fix-clang.patch | 9 Upstream-Status: Inappropriate [unresponsive contact email address]
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | SBE.interface.yaml | 8 unresponsive. In such situations, the debug data needs to be collected from
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | BMC.interface.yaml | 68 unresponsive or only processing a restricted set of commands.
|
| H A D | Host.interface.yaml | 90 either unresponsive or only processing a restricted set of
|
| /openbmc/linux/include/linux/mtd/ |
| H A D | xip.h | 70 #warning "your system will therefore be unresponsive when writing or erasing flash"
|
| /openbmc/linux/include/linux/sunrpc/ |
| H A D | metrics.h | 42 * than one transmission because the server is unresponsive,
|
| /openbmc/openbmc-test-automation/redfish/service_root/ |
| H A D | test_service_root.robot | 123 Verify Redfish Unresponsive URL paths
|
| /openbmc/linux/drivers/net/ethernet/intel/iavf/ |
| H A D | iavf_client.h | 115 /* If the PE Engine is unresponsive, RDMA driver can request a reset.*/
|
| /openbmc/linux/kernel/debug/kdb/ |
| H A D | kdb_debugger.c | 125 /* set CATASTROPHIC if the system contains unresponsive processors */ in kdb_stub()
|
| /openbmc/linux/include/soc/fsl/ |
| H A D | bman.h | 111 * Adds the given buffers to RCR entries. If the RCR ring is unresponsive,
|
| /openbmc/linux/include/linux/net/intel/ |
| H A D | i40e_client.h | 118 /* If the PE Engine is unresponsive, RDMA driver can request a reset.
|
| /openbmc/linux/drivers/net/ethernet/freescale/dpaa2/ |
| H A D | dpaa2-switch.h | 66 * hardware becomes unresponsive, but not give up too easily if
|
| /openbmc/linux/Documentation/devicetree/bindings/hwmon/pmbus/ |
| H A D | max31785.txt | 54 emergency action for an unresponsive fan and driving
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | gpio-fault-injection.rst | 27 the condition of SCL being unresponsive and report an error to the upper
|
| /openbmc/linux/drivers/infiniband/hw/efa/ |
| H A D | efa_io_defs.h | 57 /* Unresponsive remote - detected locally */
|