Re: How do I debug kernel panic that occurs while running X?
On 2012-03-04 09:16 +0100, Jason Heeris wrote:
> On 4 March 2012 01:28, Brendon Higgins <blhiggins@gmail.com> wrote:
>> Any more ideas? As I said, I tried getting kdump working but have been having
>> trouble getting it to behave.
>
> One more thought, but it's a bit of a long shot as to whether you have
> the equipment. The most watertight way I know of to capture kernel
> output is a serial port and another computer. If, by any chance, you
> have one on your machine, edit /etc/defaults/grub to include
> console=ttyS0,155200n1 (or whatever speed you like) on the kernel boot
> line. You'll also need another machine with either a serial port or a
> USB-serial adapter, making it half as likely that this will help you
> :P
>
> Of course, most computers these days (*ahem*) don't have serial ports.
> *Maybe* a USB-serial adapter will work for the target machine too...
> although this requires an extra level of redirection on the part of
> the kernel, and may not be as foolproof, so I wouldn't spend the money
> if you don't already have one (or, in fact, two).
>
> Other than that, I'm out of ideas. Hopefully someone else on this list
> has an idea that doesn't require technology that was rendered obsolete
> for most people by 1995...
Either log in via ssh if that is still possible, or use netconsole to
capture kernel messages.
Sven
http://www.kernel.org/doc/Documentation/networking/netconsole.txt
http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/
Reply to: