All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Rovins <janr@adax.com>
To: linux-mips@linux-mips.org
Subject: Help with decoding a NMI Watchdog interrupt on an Octeon
Date: Thu, 17 Jun 2010 17:03:02 -0400	[thread overview]
Message-ID: <4C1A8D86.60005@adax.com> (raw)

Hi, I need some tips on how to go about deciphering the following NMI dump.

This is from a 2.6.21.7 kernel that came with the Cavium Networks 1.8.1 
toolchain.
Is there any way to get some kind of back trace from this, or just find 
out which function it was in?

I have been playing around with objdump -x vmlinux  but I cant zero in 
on anything this way.

Thanks in advance,

 Jan
*** NMI Watchdog interrupt on Core 0x6 ***
        $0      0x0000000000000000      at      0x000000001010cce0
        v0      0x000000000000003d      v1      0x000000000000024a
        a0      0xffffffff807d7b70      a1      0x0000000000000000
        a2      0x000000000000024a      a3      0x0000000000000000
        a4      0xffffffff807d7b60      a5      0x0000000000000080
        a6      0x0000000000000001      a7      0xa800000411c62578
        t0      0x0000000000000001      t1      0xa80000048ef3e880
        t2      0xffffffff82d40000      t3      0xa80000041f48c000
        s0      0xc0000000000d9640      s1      0xc000000000088028
        s2      0x0000000000000000      s3      0x0000000000000180
        s4      0x0000000000000000      s5      0x0000000000000000
        s6      0xb7a89c196f513832      s7      0x0000000000000000
        t8      0xffffffff807d0000      t9      0xffffffff807d0000
        k0      0x0000000000000000      k1      0x00000000104dbcbf
        gp      0xa80000041f48c000      sp      0xa80000041f48fcf0
        s8      0x0000000000000000      ra      0xc0000000023c5004
        epc     0xffffffff802b10b8
        status  0x000000001058cce4      cause   0x0000000040008c08
        sum0    0x0000002100000000      en0     0x0000009300008000
Code around epc
        0xffffffff802b10a8      000000002406ffff
        0xffffffff802b10ac      0000000064a5ffff
        0xffffffff802b10b0      0000000010a60005
        0xffffffff802b10b4      0000000000000000
        0xffffffff802b10b8      0000000080620000
        0xffffffff802b10bc      000000001440fffb
        0xffffffff802b10c0      0000000064630001
        0xffffffff802b10c4      000000006463ffff
        0xffffffff802b10c8      0000000003e00008

             reply	other threads:[~2010-06-17 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 21:03 Jan Rovins [this message]
2010-06-17 21:25 ` Help with decoding a NMI Watchdog interrupt on an Octeon David Daney
2010-06-17 21:26 ` Kevin D. Kissell
2010-06-17 21:51   ` David Daney
2010-06-19 19:13     ` Jan Rovins
2010-06-21  5:55       ` Jan Rovins
2010-06-21  5:55         ` Jan Rovins
2010-06-21 16:22         ` David Daney

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=4C1A8D86.60005@adax.com \
    --to=janr@adax.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.