Re: oops in 2.2.10
Keith Owens (kaos@ocs.com.au)
Mon, 21 Jun 1999 10:08:01 +1000
On Sun, 20 Jun 1999 21:58:25 +0100 (GMT),
Tim Waugh <tim@cyberelk.demon.co.uk> wrote:
>On Tue, 15 Jun 1999, Joop Stakenborg wrote:
>> I managed to get a trace of the program together with an oops,
>> Jun 15 20:31:57 pa4tu kernel: Call Trace: [3c509:el3_probe+-94804/5532] [3c509:el3_probe+-94727/5532] [3c509:el3_probe+-94804/5532] [3c509:el3_probe+-6288/5532] [3c509:el3_probe+-8720/5532] [3c509:el3_probe+-6288/5532] [3c509:el3_probe+-22159/5532]
>> Jun 15 20:31:57 pa4tu kernel: [send_sig_info+363/672] [notify_parent+184/196] [sock_recvmsg+65/180] [3c509:el3_probe+-94804/5532] [sock_read+133/148] [sys_read+166/188] [tracesys+24/38] [startup_32+43/286]
>el3_probe+-94804/5532 doesn't make any sense. I'm not up to speed on
>klogd really -- can it decode oopses from modules?
If you can reproduce the problem, I suggest running klogd with the -x
option so it does not try to decode the Oops. Then use
ftp://ftp.ocs.com.au/pub/ksymoops/ksymoops-0.7c.tar.gz to pull the Oops
apart. ksymoops can handle modules, especially if you use the modutils
patch from the same directory. See the ksymoops man page.
-
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/