Date: Sat, 31 Dec 2005 18:39:31 -0600 From: Richard Todd <rmtodd@ichotolot.servalan.com> To: "Wojciech A. Koszek" <dunstan@freebsd.czest.pl> 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 Message-ID: <x7hd8osrwc.fsf@ichotolot.servalan.com> In-Reply-To: <20051227173434.GA53513@FreeBSD.czest.pl> (Wojciech A. Koszek's message of "Tue, 27 Dec 2005 17:34:35 %2B0000") References: <20051221031526.31ABC290@mx2.synetsystems.com> <200512211111.44268.jhb@freebsd.org> <20051227173434.GA53513@FreeBSD.czest.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
"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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?x7hd8osrwc.fsf>