Date: Mon, 31 Jul 2006 20:14:06 -0400 From: Robert Huff <roberthuff@rcn.com> To: freebsd-current@FreeBSD.org Subject: Re: LOR when booting CURRENT Message-ID: <17614.40142.109365.481255@jerusalem.litteratus.org> In-Reply-To: <44CE6C0A.50009@FreeBSD.org> References: <20060726063636.GA58151@freefall.freebsd.org> <17610.836.663396.331448@jerusalem.litteratus.org> <44CE6C0A.50009@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian S.J. Peron writes: > > For the record, I'm (still) getting this also. > > This appears to be similar to the LOR associated with IPFW and ucred > based rules, I think. Although this is a lock order reversal and it > probably isn't a false positive, it should be reasonably harmless, > because the pfil hook lock is a reader lock, thus different threads can > acquire it (at this point) con-currently, presumably preventing a dead > lock from actually occurring here. To my knowledge, not so: please see kern/86427. This puppy will choke my -CURRENT system in around ten days under a light network load. Under substantial traffic, less than three. I had hoped the network stack changes Robert Watson committed a while back would fix this, but apparently not. This is a _major_ pain in the ass, and I look forward to the day when someone drives a backtrace through its pulsing green heart. Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17614.40142.109365.481255>