Finalizing device tree... using OF tree (promptr=0e1004c4)
( 700 ) Program Exception [ e1004c4 ]
The program check exception happens at 0xe1004c4 ? That looks like the
OF entry point (promptr)... could it be possible that it got corrupted
somewhat ? The only thing I see above there would be the stack but
I fail to see how it would use that much...
I don't know what this [ e1004c4 ] is, if I read the current public
SLOF code (for JS2x) correctly it seems to be whatever was on the
stack (or just below the stack) below the error code that was thrown.
Maybe some errors put something interesting there, dunno.
/me looks deeper... Nastiness :-) So, a decrementer exception gives
the current decrementer value as reason code; an external exception
reads some BE-specific registers (on any system!); and all other
exceptions use whatever was in GPR4?
Anyway, the register dump shows:
CR / XER LR / CTR SRR0 / SRR1 DAR /
DSISR
80000022 00000000014073e8 000000000189e99c
0000000000000000
0000000020000000 0000000001400000 9000000000083000 00000000
so SRR0 is 0189e99c, which is where the exception happened. Does
objdump show what's going on? It seems to happen almost immediately
after the kernel starts, given the CTR value. If the SRR0 address
doesn't help, the LR address should.
I have tried it with gcc-3.4.2, gcc-4.1.1 and gcc-4.2.4.
The binutils version is more interesting here. 2.18?
Segher
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
