Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / 92eb22223d414940cc09af7c029192473d1d385e
commit92eb22223d414940cc09af7c029192473d1d385e[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Fri Dec 22 15:38:17 2023 +1030
committerAndrew Jeffery <andrew@aj.id.au>Fri Dec 22 15:49:57 2023 +1030
tree3c9e5d5633617f78c2c15e04be5b3b8bbf2a0df7
parent5d26ce6d057aaf10cf76da02bc92fe4ead4cd9cf [diff]
OWNERS: Update Andrew's preferred email

We're having some grief with non-preferred emails in Gerrit[1]. I now
prefer project-related content goes to my work email address, so use my
non-preferred email to implement the switch.

[1]: https://issues.gerritcodereview.com/issues/317345953

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