> Other ideas were mentioned, like providing enough of the USB stack to write the crash information to a USB stick as Anvin suggests
I suppose I should resend blockconsole. It has proven to catch the crash information, along with the entire kernel log, on a usb stick. It is actually surprising how robust this is, in spite of the large amount of code it depends upon.
Posted Jun 30, 2012 14:59 UTC (Sat) by mb (subscriber, #50428)
[Link]
Am I the only one feeling nervous about using the block and fs subsystems on a fried kernel?
Displaying QR codes for kernel crashes
Posted Jul 1, 2012 2:28 UTC (Sun) by joern (subscriber, #22392)
[Link]
> Am I the only one feeling nervous about using the block and fs subsystems on a fried kernel?
Only block, no filesystem. And so far it has had a perfect track record in our environment. A rather nice surprise, as you definitely were not the only one. ;)