From owner-freebsd-questions@FreeBSD.ORG Sun Mar 20 23:21:12 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E80D716A4CE for ; Sun, 20 Mar 2005 23:21:12 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70B7F43D48 for ; Sun, 20 Mar 2005 23:21:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id EE76753C90; Sun, 20 Mar 2005 15:21:04 -0800 (PST) Date: Sun, 20 Mar 2005 15:21:04 -0800 From: Kris Kennaway To: Gerard Meijer Message-ID: <20050320232104.GA18079@xor.obsecurity.org> References: <016201c52d23$b18e5e90$9600000a@guus> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <016201c52d23$b18e5e90$9600000a@guus> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: server crash "panic: spin lock held too long" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 23:21:13 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 20, 2005 at 09:06:17AM +0100, Gerard Meijer wrote: > Hi I have a P4 2.6Mhz running on FreeBSD 5.3. >=20 > Every few days the server crashes. When it crashes it says: >=20 > spin lock sleepq chain held by 0xc1eb7640 for > 5 seconds > panic: spin lock held too long > Uptime: 2d3h56m36s >=20 > Anybody any idea how I can fix this? See the chapter on kernel debugging in the developers' handbook to learn how to obtain the necessary information for a developer to begin investigating this. Also make sure you're running with all of the 5.3 errata patches, and consider updating to 5.4-PRERELEASE to see if it's fixed already. Kris --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCPgVgWry0BWjoQKURAmdUAKDQkpXr46YWjY05EsWZJ0+WQjerFwCfZBK0 Frmeho2j7uhvCjzt7gV/xGA= =fSU0 -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g--