From owner-freebsd-pf@FreeBSD.ORG Sat Aug 6 17:24:15 2005 Return-Path: X-Original-To: freebsd-pf@freebsd.org Delivered-To: freebsd-pf@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3F6B16A41F for ; Sat, 6 Aug 2005 17:24:15 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94B0B43D46 for ; Sat, 6 Aug 2005 17:24:14 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3E7E3.dip.t-dialin.net [84.163.231.227] (helo=donor.laier.local) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML21M-1E1SP62cuV-0002Hz; Sat, 06 Aug 2005 19:24:12 +0200 From: Max Laier To: freebsd-pf@freebsd.org Date: Sat, 6 Aug 2005 19:24:03 +0200 User-Agent: KMail/1.8 References: <42F4F0CB.8050306@cs.tu-berlin.de> In-Reply-To: <42F4F0CB.8050306@cs.tu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1346261.3xF0BsS1vi"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200508061924.10927.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Subject: Re: pf causes freeze of amd64 machine on heavy network load X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Aug 2005 17:24:15 -0000 --nextPart1346261.3xF0BsS1vi Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 06 August 2005 19:18, Bj=F6rn K=F6nig wrote: > Hello, > > recently I sent a mail to the current mailing list concerning this > problem, but I figured out that my problem is related to pf. > > I have an amd64 machine with 6.0-BETA2 that freezes totally on heavy > network I/O with activated pf. I noticed that it doesn't occur with > every ruleset. > > This is the output of dmesg; note the KDB backtraces during the attempt > to load pf.ko and system shutdown: > > http://212.202.37.29/dateien/dmesg.txt > > The following ruleset is neither complete nor optimized; I stopped > working on it when I noticed that pf doesn't work for me: > > http://212.202.37.29/dateien/pf.conf.txt > > Unfortunately the time-frame where I can make tests concerning this > issue is from now until Monday. I hope someone is able to reproduce the > error to make further investigations. =46rom pf.conf(5): BUGS Due to a lock order reversal (LOR) with the socket layer, the use of t= he group and user filter parameter in conjuction with a Giant-free netsta= ck can result in a deadlock. If you have to use group or user you must s= et debug.mpsafenet to ``0'' from the loader(8), for the moment. This wor= k- around will still produce the LOR, but Giant will protect from the dea= d- lock. I am afraid this is what bites you. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1346261.3xF0BsS1vi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC9PI6XyyEoT62BG0RAsnPAJ4g2p9Pvnmh5ry7xmBqdRPhsvpPRQCeOOCR TD6vmcGKDSHOmHsF6E8PCiA= =ynIk -----END PGP SIGNATURE----- --nextPart1346261.3xF0BsS1vi--