Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / 210ad6361b666108b862903b241b5ec78b8907f7
commit210ad6361b666108b862903b241b5ec78b8907f7[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Thu Jan 13 14:16:53 2022 +1030
committerAndrew Jeffery <andrew@aj.id.au>Fri Jan 21 10:14:58 2022 +1030
tree71bfcee427e4c399d21bceb847e704f833b6d2bb
parentdb47cd7f6440c810e05e44d0fcc334502e4a9a81 [diff]
process: Lift reboot implementation to separate function

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