Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jul 2008 20:41:21 +0100
From:      Mike Clarke <jmc-freebsd@milibyte.co.uk>
To:        freebsd-questions@freebsd.org
Subject:   Re: Panic: spin lock held too long when booting
Message-ID:  <200807152041.21868.jmc-freebsd@milibyte.co.uk>
In-Reply-To: <487CA937.2060307@FreeBSD.org>
References:  <200807151422.02709.jmc-freebsd@milibyte.co.uk> <487CA937.2060307@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807152041.21868.jmc-freebsd>