Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / debug-trigger / 640de114fcccbbe22e879386b55bdab32c8f33e4
commit640de114fcccbbe22e879386b55bdab32c8f33e4[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Thu Jan 13 13:53:04 2022 +1030
committerAndrew Jeffery <andrew@aj.id.au>Wed Jan 19 15:39:20 2022 +1030
tree7863e61dc96bd754e40047a1ba4eea4562e8e562
parent9c7783babcef53d80bf14dc268b72f61651009ad [diff]
OWNERS: Fix typo in 'matchers'

https://gerrit.googlesource.com/plugins/owners/+/refs/heads/master/owners/src/main/resources/Documentation/config.md#example-4-owners-based-on-matchers

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: Id732831cb82b04ec75eb21957217ece8af107021
1 file changed
tree: 7863e61dc96bd754e40047a1ba4eea4562e8e562
  1. meson/
  2. systemd/
  3. udev/
  4. LICENSE
  5. main.c
  6. MAINTAINERS
  7. meson.build
  8. meson_options.txt
  9. OWNERS
  10. 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.