lkml.org 
[lkml]   [1999]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Oops not catched by klogd
Date
On Sat, 18 Sep 1999 23:31:42 -0400 (EDT), 
Didier Contis <didier@ece.gatech.edu> wrote:
>Well, I cannot answer this question since after the oops I am unable
>to access the console. I can still switch from one console to
>another (alt + fx) but cannot login.

That indicates the machine is still running but a critical component is
hung. It is probably the disk I/O subsystem, in which case you will
not get any logs written to disk. If you have another machine nearby,
run a null modem cable, boot Linux with a serial console (see
Documentation/serial-console.txt), capture the Oops on the second
machine and feed it through ksymoops after you reboot.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.039 / U:1.512 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site