Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / ea84ad977dc202f4b17c9faf4087949b82b86c92
commitea84ad977dc202f4b17c9faf4087949b82b86c92[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Fri Jan 14 22:07:30 2022 +1030
committerAndrew Jeffery <andrew@aj.id.au>Fri Jan 21 10:14:58 2022 +1030
tree28f9cf6afa643bdf63d3a8e22e0be03778b19fb2
parent8660e7795f8d8be00372a1e725fe68f29b2c0fb4 [diff]
main: Be clear about what we failed to open

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I5884b83716f73da8f055a7267b3efab36c856ea8
1 file changed
tree: 28f9cf6afa643bdf63d3a8e22e0be03778b19fb2
  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.