From owner-freebsd-ipfw@FreeBSD.ORG  Sun Feb 20 03:55:44 2011
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9779A106564A
	for <freebsd-ipfw@freebsd.org>; Sun, 20 Feb 2011 03:55:44 +0000 (UTC)
	(envelope-from ptyll@nitronet.pl)
Received: from mail.nitronet.pl (smtp.nitronet.pl [195.90.106.27])
	by mx1.freebsd.org (Postfix) with ESMTP id 5348F8FC08
	for <freebsd-ipfw@freebsd.org>; Sun, 20 Feb 2011 03:55:44 +0000 (UTC)
Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.72 (FreeBSD))
	(envelope-from <ptyll@nitronet.pl>) id 1Pr0Od-000Au4-7t
	for freebsd-ipfw@freebsd.org; Sun, 20 Feb 2011 04:55:43 +0100
Date: Sun, 20 Feb 2011 04:54:34 +0100
From: Pawel Tyll <ptyll@nitronet.pl>
X-Priority: 3 (Normal)
Message-ID: <1145317277.20110220045434@nitronet.pl>
To: Jack Vogel <jfvogel@gmail.com>
In-Reply-To: <AANLkTi=CLDFGxLQ8rdq3hg0KN9aYZA_YDwDWbqk5gcz2@mail.gmail.com>
References: <410175608.20110220013900@nitronet.pl>
	<AANLkTimWkWYj=HB5BTM0nwYWgNia-Wq4bYHsRB=OjVP7@mail.gmail.com>
	<AANLkTi=CLDFGxLQ8rdq3hg0KN9aYZA_YDwDWbqk5gcz2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Nitronet.pl
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: ptyll@nitronet.pl
X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false
Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, freebsd-ipfw@freebsd.org,
	Luigi Rizzo <rizzo@iet.unipi.it>, freebsd-net@freebsd.org
Subject: Re: [Panic] Dummynet/IPFW related recurring crash.
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Feb 2011 03:55:44 -0000

> I've never seen a trace like this, and no absolutely nothing about dummyn=
et, sorry.
> If it is in some way em's fault, then making sure you have the latest cod=
e would be
> a good idea. I have a test driver that is under selective test, it does e=
ffect the code
> path that you seem to be in, so it might be worth a try. If you want to t=
ry it early
> just pipe up and I'll send it.
I'm less and less sure that it has anything to do with em. I'd like to
hear Luigi's take on all this. That being said, I'll gladly try the
new driver -- if I'm right, I'll drop under 7 day reboot threshold
later into the year anyway, so I really need a permanent solution of
some kind. Apparently next crash always comes sooner that previous
one, which coincides with growing traffic.