From owner-freebsd-net@FreeBSD.ORG Mon Jan 24 01:08:51 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81A37106566B for ; Mon, 24 Jan 2011 01:08:51 +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 3FA768FC1E for ; Mon, 24 Jan 2011 01:08:50 +0000 (UTC) Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.72 (FreeBSD)) (envelope-from ) id 1PhAvK-0000Xb-8t for freebsd-net@freebsd.org; Mon, 24 Jan 2011 02:08:50 +0100 Date: Mon, 24 Jan 2011 02:08:48 +0100 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <13247006.20110124020848@nitronet.pl> To: Brandon Gooch In-Reply-To: References: <201953550.20110106221821@nitronet.pl> <57312439.20110107171430@nitronet.pl> 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: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false Cc: freebsd-net@freebsd.org, Luigi Rizzo , Jack Vogel , freebsd-ipfw@freebsd.org Subject: Re: [Panic] Dummynet/IPFW related recurring crash. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 01:08:51 -0000 On Fri, Jan 7, 2011, Brandon Gooch wrote: > It's likely that the mbuf handling problem (in em_refresh_mbufs()) is > triggered by the processing you're doing with ipfw (or elsewhere for > that matter), so, yes, I think it's a bug fixed in the revision > discussed. > When you update and test, please let us know. Also, don't forget to > submit a follow-up to your PR. Unfortunately bad news: Machine fell after 14 days, 22:31:42 for the same reason according to what was left of panic screen. It didn't do a dump, nor reboot as is customary since some time on S3420GP boards (and other Intel server boards, since colleague has dual-cpu board from same epoch). What can I try next?