From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 20:03:01 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 7E2BD1065676 for ; Tue, 15 Jul 2008 20:03:01 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1B26E8FC08; Tue, 15 Jul 2008 20:02:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <487D0276.5010607@FreeBSD.org> Date: Tue, 15 Jul 2008 22:03:02 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Mike Clarke References: <200807151422.02709.jmc-freebsd@milibyte.co.uk> <487CA937.2060307@FreeBSD.org> <200807152041.21868.jmc-freebsd@milibyte.co.uk> In-Reply-To: <200807152041.21868.jmc-freebsd@milibyte.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org 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 20:03:01 -0000 Mike Clarke wrote: > 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? > Not really, they are basically just advisory in this context (and fixed in later releases AFAIK). Unfortunately WITNESS can drastically change timing of events which can mask this kind of problem. If you can afford it, keep trying with it enabled for a while. Kris