Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / 5d26ce6d057aaf10cf76da02bc92fe4ead4cd9cf
commit5d26ce6d057aaf10cf76da02bc92fe4ead4cd9cf[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Fri Dec 22 15:41:27 2023 +1030
committerAndrew Jeffery <andrew@aj.id.au>Fri Dec 22 15:49:57 2023 +1030
treecb14e9fdce5f2c1bfe109401061ca4b0907c6301
parentbe3dd0e67482cddc67c80ea1d4a0ed5cb6ad7733 [diff]
README: Fix header formatting

Address formatting failures from CI.

Change-Id: Iab2a07d6eb5bfecaeb7f250b85f00596d09aa948
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
1 file changed
tree: cb14e9fdce5f2c1bfe109401061ca4b0907c6301
  1. meson/
  2. systemd/
  3. udev/
  4. LICENSE
  5. main.c
  6. meson.build
  7. meson_options.txt
  8. OWNERS
  9. README.md
README.md

BMC Debug Trigger

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.

Trigger sources

debug-trigger implements a simple protocol over an LPC KCS device as its trigger source.

Debug actions

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.