Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Jan 2006 15:49:58 +0000 (GMT)
From:      Chris Hedley <cbh-freebsd-current@groups.chrishedley.com>
To:        current@freebsd.org
Cc:        freebsd-current@freebsd.org
Subject:   Re: -CURRENT spontaneously rebooting when using X
Message-ID:  <20060126154605.C54781@aga.cbhnet>
In-Reply-To: <20060124171443.X94816@teapot.cbhnet>
References:  <20060123112629.F79825@teapot.cbhnet> <200601231624.14321.jhb@freebsd.org> <20060124100055.B84257@teapot.cbhnet> <200601241045.06880.jhb@freebsd.org> <20060124171443.X94816@teapot.cbhnet>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Jan 2006, Chris Hedley wrote:
> On Tue, 24 Jan 2006, John Baldwin wrote:
>> On Tuesday 24 January 2006 05:03, Chris Hedley wrote:
>>> On Mon, 23 Jan 2006, John Baldwin wrote:
>>>> It's a bug, but you can try this workaround:
>>> 
>>> Unfortunately that caused my system to lock up at (presumably) the same
>>> point it was crashing before; testing it a couple of times produced the
>>> same result.  Is there anything you want me to do to try to extract some
>>> more details from it?
>> 
>> Ah, sorry then.  The bug is that some thread has gone to sleep while 
>> holding a
>> mutex and now another thread wants that mutex.  Try turning on witness as 
>> it
>> will tell you when the first thread goes to sleep (the real bug).
>
> I've done that, and (perhaps unhelpfully) ran cvsup before rebuilding, so one 
> or the other has fixed my problem somehow.  When I'm feeling brave enough 
> I'll turn off witness again and see if the problem returns; I'll report back 
> if it does...

Just to close this one down, I turned off witness again and the problem 
didn't come back, so it looks like I must've just cvsuped the kernel at a 
bad time.  It feels like it's quite solid now, whatever I chuck at it.

Cheers,

Chris.



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