[K12OSN] Help diagnosing a kernal panic

[Jim McQuillan]

Brian,

smbd is a user-space program.  It's pretty rare that a user-space 
program can cause a kernel panic, unless it's managed to trip over a bug 
in the kernel.

I'd say it's more likely a hardware issue.  First thing I'd do is shut 
down the machine, open it up, and re-seat all of the cards and memory.
Make sure everything is plugged in securely.

Jim McQuillan
jam at Ltsp.org



Brian Chivers wrote:
> Three times in the last three weeks our main Samba server has tripped 
> over giving the information below in /var/log/messages
> 
> Mar  7 13:08:50 rho2 kernel: Unable to handle kernel NULL pointer 
> dereference at virtual address 0000000c
> Mar  7 13:08:50 rho2 kernel:  printing eip:
> Mar  7 13:08:50 rho2 kernel: c01cbbc8
> Mar  7 13:08:50 rho2 kernel: *pde = 06f1f001
> Mar  7 13:08:50 rho2 kernel: Oops: 0000 [#1]
> Mar  7 13:08:50 rho2 kernel: SMP
> Mar  7 13:08:50 rho2 kernel: Modules linked in: md5 ipv6 autofs4 i2c_dev 
> i2c_core sunrpc dm_mod video button battery ac uhci_hcd ehci_hcd e1000 
> floppy sg ext3
>  jbd mptscsih mptbase sd_mod scsi_mod
> Mar  7 13:08:50 rho2 kernel: CPU:    2
> Mar  7 13:08:50 rho2 kernel: EIP:    0060:[<c01cbbc8>]    Not tainted VLI
> Mar  7 13:08:50 rho2 kernel: EFLAGS: 00010207   (2.6.11-1.14_FC3smp)
> Mar  7 13:08:50 rho2 kernel: EIP is at __rb_rotate_left+0x8/0x3a
> Mar  7 13:08:50 rho2 kernel: eax: cb457e80   ebx: c0472804   ecx: 
> cb457e80   edx: 00000000
> Mar  7 13:08:50 rho2 kernel: esi: cb457e80   edi: d98ad500   ebp: 
> c0472804   esp: d230ced0
> Mar  7 13:08:50 rho2 kernel: ds: 007b   es: 007b   ss: 0068
> Mar  7 13:08:50 rho2 kernel: Process smbd (pid: 9477, 
> threadinfo=d230c000 task=f640d020)
> Mar  7 13:08:50 rho2 kernel: Stack: caadc6c0 c01cbca5 00000000 d98ad50c 
> d98ad500 00000e49 c01aa6bc caadc6c0
> Mar  7 13:08:50 rho2 kernel:        d230cf50 00000016 d230cf5e ffffffea 
> c01aa762 0000000e 00000016 00000000
> Mar  7 13:08:50 rho2 kernel:        00000e49 c0365440 00000e49 c0467358 
> e1bddbc0 e1bddbc0 c01aba60 ffffffff
> Mar  7 13:08:50 rho2 kernel: Call Trace:
> Mar  7 13:08:50 rho2 kernel:  [<c01cbca5>] rb_insert_color+0x71/0xc4
> Mar  7 13:08:50 rho2 kernel:  [<c01aa6bc>] key_user_lookup+0xfc/0x113
> Mar  7 13:08:50 rho2 kernel:  [<c01aa762>] key_alloc+0x5b/0x2ef
> Mar  7 13:08:50 rho2 kernel:  [<c01aba60>] keyring_alloc+0x28/0x62
> Mar  7 13:08:50 rho2 kernel:  [<c01ad1f1>] alloc_uid_keyring+0x41/0x9f
> Mar  7 13:08:50 rho2 kernel:  [<c012a89a>] alloc_uid+0xaf/0x139
> Mar  7 13:08:50 rho2 kernel:  [<c012e0cb>] set_user+0xb/0x78
> Mar  7 13:08:50 rho2 kernel:  [<c012e45c>] sys_setresuid+0x9b/0x1cd
> Mar  7 13:08:51 rho2 kernel:  [<c0103f0f>] syscall_call+0x7/0xb
> Mar  7 13:08:51 rho2 kernel: Code: 0c 83 c1 01 83 f9 01 76 ea 31 c0 5bcl 
> c3 b8 01 00 00 00 5b c3 57 b9 45 00 00 00 89 c7 31 c0 f3 ab 5f c3 90 53 
> 89 d3 89 c1 8b
> 50 08 <8b> 42 0c 85 c0 89 41 08 74 02 89 08 8b 01 89 4a 0c 85 c0 89 02
> 
> Would you say that it's the smbd process on line 15 that's causing the 
> system to trip over ??
> 
> The system has been running fine for almost 3 years now so I'm not sure 
> why it has suddenly started doing this, I've not installed any new 
> software or run any updates since it was installed, I know this is bad 
> but it's a Fedora Core 3 box and with the closure of the fedora legecy 
> project it's not that simple to do updates.
> 
> This is our main Samba server so I'm a little concerned about just 
> trying things as the system also runs our OpenLDAP server so is the 
> "heart of the machine"
> 
> Any pointers would be gratefully be received.
> 
> Brian Chivers
> 
> 
> ------------------------------------------------------------------------
>    The views expressed here are my own and not necessarily 
>                the views of Portsmouth College   
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>