Date: Thu, 8 Mar 2007 21:41:57 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Eirik ?verby <ltning@anduin.net> Cc: stable@freebsd.org Subject: Re: Panic: spin lock smp rendezvous ... held too long Message-ID: <20070309024157.GA58736@xor.obsecurity.org> In-Reply-To: <3FCD4E86-40CA-4E27-AF97-DFB94F02077C@anduin.net> References: <3FCD4E86-40CA-4E27-AF97-DFB94F02077C@anduin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF8Ml1Wry0BWjoQKURAqHxAJ4yIKMMi/z98VQvwFUdBo34Tc5GxQCdGo85 dC/rm5rIPeJuH49L9gtSEXk= =LAA+ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070309024157.GA58736>