Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Feb 2006 10:14:26 +0200
From:      Giorgos Keramidas <keramida@ceid.upatras.gr>
To:        Gleb Smirnoff <glebius@FreeBSD.org>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: insta-panic in softclock() -> acctwatch()
Message-ID:  <20060213081426.GA1147@flame.pc>
In-Reply-To: <20060213080854.GY86448@FreeBSD.org>
References:  <20060212233636.GA1005@flame.pc> <20060213080854.GY86448@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-02-13 11:08, Gleb Smirnoff <glebius@FreeBSD.org> wrote:
> On Mon, Feb 13, 2006 at 01:36:36AM +0200, Giorgos Keramidas wrote:
> G> I've finally managed to catch one of the panics of a 2006.01.25 kernel
> G> in action, while working on the console.  Unfortunately, not with a
> G> debugging kernel, but the function backtrace was:
> G>
> G>     panic()
> G>     sleepq_add()
> G>     cv_wait_unlock()
> G>     cv_wait()
> G>     _sx_xlock()
> G>     acctwatch()
> G>     softclock()
> G>
> G> This went away after I disabled process accounting in `rc.conf', but it
> G> may help someone more experienced with process accounting to find a
> G> better fix :)
>
> AFAIK, John has fixed this recently. Check whether you have last revision
> of kern_acct.c

Thanks :)

I quite probably don't.  I haven't been able to use a recent HEAD build
since around January 20, but I'm rebuilding since half an hour ago.




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