CentOS - Feb 2006 - Busy day today...

What's the procedure for filing bug reports related to kernel panics
on CentOS/RHEL? I've just had the following kernel panic on one of the
new mailstores (argh!). Would this have to be reproduceable to warrant
a bug report?


Feb 28 14:40:53 tempmailstore1a kernel: eip: c0146a64
Feb 28 14:40:53 tempmailstore1a kernel: eip: c0146a64
Feb 28 14:40:53 tempmailstore1a kernel: ------------[ cut here ]------------
Feb 28 14:40:53 tempmailstore1a kernel: kernel BUG at
include/asm/spinlock.h:133!
Feb 28 14:40:53 tempmailstore1a kernel: invalid operand: 0000 [#1]
Feb 28 14:40:53 tempmailstore1a kernel: SMP
Feb 28 14:40:53 tempmailstore1a kernel: Modules linked in: nfs
iptable_filter ip_tables nfsd exportfs lockd sunrpc ip_vs drbd(U) md5
ipv6 autofs4 button batte
ry ac ohci_hcd tg3 floppy sg dm_snapshot dm_zero dm_mirror ext3 jbd
dm_mod megaraid_mbox megaraid_mm sd_mod scsi_mod
Feb 28 14:40:53 tempmailstore1a kernel: CPU:    0
Feb 28 14:40:53 tempmailstore1a kernel: EIP:    0060:[<c02cfb49>]   
Not tainted VLI
Feb 28 14:40:53 tempmailstore1a kernel: EFLAGS: 00010046   (2.6.9-22.0.1.ELsmp)
Feb 28 14:40:53 tempmailstore1a kernel: EIP is at _spin_lock+0x1c/0x34
Feb 28 14:40:53 tempmailstore1a kernel: eax: c02e35dc   ebx: c144ba58 
 ecx: f6acbed8   edx: c0146a64
Feb 28 14:40:53 tempmailstore1a kernel: esi: e386cc00   edi: c16848c8 
 ebp: 2002002c   esp: f6acbedc
Feb 28 14:40:53 tempmailstore1a kernel: ds: 007b   es: 007b   ss: 0068
Feb 28 14:40:53 tempmailstore1a kernel: Process nfsd (pid: 6512,
threadinfo=f6acb000 task=f7a16330)
Feb 28 14:40:53 tempmailstore1a kernel: Stack: c16848b8 c0146a64
c16848b8 c144b998 c16848b8 e386cc00 c16848c8 00000286
Feb 28 14:40:53 tempmailstore1a kernel:        c0146e84 e386cc00
bbfb9f0b fffffff5 f8e7cf20 f8e6ac04 00000000 f8e7eae4
Feb 28 14:40:53 tempmailstore1a kernel:        00000000 f7dd9b50
f7dd9a00 e386cc00 f6acbf55 f7dd9a00 f8e6923c c19f31f4
Feb 28 14:40:53 tempmailstore1a kernel: Call Trace:
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0146a64>]
cache_flusharray+0x1a/0x9c
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0146e84>] kfree+0x43/0x51
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6ac04>]
cache_check+0x11c/0x126 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6923c>]
svcauth_unix_set_client+0x68/0xb5 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e69561>]
svcauth_unix_accept+0x189/0x292 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6877f>]
svc_set_client+0x43/0x46 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e66292>]
svc_process+0x284/0x6ce [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8eb745a>] nfsd+0x1cc/0x332
[nfsd]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8eb728e>] nfsd+0x0/0x332
[nfsd]
Feb 28 14:40:53 tempmailstore1a kernel:  [<c01041f1>]
kernel_thread_helper+0x5/0xb
Feb 28 14:40:53 tempmailstore1a kernel: Code: 00 75 09 f0 81 02 00 00
00 01 30 c9 89 c8 c3 53 89 c3 81 78 04 ad 4e ad de 74 18 ff 74 24 04
68 dc 35 2e c0 e8 e
3 26 e5 ff 58 5a <0f> 0b 85 00 96 26 2e c0 f0 fe 0b 79 09 f3 90 80 3b
00 7e f9 eb
Feb 28 14:40:53 tempmailstore1a kernel:  ------------[ cut here ]------------
Feb 28 14:40:53 tempmailstore1a kernel: kernel BUG at
include/asm/spinlock.h:133!
Feb 28 14:40:53 tempmailstore1a kernel: invalid operand: 0000 [#2]
Feb 28 14:40:53 tempmailstore1a kernel: SMP
Feb 28 14:40:53 tempmailstore1a kernel: Modules linked in: nfs
iptable_filter ip_tables nfsd exportfs lockd sunrpc ip_vs drbd(U) md5
ipv6 autofs4 button batte
ry ac ohci_hcd tg3 floppy sg dm_snapshot dm_zero dm_mirror ext3 jbd
dm_mod megaraid_mbox megaraid_mm sd_mod scsi_mod
Feb 28 14:40:53 tempmailstore1a kernel: CPU:    1
Feb 28 14:40:53 tempmailstore1a kernel: EIP:    0060:[<c02cfb49>]   
Not tainted VLI
Feb 28 14:40:53 tempmailstore1a kernel: EFLAGS: 00010002   (2.6.9-22.0.1.ELsmp)
Feb 28 14:40:53 tempmailstore1a kernel: Fatal exception: panic in 5 seconds
Feb 28 14:40:53 tempmailstore1a kernel: eip: c0146a64
Feb 28 14:40:53 tempmailstore1a kernel: EIP is at _spin_lock+0x1c/0x34
Feb 28 14:40:53 tempmailstore1a kernel: eax: c02e35dc   ebx: c1470e58 
 ecx: c2ea1ed8   edx: c0146a64
Feb 28 14:40:53 tempmailstore1a kernel: esi: e386cc00   edi: c1470da8 
 ebp: 20000080   esp: c2ea1edc
Feb 28 14:40:53 tempmailstore1a kernel: ds: 007b   es: 007b   ss: 0068
Feb 28 14:40:53 tempmailstore1a kernel: Process nfsd (pid: 6513,
threadinfo=c2ea1000 task=f7b40130)
Feb 28 14:40:53 tempmailstore1a kernel: Stack: c1470d98 c0146a64
c1470d98 c1470d98 c1470d98 e386cc00 c1470da8 00000286
Feb 28 14:40:53 tempmailstore1a kernel:        c0146e84 e386cc00
bbfb9f0b fffffff5 f8e7cf20 f8e6ac04 00000000 f8e7eae4
Feb 28 14:40:53 tempmailstore1a kernel:        00000000 f519c350
f519c200 e386cc00 c2ea1f55 f519c200 f8e6923c c19f31f4
Feb 28 14:40:53 tempmailstore1a kernel: Call Trace:
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0146a64>]
cache_flusharray+0x1a/0x9c
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0146e84>] kfree+0x43/0x51
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6ac04>]
cache_check+0x11c/0x126 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6923c>]
svcauth_unix_set_client+0x68/0xb5 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e69561>]
svcauth_unix_accept+0x189/0x292 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6877f>]
svc_set_client+0x43/0x46 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e66292>]
svc_process+0x284/0x6ce [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8eb745a>] nfsd+0x1cc/0x332
[nfsd]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8eb728e>] nfsd+0x0/0x332
[nfsd]
Feb 28 14:40:53 tempmailstore1a kernel:  [<c01041f1>]
kernel_thread_helper+0x5/0xb
Feb 28 14:40:53 tempmailstore1a kernel: Code: 00 75 09 f0 81 02 00 00
00 01 30 c9 89 c8 c3 53 89 c3 81 78 04 ad 4e ad de 74 18 ff 74 24 04
68 dc 35 2e c0 e8 e
3 26 e5 ff 58 5a <0f> 0b 85 00 96 26 2e c0 f0 fe 0b 79 09 f3 90 80 3b
00 7e f9 eb
Feb 28 14:40:53 tempmailstore1a kernel:  ------------[ cut here ]------------
Feb 28 14:40:53 tempmailstore1a kernel: Fatal exception: panic in 5 seconds
Feb 28 14:40:53 tempmailstore1a kernel: kernel BUG at
include/asm/spinlock.h:133!
Feb 28 14:40:53 tempmailstore1a kernel: invalid operand: 0000 [#3]
Feb 28 14:40:53 tempmailstore1a kernel: SMP
Feb 28 14:40:53 tempmailstore1a kernel: Modules linked in: nfs
iptable_filter ip_tables nfsd exportfs lockd sunrpc ip_vs drbd(U) md5
ipv6 autofs4 button batte
ry ac ohci_hcd tg3 floppy sg dm_snapshot dm_zero dm_mirror ext3 jbd
dm_mod megaraid_mbox megaraid_mm sd_mod scsi_mod
Feb 28 14:40:53 tempmailstore1a kernel: CPU:    0
Feb 28 14:40:53 tempmailstore1a kernel: EIP:    0060:[<c02cfb49>]   
Not tainted VLI
Feb 28 14:40:53 tempmailstore1a kernel: EFLAGS: 00010002   (2.6.9-22.0.1.ELsmp)
Feb 28 14:40:53 tempmailstore1a kernel: EIP is at _spin_lock+0x1c/0x34
Feb 28 14:40:53 tempmailstore1a kernel: eax: c02e35dc   ebx: c144ba58 
 ecx: ca0cce98   edx: c0146a64
Feb 28 14:40:53 tempmailstore1a kernel: esi: e386cc00   edi: c16848c8 
 ebp: 2002002c   esp: ca0cce9c
Feb 28 14:40:53 tempmailstore1a kernel: ds: 007b   es: 007b   ss: 0068
Feb 28 14:40:53 tempmailstore1a kernel: Process rpc.mountd (pid: 6525,
threadinfo=ca0cc000 task=c1b182b0)
Feb 28 14:40:53 tempmailstore1a kernel: Stack: c16848b8 c0146a64
c16848b8 c144b998 c16848b8 e386cc00 c16848c8 00000286
Feb 28 14:40:53 tempmailstore1a kernel:        c0146e84 e386cc00
f7a1c5c0 440467fd ca0cceec f8e68d35 ca0ccefa 000000c0
Feb 28 14:40:53 tempmailstore1a kernel:        000000a8 00000018
00000014 bfe1109c f8e7ff66 31343131 34393331 00003335
Feb 28 14:40:53 tempmailstore1a kernel: Call Trace:
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0146a64>]
cache_flusharray+0x1a/0x9c
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0146e84>] kfree+0x43/0x51
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e68d35>]
ip_map_parse+0x194/0x1bc [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e68ba1>]
ip_map_parse+0x0/0x1bc [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<f8e6b741>]
cache_write+0xf8/0x115 [sunrpc]
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0159d24>] vfs_write+0xb6/0xe2
Feb 28 14:40:53 tempmailstore1a kernel:  [<c0159dee>] sys_write+0x3c/0x62
Feb 28 14:40:53 tempmailstore1a kernel:  [<c02d0fb7>] syscall_call+0x7/0xb
Feb 28 14:40:53 tempmailstore1a kernel:  [<c02d007b>]
__lock_text_end+0x232/0x100f
Feb 28 14:40:53 tempmailstore1a kernel: Code: 00 75 09 f0 81 02 00 00
00 01 30 c9 89 c8 c3 53 89 c3 81 78 04 ad 4e ad de 74 18 ff 74 24 04
68 dc 35 2e c0 e8 e
3 26 e5 ff 58 5a <0f> 0b 85 00 96 26 2e c0 f0 fe 0b 79 09 f3 90 80 3b
00 7e f9 eb
Feb 28 14:40:53 tempmailstore1a kernel:  <0>Fatal exception: panic in 5
seconds
Feb 28 14:40:53 tempmailstore1a kernel: Unable to handle kernel paging
request at virtual address 2b69616f
Feb 28 14:40:53 tempmailstore1a kernel:  printing eip:
Feb 28 14:40:53 tempmailstore1a kernel: f887eaa1
Feb 28 15:09:01 tempmailstore1a syslogd 1.4.1: restart.



Will.

Will McDonald wrote:
> What's the procedure for filing bug reports related to kernel panics
> on CentOS/RHEL? I've just had the following kernel panic on one of the
> new mailstores (argh!). Would this have to be reproduceable to warrant
> a bug report?
> 
yes, please include details on reproduction methods...

http://bugs.centos.org/

and/or also at http://bugzilla.redhat.com/ ( but if you bugzilla it with 
redhat, please also post something at bugs.centos.org and mention the 
bugzilla number. )

- KB

-- 
Karanbir Singh : http://www.karan.org/ : 2522219 at icq

On 2/28/06, Will McDonald <wmcdonald at gmail.com>
wrote:
> What's the procedure for filing bug reports related to kernel panics
> on CentOS/RHEL? I've just had the following kernel panic on one of the
> new mailstores (argh!). Would this have to be reproduceable to warrant
> a bug report?
For the upstream vendor, yes. If they can't duplicate the problem,
then the assumption is that it's something you screwed up locally.

Does it happen repeatedly to you during certain activity? How is the
system set up? any log activity around the time of the panic etc...

--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety''
Benjamin Franklin 1775