The XGS 136's host panics at the driver's unload, 2026-11-03
988: on 2026-11-02 the XGS 136's host stopped
after its coprocessor had been taken up again in place, and left nothing to say why - its kernel waited
in the debugger after a panic, if it was one, until the hardware watchdog restarted it. the hardware
watchdog restarted it, with no dump. (Corrected 2026-11-03: OPNsense loads a script for the kernel's
debugger at every boot, kdb.enter.default in debug.ddb.scripting.scripts, which writes a textdump and
restarts the host - a panic that entered the debugger would not have waited there for the watchdog, so
that stop was a hang, or a panic that never finished its textdump.) For the runs of
2026-11-03 debug.debugger_on_panic was 0, so that a panic writes its dump and restarts the host. The
lab's XGS 136 (vendor version 21), the same stop as in the runs of 2026-11-02
(images/deploy/lab-768-silent.sh: the coprocessor's getty and watchdog feeder stopped, its end of the
management link down; its own watchdog resets it and fastpath.py takes it up again in place), and a
logger on the host reading dev.npuep.0.heartbeat.state every half second.
The whole page, with how it was taken and what it does not show: The XGS 136's host panics at the driver's unload, 2026-11-03.
The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.