Re: Left Bliz1230mkIV compiling, found it had crashed.

[Roc Vallès <vallesroc%gmail.com@localhost>]

Crashed again (having left it compiling). This time I took some pictures.

See http://b.rvalles.net/unsorted/netbsd/

(Compiling_panic)

On Thu, Dec 5, 2013 at 8:14 AM, Roc Vallès <vallesroc%gmail.com@localhost> 
wrote:
> AmigaOS is now having fun unpacking AROS's contrib .tar.bz2... whoever
> at AROS thought bz2 was a good idea for the Amiga native port...
>
> Meanwhile, I built a kernel with DEBUG and -g and copied it, .gdb and
> .map to the Amiga. Once this unpacking ends, I'll boot netbsd, edit
> sysctl.conf, reproduce the Xamiga-induced panic, take a photo of the
> backtrace then, dump core from ddb (if I can figure out how), coldboot
> again (blizkick with areas outside MPROM = crash on reboot after
> netbsd or linux or anything that screws its MMU tables), look at the
> new core and post again.
>
> On Thu, Dec 5, 2013 at 7:45 AM, Radoslaw Kujawa
> <radoslaw.kujawa%c0ff33.net@localhost> wrote:
>>
>> On 5 Dec 2013, at 06:45, Roc Vallès <vallesroc%gmail.com@localhost> wrote:
>>
>>> And it seems eerie similar to the Xamiga-induced crash log.
>>
>> I wonder what was the original panic message when it died. Can you set 
>> ddb.onpanic to 1 in /etc/sysctl.conf, reload sysctl variables and try to 
>> repeat the crash? It should stop at the debugger prompt instead of dumping 
>> core and reboot.
>>
>> Dying in sleepq_block seems most suspicious. I never saw a crash like this 
>> before. I should also try to reproduce this on my A1200, but I need some 
>> time.
>>
>> --
>> Best regards,
>> Radoslaw Kujawa
>>
>>
>>