System crash on boot_e500.S on 2.4Kernel

mike zheng mail4mz at
Fri Aug 17 00:37:47 EST 2007

On 8/15/07, Andy Fleming <afleming at> 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.

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Linuxppc-embedded mailing list