wierd bug, help decoding sysrq output?

[Chris Friesen]

I'm looking for some help decoding an x86 stack trace.

We have a process showing as defunct, but its parent is listed as init. 
 It shows up in top as using basically 100% cpu, and one cpu out of 
four is showing spending all its time in "sys".

Dumping all tasks via sysrq gave the following information for the 
affected process:


oamFmLogServe X C8A5E610     0 23551      1         23553 20706 (L-TLB)
ee45fe58 00000046 c8a5ebf0 c8a5e610 00000a3c 00000000 00000003 c04cfb74
       f91a919f c01406ce c8a5ebf0 00000000 c8a5e610 c515c060 00000001 
00000174
       e132a861 00000a3c c8a5e610 c8a5ebf0 c8a5ed64 00005bff c8a5e610 
00000020
Call Trace:
 [<c011e742>] do_exit+0x31e/0x48a
 [<c011e95e>] do_group_exit+0x3a/0xa9
 [<c01277d1>] get_signal_to_deliver+0x21f/0x342
 [<c010238a>] do_signal+0x72/0x12f
 [<c0102482>] do_notify_resume+0x3b/0x3d
 [<c010265e>] work_notifysig+0x13/0x15


Disassembling vmlinux gives:

0xc011e73d <do_exit+793>:       call   0xc046194c <schedule>
0xc011e742 <do_exit+798>:       ud2a

I haven't been able to find any kernel code that would match up to a 
program counter of "C8A5E610".

Anyone have any ideas?

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/