From owner-freebsd-ipfw@FreeBSD.ORG Mon Jan 24 17:11:14 2011 Return-Path: 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 2FB3910656A4; Mon, 24 Jan 2011 17:11:14 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 878B88FC32; Mon, 24 Jan 2011 17:11:13 +0000 (UTC) Received: by ewy24 with SMTP id 24so2044876ewy.13 for ; Mon, 24 Jan 2011 09:11:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=inkRhYBEHV5u2A9+dcK5fyEN3ADJlJwpl31Fql1EcL0=; b=YjC3iSPs8DVf3vUmkLUPURewLe5Gq609ibGWdOvj3oogZYXU8RI+h8yAHIPXs7KKJZ 9hrMDVKWb/0VVdX7CNEZj6ZJUsKI2l7uzo1YSY1O1hGE9urYirIdribdqrXfPEGW4O0M T6tCoopOrHyFOm9UgbwZfasFJeakd9+F0O6y8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Q82li1J/UusT2v5qoM0Idponrx3kB5pRQNu4M4h47fX2QI8615I0T7zucOzmS+ei3l hTw3skX7PYLrmULg0RxpmNlVQ22tyuFDk+GW8lPewAvuXbiZj3RDDrfFdv10YM67qlS5 b1tdZuARao2zFIaj71D5pczypOdXJJedC+p+w= MIME-Version: 1.0 Received: by 10.216.55.145 with SMTP id k17mr2762962wec.48.1295889072086; Mon, 24 Jan 2011 09:11:12 -0800 (PST) Received: by 10.216.36.71 with HTTP; Mon, 24 Jan 2011 09:11:12 -0800 (PST) In-Reply-To: <13247006.20110124020848@nitronet.pl> References: <201953550.20110106221821@nitronet.pl> <57312439.20110107171430@nitronet.pl> <13247006.20110124020848@nitronet.pl> Date: Mon, 24 Jan 2011 11:11:12 -0600 Message-ID: From: Brandon Gooch To: Pawel Tyll Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, Luigi Rizzo , Jack Vogel , freebsd-ipfw@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 17:11:14 -0000 On Sun, Jan 23, 2011 at 7:08 PM, Pawel Tyll wrote: > 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? I'm not sure. Perhaps there is another code path in the em(4) driver that leads to the same, bad-pointer state. I'll have to defer to Jack Vogel or Luigi Rizzo for potential insight into the issue. Please provide as much information as possible (even if it comes down to taking a photo of the console, or transcribing the backtrace). FYI, I haven't been able to test this on any of my setups yet... -Brandon