Re: [PLUG] kernel panic from unknown cause

[Randall A Sindlinger <rsindlin+plug@seas.upenn.edu>]

Eric,

If it's a system that you'd like to have up right away, and can afford to
have another unpredictable kernel panic happen on, then this is what I've
found to be useful -

After booting the system normally, manually set the loglevel to 9 and 
switch over to tty10.  You'll need to have some kind of kvm hooked up
to it, of course, too, and not just work remotely.

Alt-SysRq-9 will set loglevel 9.  Ctrl-Alt-F10 will put you into tty10,
where loglevel 9 will spit *everything* out.  (actually all log levels
spit out there)  Make sure you _leave_ the machine at tty10 on the
monitor.  (Once the system hangs, you can't switch ttys)

The last few errors you see there will provide the best clues to what
caused the kernel panic.

Hope that helps,
-Randall Sindlinger
 Systems Programmer
 CETS, School of Engineering
 University of Pennsyvania

On Fri, Sep 11, 2009 at 12:53:06PM -0400, Eric wrote:
> Downloading SystemRescueCD right now.
> 
> Thanks
> 
> brent timothy saner wrote:
> > Burn a sysresccd[2] and do a memtest (memtest at the boot prompt) and also do a badblocks test to check for bad sectors in your /boot.
> > 
> > [1] http://www.google.com/linux?hl=en&ie=ISO-8859-1&q=debugging+kernel+panics&btnG=Search
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug