| commit | 30b6496ac81b878ac8ccfe03f495386e24ff1a19 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Wed Jan 19 16:58:28 2022 +1030 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Fri Jan 21 10:14:58 2022 +1030 |
| tree | c592eeb44fa5d857ef1b647246b88c6aab8bc517 | |
| parent | 210ad6361b666108b862903b241b5ec78b8907f7 [diff] |
main: Use /proc/sysrq-trigger for reboot as well as crash This way when using stdout as the sink we don't accidentally reboot the system. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: If6b08f7a2773debf10bd1439790f8f9c83604d59
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.