LKML Archive on
help / color / mirror / Atom feed
From: "Chris Friesen" <>
Subject: wierd bug, help decoding sysrq output?
Date: Mon, 19 Feb 2007 15:12:53 -0600	[thread overview]
Message-ID: <> (raw)

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 
        e132a861 00000a3c c8a5e610 c8a5ebf0 c8a5ed64 00005bff c8a5e610 
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?


                 reply	other threads:[~2007-02-19 21:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: wierd bug, help decoding sysrq output?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).