Kernel bug

Trevor Johnson (robert@pc021.phy.uct.ac.za)
Tue, 16 Mar 1999 10:46:13 +0200 (SAST)


I have had the following oops from the linux 2.2.2 kernel.
The problem may have something to do with the NCPFS code as after this
error, one could not view any of the files under an ncpfs mount point. I
could not unmount the ncp file system (It gave device busy errors.)
Even after entering single user mode I was not able to unmount this
filesystem or view any of the files in it.
I was able to mount and unmount the ncp filesystem under other mount
points.

The following appeared in the syslog file
Mar 15 17:06:26 pc021 kernel: NCP max timeout
Mar 15 17:06:32 pc021 kernel: NCP max timeout
Mar 15 17:06:38 pc021 kernel: NCP server not responding
Mar 15 17:06:38 pc021 kernel: NCP: notice message: result=-11
Mar 15 17:17:20 pc021 PAM_pwdb[354]: (login) session closed for user
robert
Mar 16 04:02:02 pc021 PAM_pwdb[3260]: (su) session opened for user nobody
by (ui
d=99)
Mar 16 04:03:41 pc021 PAM_pwdb[3260]: (su) session closed for user nobody
Mar 16 08:22:15 pc021 PAM_pwdb[3314]: (login) session opened for user
schumann b
y (uid=0)
Mar 16 08:22:16 pc021 -- schumann [3314]:
LOGIN ON
ttyp0 BY schumann FROM ann
Mar 16 08:22:19 pc021 kernel: Unable to handle kernel paging request at
virtual
address e50a799d

I ran the oops through the ksymoops program and here is the results:

Options used: -V (specified)
-o /lib/modules/2.2.2/ (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /usr/src/linux/System.map (default)
-c 1 (default)

Mar 16 08:22:19 pc021 kernel: Unable to handle kernel paging request at virtual address e50a799d
Mar 16 08:22:19 pc021 kernel: current->tss.cr3 = 00465000, pr3 = 00465000
Mar 16 08:22:19 pc021 kernel: *pde = 00000000
Mar 16 08:22:19 pc021 kernel: Oops: 0000
Mar 16 08:22:19 pc021 kernel: CPU: 0
Mar 16 08:22:19 pc021 kernel: EIP: 0010:[<c685806f>]
Mar 16 08:22:19 pc021 kernel: EFLAGS: 00010286
Mar 16 08:22:19 pc021 kernel: eax: e50a7965 ebx: c114aea8 ecx: 00000008 edx: c114aea8
Mar 16 08:22:19 pc021 kernel: esi: c14f9d3e edi: 00000003 ebp: c433ff10 esp: c433fee8
Mar 16 08:22:19 pc021 kernel: ds: 0018 es: 0018 ss: 0018
Mar 16 08:22:19 pc021 kernel: Process bash (pid: 3315, process nr: 79, stackpage=c433f000)
Mar 16 08:22:19 pc021 kernel: Stack: 00000003 c3ebfbc0 c0129454 c3ebfbc0 c433ff10 00000000 c14f9c90 c47e39e0
Mar 16 08:22:19 pc021 kernel: c14f9d28 c47e39e0 c14f9d35 00000008 55f3b789 c013ee69 c14f9d28 c47e39e0
Mar 16 08:22:19 pc021 kernel: 00000001 c14f9c90 c433e000 c53e9a40 c47e39e0 c47e39e0 c433ff84 c012933f
Mar 16 08:22:19 pc021 kernel: Call Trace: [<c0129454>] [<c013ee69>] [<c012933f>] [<c01294c0>] [<c012955d>] [<c0121c02>] [<c0107a40>]
Mar 16 08:22:19 pc021 kernel: Code: 80 78 38 02 74 3e 31 db 31 c9 8b 45 04 39 c3 73 30 8b 7d 00

>>EIP: c685806f <END_OF_CODE+2d737/????>
Trace: c0129454 <lookup_dentry+d8/1b8>
Trace: c013ee69 <ext2_follow_link+65/84>
Trace: c012933f <do_follow_link+47/84>
Trace: c01294c0 <lookup_dentry+144/1b8>
Trace: c012955d <__namei+29/5c>
Trace: c0121c02 <sys_chdir+e/68>
Trace: c0107a40 <system_call+34/38>
Code: c685806f <END_OF_CODE+2d737/????> 00000000 <_EIP>:
Code: c685806f <END_OF_CODE+2d737/????> 0: 80 78 38 02 cmpb $0x2,0x38(%eax)
Code: c6858073 <END_OF_CODE+2d73b/????> 4: 74 3e je 44 <_EIP+0x44> c68580b3 <END_OF_CODE+2d77b/????>
Code: c6858075 <END_OF_CODE+2d73d/????> 6: 31 db xorl %ebx,%ebx
Code: c6858077 <END_OF_CODE+2d73f/????> 8: 31 c9 xorl %ecx,%ecx
Code: c6858079 <END_OF_CODE+2d741/????> a: 8b 45 04 movl 0x4(%ebp),%eax
Code: c685807c <END_OF_CODE+2d744/????> d: 39 c3 cmpl %eax,%ebx
Code: c685807e <END_OF_CODE+2d746/????> f: 73 30 jae 41 <_EIP+0x41> c68580b0 <END_OF_CODE+2d778/????>
Code: c6858080 <END_OF_CODE+2d748/????> 11: 8b 7d 00 movl 0x0(%ebp),%edi

1 warning issued. Results may not be reliable.

I hope this helps.

Robert lindebaum

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