| commit | 8660e7795f8d8be00372a1e725fe68f29b2c0fb4 | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Fri Jan 14 21:59:15 2022 +1030 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Fri Jan 21 10:14:58 2022 +1030 |
| tree | 552c156e2f7e322d33e52f23ad708a5310f8f8d6 | |
| parent | d1c5dd1ae54b7afa7f0f3cc85c6ce279f35f0c80 [diff] |
systemd: Configure command-line using the environment The existing behaviour remains the default but can be modified by dropping in an environment file into /etc/default. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: Icbeac6ea60bf76c98eaa03f4e5f2ecf0ddc2733d
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.