Re: 2.2.0-pre3 OOPS

nads@bleh.org
Sat, 02 Jan 1999 07:13:42 -0500


nads@bleh.org wrote:

> ------------------------------------------------------------------------
>
> Subject: Re: 2.2.0-pre3 OOPS
> Date: Sat, 02 Jan 1999 06:37:57 -0500
> From: nads@bleh.org
> To: "David S. Miller" <davem@dm.cobaltmicro.com>
> References: <368DFC53.949707C5@bleh.org> <199901021108.DAA04127@dm.cobaltmicro.com>
>
> "David S. Miller" wrote:
>
> > Please feed this through ksymoops using your System.map file for this
> > kernel, the debugging is almost entirely useless without such output.
> >
> > Later,
> > David S. Miller
> > davem@dm.cobaltmicro.com
> >
> > -
> > 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/
>
> Arg,
>
> The include ksymoops, segfaults.
>
> [root@nut scripts]# ./ksymoops ../System.map < /home/bleh/kernoops
> Segmentation fault
> [root@nut scripts]#
>
> However after reading a recent thread on ksymoops, one of the letters
> included an alternate ksymoops availble @
> <ftp://ftp.ocs.com.au/pub/ksymoops.tar.gz>.
>
> That produced the following output:
>
> >>EIP: c0158328 <nfsd_unlink+12c/1ec>
> Trace: c0154a50 <nfsd_dispatch+0/150>
> Trace: c0155760 <nfsd_proc_rmdir+3c/4c>
> Trace: c0154b1b <nfsd_dispatch+cb/150>
> Trace: c019b0dd <svc_process+359/64c>
> Trace: c019b8a4 <svc_udp_recvfrom+1b4/1c8>
> Trace: c019c2b1 <svc_recv+239/370>
> Trace: c0154a50 <nfsd_dispatch+0/150>
> Trace: c01549a3 <nfsd+157/204>
> Trace: c015484c <nfsd+0/204>
> Trace: c01065db <kernel_thread+23/30>
> Code: c0158328 <nfsd_unlink+12c/1ec> 00000000 <_EIP>:
> Code: c0158328 <nfsd_unlink+12c/1ec> 0: ff 49 00
> decl 0
> x0(%ecx)
> Code: c015832b <nfsd_unlink+12f/1ec> 3: 0f 88 41 30 09
> js 9
> 304a <_EIP+0x9304a> c01eb372 <stext_lock+56e/2200>
> Code: c0158330 <nfsd_unlink+134/1ec> 8: 00
> Code: c0158331 <nfsd_unlink+135/1ec> 9: 83 7d 2c 00
> cmpl $
> 0x0,0x2c(%ebp)
> Code: c0158335 <nfsd_unlink+139/1ec> d: 75 06
> jne 1
> 5 <_EIP+0x15> c015833d <nfsd_unlink+141/1ec>
> Code: c0158337 <nfsd_unlink+13b/1ec> f: 8b 46 34
> movl 0
> x34(%esi),%eax
> Code: c015833a <nfsd_unlink+13e/1ec> 12: 89 45 00
> movl %
> eax,0x0(%ebp)
>
> 239 warnings issued. Results may not be reliable.
> [root@nut ksymoops-0.6]#

I have now had this seemingly same OOPS occur for the third time in less than 2
hours. The following is the output/trace from the 3rd oops (which appears to be the
same as the previous 2). This one occured telneting into my mutlia (which has nfs on
root), I wanted to see if it was still alvie or needed a reboot. I guess I'm going
back to 2.2.0-pre1ac1, until this stuff is cleared up.

Jan 2 07:04:51 nut kernel: Unable to handle kernel NULL pointer
Jan 2 07:04:51 nut kernel: current->tss.cr3 = 00101000, pr3 = 00101000
Jan 2 07:04:51 nut kernel: *pde = 00000000
Jan 2 07:04:51 nut kernel: Oops: 0000
Jan 2 07:04:51 nut kernel: CPU: 0
Jan 2 07:04:51 nut kernel: EIP: 0010:[<c0158328>]
Jan 2 07:04:51 nut kernel: EFLAGS: 00010246
Jan 2 07:04:51 nut kernel: eax: c2091694 ebx: 0000004c ecx: 0000004c
Jan 2 07:04:51 nut kernel: esi: c2091648 edi: c21d2660 ebp: c5611120
Jan 2 07:04:51 nut kernel: ds: 0018 es: 0018 ss: 0018
Jan 2 07:04:51 nut kernel: Stack: c53fc014 c0154a50 c0155760 c5aa9c00
c5611120 00004000 c275d668 0000000d
Jan 2 07:04:51 nut kernel: c5aa9c00 c021df4c c0154b1b c5aa9c00
c5611120 c5611240 00000004 c021df4c
Jan 2 07:04:51 nut kernel: c53fc014 c019b0dd c5aa9c00 c53fc014
c53de000 00000000 c5aa9c00 c0088840
Jan 2 07:04:51 nut kernel: Call Trace: [<c0154a50>] [<c0155760>]
[<c0154b1b>] [<c019b0dd>] [<c019b8a4>] [<c019c2b1>] [<c0154a50>]
Jan 2 07:04:51 nut kernel: [<c01549a3>] [<c015484c>] [<c01065db>]
Jan 2 07:04:51 nut kernel: Code: ff 49 00 0f 88 41 30 09 00 83 7d 2c 00

>>EIP: c0158328 <nfsd_unlink+12c/1ec>
Trace: c0154a50 <nfsd_dispatch+0/150>
Trace: c0155760 <nfsd_proc_rmdir+3c/4c>
Trace: c0154b1b <nfsd_dispatch+cb/150>
Trace: c019b0dd <svc_process+359/64c>
Trace: c019b8a4 <svc_udp_recvfrom+1b4/1c8>
Trace: c019c2b1 <svc_recv+239/370>
Trace: c0154a50 <nfsd_dispatch+0/150>
Trace: c01549a3 <nfsd+157/204>
Trace: c015484c <nfsd+0/204>
Trace: c01065db <kernel_thread+23/30>
Code: c0158328 <nfsd_unlink+12c/1ec> 00000000 <_EIP>:
Code: c0158328 <nfsd_unlink+12c/1ec> 0: ff 49 00 decl 0
x0(%ecx)
Code: c015832b <nfsd_unlink+12f/1ec> 3: 0f 88 41 30 09 js 9
304a <_EIP+0x9304a> c01eb372 <stext_lock+56e/2200>
Code: c0158330 <nfsd_unlink+134/1ec> 8: 00
Code: c0158331 <nfsd_unlink+135/1ec> 9: 83 7d 2c 00 cmpl $
0x0,0x2c(%ebp)

239 warnings issued. Results may not be reliable.
[root@nut ksymoops-0.6]#

-
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/