From: Scott Wood <scottwood@freescale.com>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: machine check in kernel for a mpc870 board
Date: Wed, 30 Jun 2010 11:16:53 -0500 [thread overview]
Message-ID: <4C2B6DF5.7030403@freescale.com> (raw)
In-Reply-To: <AANLkTik48Ht-jeq_U1yh9c9WzFYE8yYpALiz_N8SzF4N@mail.gmail.com>
On 06/30/2010 01:14 AM, Shawn Jin wrote:
> Hi Scott,
>
>>> Bus Fault @ 0x00404c40, fixup 0x00000000
>>> Machine check in kernel mode.
>>> Caused by (from msr): regs 07d1cb80 Unknown values in msr
>>> NIP: 00404C40 XER: 00000000 LR: 00404C24 REGS: 07d1cb80 TRAP: 0200 DAR: 00000001
>>> MSR: 00001002 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
>>
>> Can you look up the source line/instruction corresponding to 0x404c40, in
>> the wrapper ELF file?
>
> I'm not sure how to look up it.
Use a powerpc gdb on the wrapper ELF file, and do "li *0x404c40" and/or
"i li *0x404c40".
Or use a powerpc addr2line.
> But I used the BDI to dump the
> instructions in which you may find some clue? These should be kernel
> code, right? Maybe the gdb can help to de-assemble them?
Not easily (Format letter "i" is meaningless in "print" command, it
says...) and there'd be no context about what part of the source code it
corresponds to...
> 00404c40 : 0xa00a0000 -1609957376 ....
But this is a 16-bit load from r10, which is from your previous register
dump is FF0009C0.
Does u-boot on your board put IMMR somewhere other than 0xff000000? If
so, you'll need to update the device tree to reflect this.
-Scott
next prev parent reply other threads:[~2010-06-30 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 7:59 machine check in kernel for a mpc870 board Shawn Jin
2010-06-29 8:06 ` Joakim Tjernlund
2010-06-29 8:37 ` Shawn Jin
2010-06-29 18:56 ` Scott Wood
2010-06-30 6:14 ` Shawn Jin
2010-06-30 16:16 ` Scott Wood [this message]
2010-06-30 22:25 ` Shawn Jin
2010-07-01 7:50 ` Shawn Jin
2010-07-01 17:42 ` Scott Wood
2010-07-01 20:17 ` Shawn Jin
2010-07-01 20:25 ` Scott Wood
2010-07-02 17:06 ` Shawn Jin
2010-07-02 17:47 ` Scott Wood
2010-07-02 19:16 ` Shawn Jin
2010-07-02 19:41 ` Scott Wood
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=4C2B6DF5.7030403@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=shawnxjin@gmail.com \
/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.