freebsd stable - Mar 2007 - Panic: spin lock smp rendezvous ... held too long

Hi all,

I just installed 6.2-RELEASE on a Supermicro 6013P-8 server, a dual  
P4-Xeon 2.4ghz with 4GB ECC memory and an asr driven SCSI RAID  
controller.

It has been working OK (although I suspect the asr driven, being  
giant-locked, is very inefficient) for a little while, but as I was  
extracting a bunch of tarballs it paniced like so:

spin lock smp rendezvous held by 0xc9d54600 for > 5 seconds
panic: spin lock held too long
cpuid = 0

I don't have a dump device (though I'm setting that up for the next  
reboot). However, I have tried turning off HT, to see if that might  
help.

Does this look familiar to anyone? Or do I need to produce more data  
if it happens again?

Thanks,
/Eirik

On Fri, Mar 09, 2007 at 12:44:03AM +0100, Eirik ?verby
wrote:
> Hi all,
> 
> I just installed 6.2-RELEASE on a Supermicro 6013P-8 server, a dual  
> P4-Xeon 2.4ghz with 4GB ECC memory and an asr driven SCSI RAID  
> controller.
> 
> It has been working OK (although I suspect the asr driven, being  
> giant-locked, is very inefficient) for a little while, but as I was  
> extracting a bunch of tarballs it paniced like so:
> 
> spin lock smp rendezvous held by 0xc9d54600 for > 5 seconds
> panic: spin lock held too long
> cpuid = 0
> 
> I don't have a dump device (though I'm setting that up for the next
> reboot). However, I have tried turning off HT, to see if that might  
> help.
> 
> Does this look familiar to anyone? Or do I need to produce more data  
> if it happens again?
It can mean that something deadlocked.  Turning on WITNESS may help to
debug this, although it has a large performance impact.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070309/fd98a46e/attachment.pgp