Re: panic on dual processor UltraSPARC-IIIi

[Bert Kiers <kiers%original.xs4all.nl@localhost>]

On Thu, Jan 14, 2010 at 08:58:12PM -0500, Michael wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> On Jan 14, 2010, at 8:55 PM, Chris Ross wrote:
> 
> >
> >On Jan 14, 2010, at 18:08, Bert Kiers wrote:
> >>cpu0: shutting down
> >>rebooting
> >>
> >>How do you get into debugger to enter "bt" on sparc64?
> >
> > For the most part, you should likely build a kernel that's  
> >configured to drop into ddb on panic.  If you need it to reboot  
> >without a human, then it's not good, but...
> >
> > Apologies for not knowing which kernel options you need to use off  
> >of the top of my head.  Just wanted to offer the advice sooner  
> >rather than later.
> 
> To enter ddb on panic:
> sysctl -w ddb.onpanic=1
> And to automatically run bt in case keyboard access is hosed:
> sysctl -w ddb.commandonenter=bt

Thanks!

That resulted in a successful "build.sh tools", but after that, the
"build.sh release" ended with:

panic: fpusave_lwp ipi didn't
Stopped in pid 20135.1 (nbsed) at       netbsd:cpu_Debugger+0x4:        nop
fpusave_lwp(13169020, 1, badcafe, badcafe, badcafe, badcafe) at 
netbsd:fpusave_lwp+0x134
trap(1349ded0, 20, 4030bab8, 44820082, badcafe, badcafe) at netbsd:trap+0xafc
?(4020a200, 0, 1a0, 0, 4020a200, badcafe) at 0x1009070

That was after 13 hours uptime. Does this help anyone?

Grtnx,
-- 
Bert Kiers, !MCSE && 0xFF, frique d'ordinateur
gsm: +31(0)651589085  mailto: kiers%original.xs4all.nl@localhost
icbm: 52 18.56N  4 58.79E  PGPkeyID: f7e721ab