You are not logged in.
[SOLVED] but the kdump solution sounds tricky to set up. the firewire or netdump approach looks really good if one has a firewire laptop or tablet lying around to serve as the server onto which one may dump the panic'd kernel.
Has anyone found a way to get a serial console purely over USB? I tried taking pictures of the kernel panic stack trace but it looks like a lot of info goes off the screen. several times the call chain's final few lines are at the top of the screen & the rest of the screen, almost all of it, is a bunch of other info I don't recognize at all.
I've been searching for the full-USB solution but if it's possible I have not found it. All the articles require a serial port on the machine to be debugged. Couple of cool things I've come across so far
http://linux.die.net/man/8/netdump
firewire "serial console"
http://wiki.freebsd.org/DebugWithDcons
http://www.breaknenter.org/projects/inception/
<sigh> I have stuff due @ school I hope this machine doesn't blow out & take up too much time </sigh>
If I figure something out I'll update this when I can.
https://wiki.archlinux.org/index.php/Kexec
https://wiki.archlinux.org/index.php/Kdump
For as long as I can remember the party line has been that one should not use the machine at all after a panic without rebooting. Doing anything might corrupt your disks. But if this is now a standard kernel technique the older caveats must have been loosened ... Well, I also see on the Kdump page
" or optionally you can copy the crash to other machine. Once dump is saved you should reboot machine into normal system kernel. "
so it's telling you not to do much on the corrupted machine, even with the "clean" kernel
Last edited by Sanjeev K Sharma (2013-10-27 04:50:27)
Offline