From owner-freebsd-current@FreeBSD.ORG Sun Sep 9 20:45:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD2ED16A420 for ; Sun, 9 Sep 2007 20:45:48 +0000 (UTC) (envelope-from mail@petecurry.net) Received: from adam.russellhosting.net (russellit.com [64.246.48.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6972613C469 for ; Sun, 9 Sep 2007 20:45:48 +0000 (UTC) (envelope-from mail@petecurry.net) Received: from 015-806-741.area5.spcsdns.net ([68.240.64.214]:61116 helo=petecurry.net) by adam.russellhosting.net with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim 4.63) (envelope-from ) id 1IUTfD-0007YG-Tk; Sun, 09 Sep 2007 16:45:53 -0400 Received: by petecurry.net (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168/168 bits)) mail@petecurry.net; Sun, 9 Sep 2007 15:45:39 -0500 (CDT) Date: Sun, 9 Sep 2007 15:45:36 -0500 From: Pete Curry To: Kip Macy Message-ID: <20070909204536.GB33652@kiwi.petecurry.net> References: <20070909180445.GA33652@kiwi.petecurry.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - adam.russellhosting.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - petecurry.net X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-current@freebsd.org Subject: Re: Panic and LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2007 20:45:48 -0000 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 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@:/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) @ /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) @ /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/fil.c:2419 > > [snip]