troubleshooting Question

Red Hat Enterprise 4.0 kernel panic

Avatar of rheckman1
rheckman1 asked on
Operating SystemsLinux Distributions
5 Comments1 Solution1059 ViewsLast Modified:
Kernel 2.6.9-11.ELsmp

My system panic'd last night, tried a reboot, panic'd again and stopped trying.  A simple reset this morning brought it back up with no issues.

Limiited experience reading redhat crash logs, but it looks like this is a software issue as there is a line that says:

kernel BUG at include/asm/spinlock.h:146

Apologize in advance for the long paste, but this is what I need help deciphering.

Feb 21 04:02:02 imagehost-fl kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000c
Feb 21 04:02:02 imagehost-fl kernel:  printing eip:
Feb 21 04:02:02 imagehost-fl kernel: c01b6959
Feb 21 04:02:02 imagehost-fl kernel: *pde = 1737b001
Feb 21 04:02:02 imagehost-fl kernel: Oops: 0000 [#1]
Feb 21 04:02:02 imagehost-fl kernel: SMP
Feb 21 04:02:02 imagehost-fl kernel: Modules linked in: parport_pc lp parport autofs4 i2c_dev i2c_core nfs nfsd exportfs lockd sunrpc md5 ipv6 dm_mod button battery ac uhci_hcd ehci_hcd e1000 e100 mii floppy ext3 jbd ata_piix libata 3w_xxxx sd_mod scsi_mod
Feb 21 04:02:02 imagehost-fl kernel: CPU:    1
Feb 21 04:02:02 imagehost-fl kernel: EIP:    0060:[<c01b6959>]    Not tainted VLI
Feb 21 04:02:02 imagehost-fl kernel: EFLAGS: 00010246   (2.6.9-11.ELsmp)
Feb 21 04:02:02 imagehost-fl kernel: EIP is at rb_insert_color+0x19/0xc1
Feb 21 04:02:02 imagehost-fl kernel: eax: f62e4708   ebx: f62e4408   ecx: 936ddd74   edx: f53c1d80
Feb 21 04:02:02 imagehost-fl kernel: esi: 00000000   edi: f62e4708   ebp: f53c1d80   esp: c413fe28
Feb 21 04:02:02 imagehost-fl kernel: ds: 007b   es: 007b   ss: 0068
Feb 21 04:02:02 imagehost-fl kernel: Process sh (pid: 3210, threadinfo=c413f000 task=f6094830)
Feb 21 04:02:02 imagehost-fl kernel: Stack: f62e4700 f62e4400 f62e4725 f62e4410 f889fa7d f53c1d80 f62e4408 b2fe3513
Feb 21 04:02:02 imagehost-fl kernel:        936ddd74 f16ed0cc e8e6ca70 f16edff8 c413fec0 f88a4b3c f16ed0cc 0000000e
Feb 21 04:02:02 imagehost-fl kernel:        c74d8380 00000000 00000000 f5ae2320 f53c1d80 c74d8380 f88a4bd5 c413fec0
Feb 21 04:02:02 imagehost-fl kernel: Call Trace:
Feb 21 04:02:02 imagehost-fl kernel:  [<f889fa7d>] ext3_htree_store_dirent+0x147/0x151 [ext3]
Feb 21 04:02:02 imagehost-fl kernel:  [<f88a4b3c>] htree_dirblock_to_tree+0x78/0xb6 [ext3]
Feb 21 04:02:02 imagehost-fl kernel:  [<f88a4bd5>] ext3_htree_fill_tree+0x5b/0x176 [ext3]
Feb 21 04:02:02 imagehost-fl kernel:  [<f889fc4e>] ext3_dx_readdir+0x112/0x198 [ext3]
Feb 21 04:02:02 imagehost-fl kernel:  [<c0165ee0>] filldir64+0x0/0x11a
Feb 21 04:02:02 imagehost-fl kernel:  [<f889f551>] ext3_readdir+0x8c/0x3a0 [ext3]
Feb 21 04:02:02 imagehost-fl kernel:  [<c0165ee0>] filldir64+0x0/0x11a
Feb 21 04:02:02 imagehost-fl kernel:  [<c0165ee0>] filldir64+0x0/0x11a
Feb 21 04:02:02 imagehost-fl kernel:  [<c0165c1d>] vfs_readdir+0x7d/0xa5
Feb 21 04:02:02 imagehost-fl kernel:  [<c016605f>] sys_getdents64+0x65/0x9f
Feb 21 04:02:02 imagehost-fl kernel:  [<c02c7377>] syscall_call+0x7/0xb
Feb 21 04:02:02 imagehost-fl kernel: Code: 75 05 89 50 08 eb 07 89 50 0c eb 02 89 13 89 11 5b c3 55 89 d5 57 89 c7 56 53 e9 9b 00 00 00 83 7b 04 00 0f 85 9b 00 00 00 8b 33 <8b> 46 0c 39 c3 75 3a 8b 46 08 85 c0 74 06 83 78 04 00 74 37 39
Feb 21 04:02:02 imagehost-fl kernel:  <0>Fatal exception: panic in 5 seconds
Feb 21 04:02:02 imagehost-fl kernel: eip: c011f619
Feb 21 04:02:02 imagehost-fl kernel: ------------[ cut here ]------------
Feb 21 04:02:02 imagehost-fl kernel: kernel BUG at include/asm/spinlock.h:146!
Feb 21 04:02:02 imagehost-fl kernel: invalid operand: 0000 [#2]
Feb 21 04:02:02 imagehost-fl kernel: SMP
Feb 21 04:02:02 imagehost-fl kernel: Modules linked in: parport_pc lp parport autofs4 i2c_dev i2c_core nfs nfsd exportfs lockd sunrpc md5 ipv6 dm_mod button battery ac uhci_hcd ehci_hcd e1000 e100 mii floppy ext3 jbd ata_piix libata 3w_xxxx sd_mod scsi_mod
Feb 21 04:02:02 imagehost-fl kernel: CPU:    0
Feb 21 04:02:02 imagehost-fl kernel: EIP:    0060:[<c02c5fa5>]    Not tainted VLI
Feb 21 04:02:02 imagehost-fl kernel: EFLAGS: 00010046   (2.6.9-11.ELsmp)
Feb 21 04:02:02 imagehost-fl kernel: EIP is at _spin_lock_irqsave+0x20/0x45
Feb 21 04:02:02 imagehost-fl kernel: eax: c011f619   ebx: 00000246   ecx: c02d972a   edx: c02d972a
Feb 21 04:02:02 imagehost-fl kernel: esi: f62e4540   edi: 00000001   ebp: f610b590   esp: c4a92ed0
Feb 21 04:02:02 imagehost-fl kernel: ds: 007b   es: 007b   ss: 0068
Feb 21 04:02:02 imagehost-fl kernel: Process applydate (pid: 3211, threadinfo=c4a92000 task=e2907930)
Feb 21 04:02:02 imagehost-fl kernel: Stack: c4a92f10 f62e4540 c011f619 f610b600 c4a92f10 c4a92f04 f610b590 c0160246
Feb 21 04:02:02 imagehost-fl kernel:        00000000 e2907930 c011f6ee c4a92f1c c4a92f1c 000fc02f 000081a4 00000001
Feb 21 04:02:02 imagehost-fl kernel:        00000000 e2907930 c011f6ee c4a92f1c c4a92f1c 00000246 00000000 f610b600
Feb 21 04:02:02 imagehost-fl kernel: Call Trace:
Feb 21 04:02:02 imagehost-fl kernel:  [<c011f619>] prepare_to_wait+0x12/0x4c
Feb 21 04:02:02 imagehost-fl kernel:  [<c0160246>] pipe_wait+0x5a/0xa2
Feb 21 04:02:02 imagehost-fl kernel:  [<c011f6ee>] autoremove_wake_function+0x0/0x2d
Feb 21 04:02:02 imagehost-fl kernel:  [<c011f6ee>] autoremove_wake_function+0x0/0x2d
Feb 21 04:02:02 imagehost-fl kernel:  [<c01604b3>] pipe_readv+0x225/0x29e
Feb 21 04:02:02 imagehost-fl kernel:  [<c0160548>] pipe_read+0x1c/0x20
Feb 21 04:02:02 imagehost-fl kernel:  [<c0156011>] vfs_read+0xb6/0xe2
Feb 21 04:02:02 imagehost-fl kernel:  [<c0156224>] sys_read+0x3c/0x62
Feb 21 04:02:02 imagehost-fl kernel:  [<c02c7377>] syscall_call+0x7/0xb
Feb 21 04:02:02 imagehost-fl kernel: Code: 81 00 00 00 00 01 c3 f0 ff 00 c3 56 89 c6 53 9c 5b fa 81 78 04 ad 4e ad de 74 18 ff 74 24 08 68 2a 97 2d c0 e8 33 ba e5 ff 59 58 <0f> 0b 92 00 4f 88 2d c0 f0 fe 0e 79 13 f7 c3 00 02 00 00 74 01
Feb 21 04:02:02 imagehost-fl kernel:  <0>Fatal exception: panic in 5 seconds
Feb 21 08:39:27 imagehost-fl syslogd 1.4.1: restart.

Any and all help would be greatly appreciated.

Thanks
Rick
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 5 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros