Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / 1348d52b6b5367554a9f4a30dadd536c3ded6f1e
commit1348d52b6b5367554a9f4a30dadd536c3ded6f1e[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Thu Jan 13 13:54:15 2022 +1030
committerAndrew Jeffery <andrew@aj.id.au>Wed Jan 19 15:39:56 2022 +1030
tree701028c7c53da1d9d3b72e7e0111145a13792cdc
parent640de114fcccbbe22e879386b55bdab32c8f33e4 [diff]
MAINTAINERS: Remove in favour of OWNERS

We use Gerrit's 'owners' plugin now, so drop the org-specific
MAINTAINERS file.

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