Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Jan 2011 09:14:33 -0800
From:      Jack Vogel <jfvogel@gmail.com>
To:        Brandon Gooch <jamesbrandongooch@gmail.com>
Cc:        Pawel Tyll <ptyll@nitronet.pl>, Luigi Rizzo <rizzo@iet.unipi.it>, freebsd-ipfw@freebsd.org, freebsd-net@freebsd.org
Subject:   Re: [Panic] Dummynet/IPFW related recurring crash.
Message-ID:  <AANLkTim87RE_ZAR3ZKwbJ6KW3xCPze=76fQ9e8Qo1v_D@mail.gmail.com>
In-Reply-To: <AANLkTi=UJHtvEm5k-Cxrtdr-2k_3_hyR_F8GuUwmHmE4@mail.gmail.com>
References:  <201953550.20110106221821@nitronet.pl> <AANLkTikozeXLQtePk1niH-N58n9f6xAVGVBTmLPux2e-@mail.gmail.com> <57312439.20110107171430@nitronet.pl> <AANLkTikZAHNRu_3=i5_0FTNOMua8Kr2bW7H+RJZ4c=PW@mail.gmail.com> <13247006.20110124020848@nitronet.pl> <AANLkTi=UJHtvEm5k-Cxrtdr-2k_3_hyR_F8GuUwmHmE4@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Just replying so you know I'm seeing it, but something that takes 14 days to
even happen
is NOT going to be an easy one to find. As Brandon said, all the info you
can provide please.

Jack


On Mon, Jan 24, 2011 at 9:11 AM, Brandon Gooch
<jamesbrandongooch@gmail.com>wrote:

> On Sun, Jan 23, 2011 at 7:08 PM, Pawel Tyll <ptyll@nitronet.pl> wrote:
> > On Fri, Jan 7, 2011, Brandon Gooch <jamesbrandongooch@gmail.com> 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
>



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?AANLkTim87RE_ZAR3ZKwbJ6KW3xCPze=76fQ9e8Qo1v_D>