Re: Ultrasparc III+ kernel panic

Eduardo Horvath a écrit :
> On Tue, 24 Feb 2015, BERTRAND Joël wrote:
>
>> Eduardo Horvath a écrit :
>>> 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?
>>
>> 	I haven't written sparc assembly for a very long time (and only on
>> sparc32...) :-(
>>
>> 	I can try to do something, but I'm not sure I have required knowledge
>> to do that without help.
>
> I can give you some advice, but I don't have the time or easy access to
> the hardware to re-implement traptrace.

	I will try to add code you give as soon as possible.

	I have set ddb.onpanic=1. When kernel panics, it enters in ddb, but 
console does not respond. I only obtain :

cpu data fault: pc=f000a4b4 rpc=102dfae50 addr=1ffeec000
kernel trap 30: data access exception
Stopped in pid 23349,1 (netstat) at f000a4b4: ld [%g4 + 0x0], %g4
db{1}>

	Console is dead, I cannot obtain any backtrace :-(

	Regards,

	JKB