Kernel panics in 2.2.[45] with SMBFS

Chris Old (chippo@cdsec.com)
Thu, 1 Apr 1999 13:01:21 +0200 (SAST)


Hi-ho,

For a while I've been using 2.2.x. Yesterday (I was still running 2.2.4) I
decided to add SMBFS. So I reconfigured my kernel, but didn't install any
userspace tools yet. Upon reboot, there were a dozen or so kernel panics
before it hung solid. So I upgraded to 2.2.5 - same thing. Rebuilt the
kernel without SMBFS and no more panics.

Small nit though: when I removed smbfs, the kernel config told me that all I
had to do was 'make zImage'. This failed in the link phase with some error
about SMB. So I did a 'make dep clean zImage' (like the configurator used to
tell you) and averything built fine.

So back to these panics. I took the last one out of the logs and decoded it
-----------------------------------------
Options used: -v ../../vmlinux (specified)
-O (specified)
-K (specified)
-L (specified)
-m /System.map (specified)
-c 1 (default)

current->tss.cr3 = 03e22000, pr3 = 03e22000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0107ebf>]
EFLAGS: 00010092
eax: 74c084c0 ebx: 00000000 ecx: 00000001 edx: c0012000
esi: 0000002b edi: c3e16000 ebp: c4800000 esp: c3e15d18
ds: 0018 es: 0018 ss: 0018
Process X (pid: 348, process nr: 7, stackpage=c3e15000)
Stack: c3e14000 c02b3260 c01edcde c0161784 00000023 c3830c00 74c084c0 c3a203e0
c01dd50c 0000000e 74c084c0 00010202 c4800000 c5000000 c0107f20 c3e15d98
c01b3f48 c01b4f30 00000000 00000000 c010cf56 c01b4f30 c3e15d98 00000000
Call Trace: [<c0161784>] [<c4800000>] [<c5000000>] [<c0107f20>] [<c01b3f48>] [<c01b4f30>] [<c010cf56>]
[<c01b4f30>] [<c0161784>] [<c0107b45>] [<c0161784>] [<c0168993>] [<c01693be>] [<c0174a58>] [<c0174690>]
[<c0178a07>] [<c0178978>] [<c015c7a6>] [<c0178978>] [<c015d2ac>] [<c0116f62>] [<c01170e4>] [<c015dabb>]
[<c0107a40>]
Code: 0f b6 0c 03 89 4c 24 38 51 68 40 3f 1b c0 e8 ee 96 00 00 83

>>EIP: c0107ebf <show_registers+26b/29c>
Trace: c0161784 <dst_discard+0/20>
Trace: c4800000 <END_OF_CODE+45f8510/????>
Trace: c5000000 <END_OF_CODE+4df8510/????>
Trace: c0107f20 <die+30/38>
Trace: c01b3f48 <stext_lock+efc/1f5c>
Trace: c01b4f30 <stext_lock+1ee4/1f5c>
Trace: c010cf56 <do_page_fault+2c6/318>
Trace: c01b4f30 <stext_lock+1ee4/1f5c>
Trace: c0178a07 <inet_sendmsg+8f/a4>
Trace: c0107a40 <system_call+34/38>
Code: c0107ebf <show_registers+26b/29c> 00000000 <_EIP>: <===
Code: c0107ebf <show_registers+26b/29c> 0: 0f b6 0c 03
movzbl (%ebx,%eax,1),%ecx <===
Code: c0107ec3 <show_registers+26f/29c> 4: 89 4c 24 38 movl %ecx,0x38(%esp,1)
Code: c0107ec7 <show_registers+273/29c> 8: 51 pushl %ecx
Code: c0107ec8 <show_registers+274/29c> 9: 68 40 3f 1b c0 pushl $0xc01b3f40
Code: c0107ecd <show_registers+279/29c> e: e8 ee 96 00 00 call c01115c0 <printk+0/174>
Code: c0107ed2 <show_registers+27e/29c> 13: 83 00 00 addl $0x0,(%eax)
-----------------------------------------

So, what else can I send?
My kernel config?
Some more (all) of the panics decoded?
Anything else?

Ciao,
chippenthog

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