From owner-freebsd-stable@FreeBSD.ORG Fri Mar 9 02:41:58 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBDB216A404 for ; Fri, 9 Mar 2007 02:41:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id AAD8313C471 for ; Fri, 9 Mar 2007 02:41:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7D2B71A3C19; Thu, 8 Mar 2007 18:41:58 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C4EF1515A5; Thu, 8 Mar 2007 21:41:57 -0500 (EST) Date: Thu, 8 Mar 2007 21:41:57 -0500 From: Kris Kennaway To: Eirik ?verby Message-ID: <20070309024157.GA58736@xor.obsecurity.org> References: <3FCD4E86-40CA-4E27-AF97-DFB94F02077C@anduin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <3FCD4E86-40CA-4E27-AF97-DFB94F02077C@anduin.net> User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org Subject: Re: Panic: spin lock smp rendezvous ... held too long X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2007 02:41:58 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 09, 2007 at 12:44:03AM +0100, Eirik ?verby wrote: > Hi all, >=20 > I just installed 6.2-RELEASE on a Supermicro 6013P-8 server, a dual =20 > P4-Xeon 2.4ghz with 4GB ECC memory and an asr driven SCSI RAID =20 > controller. >=20 > It has been working OK (although I suspect the asr driven, being =20 > giant-locked, is very inefficient) for a little while, but as I was =20 > extracting a bunch of tarballs it paniced like so: >=20 > spin lock smp rendezvous held by 0xc9d54600 for > 5 seconds > panic: spin lock held too long > cpuid =3D 0 >=20 > I don't have a dump device (though I'm setting that up for the next =20 > reboot). However, I have tried turning off HT, to see if that might =20 > help. >=20 > Does this look familiar to anyone? Or do I need to produce more data =20 > 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 --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF8Ml1Wry0BWjoQKURAqHxAJ4yIKMMi/z98VQvwFUdBo34Tc5GxQCdGo85 dC/rm5rIPeJuH49L9gtSEXk= =LAA+ -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb--