From owner-freebsd-pf@FreeBSD.ORG Mon Sep 11 00:32:26 2006 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 3C81116A47C for ; Mon, 11 Sep 2006 00:32:26 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.ipactive.de [85.214.39.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81BCC43D73 for ; Mon, 11 Sep 2006 00:32:20 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-012.eplus-online.de [212.23.126.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 99FB833D21 for ; Mon, 11 Sep 2006 02:32:12 +0200 (CEST) Received: from [127.0.0.1] (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 325282E546 for ; Mon, 11 Sep 2006 02:31:57 +0200 (CEST) Message-ID: <4504AE93.3020203@vwsoft.com> Date: Mon, 11 Sep 2006 02:32:19 +0200 From: Volker User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-pf@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Subject: altq on ng0 sometimes causing system panic 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: Mon, 11 Sep 2006 00:32:26 -0000 Hi folks, two or three weeks ago I've switched from userland ppp to mpd for my internet connection. While using ng0 as the public interface I'm also using altq (cbq) for bw management. Everything works (haven't yet measured for queue effectiveness) but when issuing a `pfctl -gf mypf.conf' sometimes the system will panic. I need to reload my ruleset as soon as the internet connection has been set up because I've been lazy and am not using anchors so I'm just reloading my complete ruleset by a link-up script. I've been able to panic the machine just by reloading the ruleset manually several times in a row. As I currently don't have a serial console setup I'm unable to post any dumps or panic messages. Has anyone else experienced that? I've had queue statements in my pf rules before (even while using ppp and knowing about the problems with altq and tun) I've never experienced any panics. This is really just since changing from a tun to an ng device. If no one else has experienced panics like this I'll go and hook up the serial console and try to get a panic again. Current workaround is not to use altq on ng0 so I don't get panics ATM. Running RELENG_6, almost recently csup'ed. Greetings, Volker