correct the record: the 2026-08-10 boot wedges were the USB-serial adapter hanging an unbounded overlapped write, NOT print-deadlock (confounded A/B, retracted); pod runbook gets the full COM1/FTDI diagnosis + remote minidump procedure
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
716e10e3fa
commit
9754fb1295
@@ -2121,9 +2121,11 @@ static unsigned long
|
||||
return token;
|
||||
}
|
||||
|
||||
// [rio] health printer (L4RIO.cpp): the serial path may only COUNT --
|
||||
// printing from it deadlocks against the PCSPAK RX thread -- so the report
|
||||
// rides this tick, which already streams [glassperf] safely every second.
|
||||
// [rio] health printer (L4RIO.cpp): the serial poll path only COUNTS (kept
|
||||
// I/O-free by design; the 2026-08-10 wedges once blamed on prints there were
|
||||
// really the USB-serial adapter hanging an unbounded overlapped write --
|
||||
// see PCSerialPacket::SendPacket); the report rides this tick, which
|
||||
// already streams [glassperf] every second.
|
||||
extern "C" void BTRioHealthReport();
|
||||
|
||||
void
|
||||
|
||||
Reference in New Issue
Block a user