From: "mike zheng" <mail4mz@gmail.com>
To: "Andy Fleming" <afleming@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: System crash on boot_e500.S on 2.4Kernel
Date: Thu, 16 Aug 2007 10:37:47 -0400 [thread overview]
Message-ID: <5c9cd53b0708160737u5dc174a0q9433a6e4d2ee0afd@mail.gmail.com> (raw)
In-Reply-To: <8513767D-F467-49EA-816B-48567E13F56D@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On 8/15/07, Andy Fleming <afleming@freescale.com> wrote:
>
>
> On Aug 15, 2007, at 17:46, mike zheng wrote:
>
> > Hi Andy,
> >
> > Here is BDI output of the register value after line 212. The value
> > of R6, R7 is 0x20, 0x160. However the value of SRR0(SPR26), SRR1
> > (SPR27) is 0xfff81300 and 0x00001000. Why are they different from
> > r7 and r6? We just did the mtspr, the value should be the same. The
> > rfi jump to 0xfff81300 is because of the value in SRR0.
>
>
> Yes, it's very strange. But it's also pretty much impossible for the
> mtspr to just fail like that. A more likely scenario is that the BDI
> is getting bad information. Could you take a look at your IVORs?
> I'm very curious to see if fff81300 is an interrupt vector.
Now I know the BDI need debug vector to be set properly. I manually change
the IVPR and IVOR15 for BDI, and will update you the progress.
Andy
>
[-- Attachment #2: Type: text/html, Size: 1401 bytes --]
prev parent reply other threads:[~2007-08-16 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 20:21 System crash on boot_e500.S on 2.4Kernel mike zheng
2007-08-14 20:38 ` Andy Fleming
2007-08-15 13:59 ` mike zheng
2007-08-15 16:17 ` Becky Bruce
2007-08-15 21:12 ` mike zheng
2007-08-15 22:06 ` Andy Fleming
2007-08-15 22:46 ` mike zheng
2007-08-16 1:16 ` Andy Fleming
2007-08-16 14:37 ` mike zheng [this message]
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=5c9cd53b0708160737u5dc174a0q9433a6e4d2ee0afd@mail.gmail.com \
--to=mail4mz@gmail.com \
--cc=afleming@freescale.com \
--cc=linuxppc-embedded@ozlabs.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 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).