Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / d1c5dd1ae54b7afa7f0f3cc85c6ce279f35f0c80
commitd1c5dd1ae54b7afa7f0f3cc85c6ce279f35f0c80[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Fri Jan 14 21:43:28 2022 +1030
committerAndrew Jeffery <andrew@aj.id.au>Fri Jan 21 10:14:58 2022 +1030
tree043bb56ccadda9f27ea92cc2c9787f202409cc05
parent86094694a28e0c50a4f10bc18b9ac6e9c11c0f52 [diff]
systemd: Start after the dump manager

In case --sink=dbus is supplied.

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