| commit | d65368be2872800621eb2528d6ff9494ab2362c3 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Wed Jan 19 15:59:20 2022 +1030 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Fri Jan 21 10:14:58 2022 +1030 |
| tree | 11bef798e43edcd15a0bbaa6fcd5c822e3146a02 | |
| parent | 30b6496ac81b878ac8ccfe03f495386e24ff1a19 [diff] |
main: Add some documentation Some tricks like defaulting the source and sink file descriptors to stdin and stdout aren't necessarily obvious, so add some commentary and justifications throughout. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: I515f36857a7056aa589ecbb09c46372ec4d3976d
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.