Date: Wed, 12 Sep 2007 12:47:58 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Kris Kennaway <kris@FreeBSD.org> Cc: re@FreeBSD.org, FreeBSD-current@FreeBSD.org, Mario Sergio Fujikawa Ferreira <lioux-list@uol.com.br> Subject: Re: panic: Trying sleep, but thread marked as sleeping prohibited Message-ID: <20070912124704.C79170@fledge.watson.org> In-Reply-To: <46E7AB54.9060103@FreeBSD.org> References: <20070912084914.9985.qmail@exxodus.fedaykin.here> <46E7AB54.9060103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Sep 2007, Kris Kennaway wrote: > Mario Sergio Fujikawa Ferreira wrote: >> I had 3 panics today. All seem to be related to ipf code. I have >> disabled ipf for the time being. >> >> I am attaching the kgdb backtraces. I am saving the cores. Let me know >> if there is anything I can do to help. >> >> FreeBSD exxodus.home.home 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Mon Sep 10 >> 15:01:49 BRT 2007 root@exxodus.home.home:/usr/obj/usr/src/sys/LIOUX i386 >> >> -current as of Sep 10 2007. > > Yes, known issue. The lack of response by the ipf maintainer so far > suggests it probably will not be fixed in 7.0. This should be documented in > the relnotes. The quick, and probably correct, fix is to replace all use of sx(9) with rw(9) in ipf. There might be places where a copying/copyout is being performed with the lock held, in which case this will trigger new warnings. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070912124704.C79170>