From owner-freebsd-pf@FreeBSD.ORG Wed Dec 6 13:20:07 2006 Return-Path: X-Original-To: freebsd-pf@hub.freebsd.org Delivered-To: freebsd-pf@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 024E516A509 for ; Wed, 6 Dec 2006 13:20:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 025C643CA7 for ; Wed, 6 Dec 2006 13:19:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB6DK5ZW004939 for ; Wed, 6 Dec 2006 13:20:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB6DK5iO004938; Wed, 6 Dec 2006 13:20:05 GMT (envelope-from gnats) Date: Wed, 6 Dec 2006 13:20:05 GMT Message-Id: <200612061320.kB6DK5iO004938@freefall.freebsd.org> To: freebsd-pf@FreeBSD.org From: Volker Cc: Subject: Re: kern/106400: fatal trap 12 at restart of PF with ALTQ if ng0 device has detached X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Volker 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: Wed, 06 Dec 2006 13:20:07 -0000 The following reply was made to PR kern/106400; it has been noted by GNATS. From: Volker To: bug-followup@FreeBSD.org, bst2006@dva.dyndns.org Cc: Subject: Re: kern/106400: fatal trap 12 at restart of PF with ALTQ if ng0 device has detached Date: Wed, 06 Dec 2006 14:16:42 +0100 First I would suggest to use ALTQ w/ mpd not on ng0 but on the real physical interface (for example fxp0, xl0) which is being used by netgraph/mpd. On the other side I also do have trouble using ALTQ with mpd but I'm using mpd for a 3G connection (based on a tty device, not a NIC). Avoiding ALTQ rules in pf.conf for the ng0 interface (not using ALTQ on ng0) doesn't produce a fatal trap 12. So disabling ALTQ in your kernel is not the only workaround. You may still use ALTQ on your internal NIC without a trap. Unlike your experience, I always do experience a kernel trap when reloading pf rules w/ ALTQ on ng0 (whether or not pf rules are reloaded by a script or manually). This also occours while the ng0 interface is still there and from my experience it's not related to a reload of mpd.