From owner-freebsd-ipfw@FreeBSD.ORG  Sun Feb 20 03:39:08 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 1146F106567A
	for <freebsd-ipfw@freebsd.org>; Sun, 20 Feb 2011 03:39:08 +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 C1EF38FC12
	for <freebsd-ipfw@freebsd.org>; Sun, 20 Feb 2011 03:39:07 +0000 (UTC)
Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.72 (FreeBSD))
	(envelope-from <ptyll@nitronet.pl>) id 1Pr08Y-000AJD-JE
	for freebsd-ipfw@freebsd.org; Sun, 20 Feb 2011 04:39:06 +0100
Date: Sun, 20 Feb 2011 04:38:02 +0100
From: Pawel Tyll <ptyll@nitronet.pl>
X-Priority: 3 (Normal)
Message-ID: <1385625194.20110220043802@nitronet.pl>
To: Brandon Gooch <jamesbrandongooch@gmail.com>
In-Reply-To: <AANLkTimWkWYj=HB5BTM0nwYWgNia-Wq4bYHsRB=OjVP7@mail.gmail.com>
References: <410175608.20110220013900@nitronet.pl>
	<AANLkTimWkWYj=HB5BTM0nwYWgNia-Wq4bYHsRB=OjVP7@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: freebsd-ipfw@freebsd.org, Luigi Rizzo <rizzo@iet.unipi.it>,
	Jack Vogel <jfvogel@gmail.com>, 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:39:08 -0000

> Same backtrace as reported here?
I'm unable to get the new backtrace, but judging from what I can see
on the console pre-reboot, it's exactly the same deal since
8.0-RELEASE - panic with dummynet as main star.

> What revision of the em(4) driver code are you using? I know Jack has
> been working out certain quirky issues lately, and there have been
> updates to the code since last you posted an update to your problem.
em0: <Intel(R) PRO/1000 Network Connection 7.1.8> port 0x2040-0x205f mem 0x=
b1a00000-0xb1a1ffff,0xb1a25000-0xb1a25fff irq 20 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:15:17:...
em1: <Intel(R) PRO/1000 Network Connection 7.1.8> port 0x1000-0x101f mem 0x=
b1900000-0xb191ffff,0xb1920000-0xb1923fff irq 16 at device 0.0 on pci2
em1: Using MSIX interrupts with 3 vectors
em1: [ITHREAD]
em1: [ITHREAD]
em1: [ITHREAD]
em1: Ethernet address: 00:15:17:..

> Maybe Jack could shed some light on the whether the updates could
> somehow work out to be a fix for your problem -- or whether or not
> your issue is even related to the em(4) driver.
I'm not sure anymore that em is at fault here. Anyway, currently I'm
running FreeBSD 8.2-PRERELEASE #1: Fri Jan  7 17:19:28. If something
happened since then that could fix this, I'll gladly update.