From owner-freebsd-current@FreeBSD.ORG Sun Feb 13 07:40:31 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6462A16A4CE for ; Sun, 13 Feb 2005 07:40:31 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31AA243D39 for ; Sun, 13 Feb 2005 07:40:30 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.13.3/8.13.3) with ESMTP id j1D7eLQl029017 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 13 Feb 2005 08:40:21 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.3/8.13.3/Submit) id j1D7eKoC029015; Sun, 13 Feb 2005 08:40:20 +0100 (CET) Date: Sun, 13 Feb 2005 08:40:20 +0100 From: Divacky Roman To: Emil Mikulic Message-ID: <20050213074020.GA28974@stud.fit.vutbr.cz> References: <20050212030852.GF693@dmr.ath.cx> <20050212162440.GA82987@stud.fit.vutbr.cz> <20050213005144.GA2580@dmr.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050213005144.GA2580@dmr.ath.cx> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 cc: current@freebsd.org Subject: Re: pfctl -f causes fatal trap 12 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 13 Feb 2005 07:40:31 -0000 On Sun, Feb 13, 2005 at 11:51:44AM +1100, Emil Mikulic wrote: > On Sat, Feb 12, 2005, Divacky Roman top-posted: > > same here.... I have pf as module and see this panic on boot > > > > when I reboot after the panic, fsck takes place and then it doesn > > panic (obviously the fsck changes something which causes pf not to > > panic) > > Really? I hadn't noticed that. You should send your message to the > mailing list in case it can help one of the developers track down the > problem. yes.... and oh, I forgot to cc: current (and I am doing it now) > >From the kgdb output: > > > (kgdb) frame 11 > > > #11 0xc0627fdc in softclock (dummy=0x0) at \ > > > /usr/src/sys/kern/kern_timeout.c:315 > > > 315 mtx_unlock(c_mtx); > > > (kgdb) print c_mtx > > > $1 = (struct mtx *) 0x0 > > It looks to me like that part of the code is trying to unlock an > uninitialized mutex. > > I guess running fsck somehow causes the mutex to be initialized before > loading the pf rules breaks stuff. maybe