Greetings

Kinda new to kernel programming so pardon any mis-steps

On 2.6.9-55.0-2.ELsmp during boot when the HP OpenView agent opcagt is launched the kernel panics (oops below)

My take on the oops is that opcnls caused the problem when it called futex_wait to 0x65 bytes into futex_wait function which is 0xc5 bytes in length. I understand the whole concept of futex/mutex etc ... without prodding too much does this look like possibly the opcnls was trying to read a peice of data that during which time it was reading it, it was being overwritten by another proc, thus causing mutex to fail ... or is this opcnls was trying to wake/wait (futex_wake) and it could not do such

Is there a way to tell if the problem was caused by opcnls or was opcnls just the victim of another thread that wouldn't release it's lock on what opcnls wanted to access in a timely manner so it caused the panic ... also, I thought futexs allowed for there not to be any kernel space interaction, or does the kernel space syscall step in when there is a conflict over a futex and it tries to resolve it, if it can't, it panics?

Sorry for the "all-over-the-place" of this post


Apr 18 05:19:28 lx4-lix kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Apr 18 05:19:28 lx4-lix kernel: printing eip:
Apr 18 05:19:28 lx4-lix kernel: c0134df6
Apr 18 05:19:28 lx4-lix kernel: *pde = 35d14001
Apr 18 05:19:28 lx4-lix kernel: Oops: 0000 [#1]
Apr 18 05:19:28 lx4-lix kernel: SMP
Apr 18 05:19:28 lx4-lix kernel: Modules linked in: md5 ipv6 parport_pc lp parport autofs4 sunrpc microcode dm_multipath joydev uhci_hcd ehci_hcd nvidia(U) i2c_core snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore tg3 floppy dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod ata_piix libata mptscsih mptsas mptspi mptscsi mptbase sd_mod scsi_mod
Apr 18 05:19:28 lx4-lix kernel: CPU: 0
Apr 18 05:19:28 lx4-lix kernel: EIP: 0060:[<c0134df6>] Tainted: P VLI
Apr 18 05:19:28 lx4-lix kernel: EFLAGS: 00010203 (2.6.9-55.0.2.ELsmp)
Apr 18 05:19:28 lx4-lix kernel: EIP is at futex_wake+0x65/0xc5
Apr 18 05:19:28 lx4-lix kernel: eax: c043db74 ebx: c043db74 ecx: 0000e260 edx: 00000000
Apr 18 05:19:28 lx4-lix kernel: esi: 00000000 edi: 007013d8 ebp: c043db80 esp: f5d13f5c
Apr 18 05:19:28 lx4-lix kernel: ds: 007b es: 007b ss: 0068
Apr 18 05:19:28 lx4-lix kernel: Process opcnls (pid: 4007, threadinfo=f5d13000 task=f73a2c30)
Apr 18 05:19:28 lx4-lix kernel: Stack: 7fffffff 00701000 f5dd6680 000003d8 c0150f3a 007013d8 00000001 00000000
Apr 18 05:19:28 lx4-lix kernel: f5d13000 c0135597 007013d8 00000000 00d93220 c01356c0 7fffffff 00d93220
Apr 18 05:19:28 lx4-lix kernel: 00000000 bffffaf8 00000000 00c85ff4 00000006 007013d8 00000000 00d93220
Apr 18 05:19:28 lx4-lix kernel: Call Trace:
Apr 18 05:19:28 lx4-lix kernel: [<c0150f3a>] do_brk+0x1f0/0x22a
Apr 18 05:19:28 lx4-lix kernel: [<c0135597>] do_futex+0x32/0x5a
Apr 18 05:19:28 lx4-lix kernel: [<c01356c0>] sys_futex+0x101/0x10c
Apr 18 05:19:28 lx4-lix kernel: [<c02d6093>] syscall_call+0x7/0xb

Apr 18 05:19:28 lx4-lix kernel: Code: 00 00 8d 5c 24 04 89 f8 89 da e8 44 fe ff ff 85 c0 89 c6 75 50 89 d8 e8 ad fd ff ff 89 c3 8d 6b 0c e8 da fd 19 00 8b 53 0c 39 ea <8b> 3a 74 2f 8b 44 24 04 8d 4a 1c 39 42 1c 75 1f 8b 44 24 08 39
Apr 18 05:19:28 lx4-lix kernel: <0>Fatal exception: panic in 5 seconds