On Tue, 24 Feb 2015, BERTRAND Joël wrote:
matthew green a écrit :
Hm. From what I remember, f000xxxx is inside OBP.
that's correct :-)
Instead of randomly swapping out hardware you really should try to
diagnose the problem. I'd turn on ddb and traptrace in the kernel and
examine the contents of the traptrace buffer after the panic. That should
tell us the sequence of traps that caused the panic.
FWIW, traptrace never was updated for SMP.
Will there a hope to quickly have a fix to obtain traptrace in syslog
? I'm trying to reproduce this bug on Blade 2000 I have at home without any
success.
Putting traptrace back in is not trivial. It basically involves taking
all of the traptrace code that was removed in locore.s version 1.214,
enhancing it for SMP, and reinserting it into locore.s. How good are your
SPARC assembly language skills?