From owner-freebsd-current@FreeBSD.ORG  Sun Jan  1 01:15:15 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5984D16A41F
	for <freebsd-current@freebsd.org>; Sun,  1 Jan 2006 01:15:15 +0000 (GMT)
	(envelope-from rmtodd@ichotolot.servalan.com)
Received: from mx2.synetsystems.com (mx2.synetsystems.com [216.226.140.79])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4EF9D43D58
	for <freebsd-current@freebsd.org>; Sun,  1 Jan 2006 01:15:13 +0000 (GMT)
	(envelope-from rmtodd@ichotolot.servalan.com)
Received: by mx2.synetsystems.com (Postfix, from userid 66)
	id E766534C; Sat, 31 Dec 2005 20:15:12 -0500 (EST)
Received: from rmtodd by servalan.servalan.com with local (Exim 4.60 (FreeBSD))
	(envelope-from <rmtodd@ichotolot.servalan.com>)
	id 1EsrFz-00003Z-Uq; Sat, 31 Dec 2005 18:39:32 -0600
To: "Wojciech A. Koszek" <dunstan@freebsd.czest.pl>
References: <20051221031526.31ABC290@mx2.synetsystems.com>
	<200512211111.44268.jhb@freebsd.org>
	<20051227173434.GA53513@FreeBSD.czest.pl>
From: Richard Todd <rmtodd@ichotolot.servalan.com>
Date: Sat, 31 Dec 2005 18:39:31 -0600
In-Reply-To: <20051227173434.GA53513@FreeBSD.czest.pl> (Wojciech A. Koszek's
	message of "Tue, 27 Dec 2005 17:34:35 +0000")
Message-ID: <x7hd8osrwc.fsf@ichotolot.servalan.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: freebsd-current@freebsd.org, rwatson@freebsd.org
Subject: Re: Bug in latest rev kern_acct.c: panic: Trying sleep,
	but thread marked as sleeping prohibited
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jan 2006 01:15:15 -0000

"Wojciech A. Koszek" <dunstan@freebsd.czest.pl> writes:

> On Wed, Dec 21, 2005 at 11:11:43AM -0500, John Baldwin wrote:
>> acctwatch() probably isn't a good thing to do from a callout since it wants to 
>> do VOPs and such.  Probably the easiest fix is to stick acctwatch() in its 
>> own kthread.
>
> I think I didn't break current behaviour. Patch is here:
>
> http://freebsd.czest.pl/dunstan/FreeBSD/kern_acct.0.patch
>
> Richard, could you try to repeat your problem with my patch?

Got a chance to try a new kernel today with your patch. I tried to reproduce 
the panic by repeatedly copying a bunch of stuff onto /usr and deleting it
in one window, and in another repeatedly doing "make configure; make clean"
in one rather large port.  Lots of "Accounting suspended/resumed" messages
in the logs and no panics.  So it's looking good from here.