Hi Kip, On Sun, Sep 09, 2007 at 01:11:02PM -0700, Kip Macy wrote: > This is a known issue. sx locks aren't for use in the I/O path. The > firewall maintainer chooses to use them. This might be avoidable in > the future if we can establish a mechanism for preventing pfil from > being unloaded without protecting it with an rwlock. > Sorry, I didn't notice this in my search. I've switched to pf instead and it seems to work fine. Thank you! - Pete Curry > -Kip > > > > On 9/9/07, Pete Curry <mail_at_petecurry.net> wrote: > > Hi, > > > > I've been getting a very reproducable panic in -CURRENT with moderate > > network traffic (including same-machine traffic, and especially > > with ssh), and a LOR on boot. > > > > kiwi# uname -a > > FreeBSD kiwi.petecurry.net 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Sun > > Sep 9 11:01:03 CDT 2007 root_at_:/usr/obj/usr/src/sys/KIWIKERN amd64 > > > > The source is from about 10:00 this morning, and my kernel config > > and dmesg output is attached. It's been happening for at least a > > few weeks, about as long as I've been running -CURRENT and had this > > machine. > > > > The LOR message is: > > Sep 9 11:16:00 kiwi kernel: lock order reversal: (sleepable after non-sleepable) > > Sep 9 11:16:00 kiwi kernel: 1st 0xffffffff807781a8 PFil hook read/write mutex (PFil hook read/write mutex) _at_ /usr/src/sys/net/pfil.c:73 > > Sep 9 11:16:00 kiwi kernel: 2nd 0xffffffffb1e2f840 ipf filter load/unload mutex (ipf filter load/unload mutex) _at_ /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/fil.c:2419 > > [snip]Received on Sun Sep 09 2007 - 18:45:48 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:17 UTC