From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 19:41:25 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 156FC1065671 for ; Tue, 15 Jul 2008 19:41:25 +0000 (UTC) (envelope-from jmc-freebsd@milibyte.co.uk) Received: from pih-relay05.plus.net (pih-relay05.plus.net [212.159.14.132]) by mx1.freebsd.org (Postfix) with ESMTP id C80B48FC12 for ; Tue, 15 Jul 2008 19:41:24 +0000 (UTC) (envelope-from jmc-freebsd@milibyte.co.uk) Received: from [84.92.153.232] (helo=curlew.milibyte.co.uk) by pih-relay05.plus.net with esmtp (Exim) id 1KIqOo-0003LE-MG for freebsd-questions@freebsd.org; Tue, 15 Jul 2008 20:41:22 +0100 Received: by curlew.milibyte.co.uk with local (Exim 4.69) (envelope-from ) id 1KIqOo-0000Lr-1R for freebsd-questions@freebsd.org; Tue, 15 Jul 2008 20:41:22 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Tue, 15 Jul 2008 20:41:21 +0100 User-Agent: KMail/1.9.7 References: <200807151422.02709.jmc-freebsd@milibyte.co.uk> <487CA937.2060307@FreeBSD.org> In-Reply-To: <487CA937.2060307@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807152041.21868.jmc-freebsd@milibyte.co.uk> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: jmc-freebsd@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-Plusnet-Relay: 45f2c25d5bfe1254c6c669676facd5f6 Subject: Re: Panic: spin lock held too long when booting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 19:41:25 -0000 On Tuesday 15 July 2008, Kris Kennaway wrote: > Mike Clarke wrote: > > I'm getting frequent panics due to spin lock held too long when > > booting my recently built 6.3 system with an Athlon 4850e dual core > > processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and > > nForce 430 chipsets). [snip] > You should add options WITNESS also and this will probably generate > additional debugging and/or a panic before the error occurs. OK, done that. The first reboot came up OK, sods law being what it is the next few boots will be clean and I'll have to wait a while for results from the next panic but in the meantime here's the messages generated by WITNESS for the clean boot: curlew:/home/mike% grep WITNESS /var/run/dmesg.boot WARNING: WITNESS option enabled, expect reduced performance. WITNESS: spin lock scrlock not in order list WITNESS: spin lock intrcnt not in order list WITNESS: spin lock ctl.rm_mtx not in order list WITNESS: spin lock dev.rm_mtx not in order list ... do they give any clues? -- Mike Clarke