| commit | 9c7783babcef53d80bf14dc268b72f61651009ad | [log] [tgz] |
|---|---|---|
| author | Manojkiran Eda <manojkiran.eda@gmail.com> | Sat Oct 23 07:04:43 2021 +0530 |
| committer | Manojkiran Eda <manojkiran.eda@gmail.com> | Sat Oct 23 07:05:18 2021 +0530 |
| tree | e2887b1d589722e9a440c3ad27495925fbda4201 | |
| parent | 15fe59cb0fc1430bdd05a85e7c7887ccc4e5c013 [diff] |
Add OWNERS file Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I8f64250aeaa85ebb6eba1a1962170a67bc2f2ae7
debug-trigger listens for an external signal that the BMC is in some way unresponsive. When the signal is received it triggers a crash to collect debug data and reboots the system in the hope that it will recover.
debug-trigger implements a simple protocol over an LPC KCS device as its trigger source.
debug-trigger implements a single action once the trigger event is received, which is to crash the kernel via /proc/sysrq-trigger. For systems with kdump configured this results in collection of system state as context for why the system was externally unresponsive.