Date: Tue, 22 Aug 2006 21:06:42 +0200 From: Pav Lucistnik <pav@FreeBSD.org> To: Eric Anderson <anderson@centtech.com> Cc: src-committers@FreeBSD.org, "Patrick M. Hausen" <hausen@punkt.de>, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org>, Pyun YongHyeon <yongari@FreeBSD.org> Subject: Re: cvs commit: src/sys/dev/em if_em.c Message-ID: <1156273602.91618.6.camel@ikaros.oook.cz> In-Reply-To: <44EB53E8.4030107@centtech.com> References: <200608220232.k7M2WmCr080275@repoman.freebsd.org> <20060822152333.GV96644@FreeBSD.org> <44EB220A.5000709@centtech.com> <20060822153210.GW96644@FreeBSD.org> <44EB2437.5070206@centtech.com> <20060822185313.GX96644@FreeBSD.org> <44EB53E8.4030107@centtech.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Eric Anderson píše v út 22. 08. 2006 v 13:58 -0500:
> On 08/22/06 13:53, Gleb Smirnoff wrote:
> > On Tue, Aug 22, 2006 at 10:35:19AM -0500, Eric Anderson wrote:
> > E> >E> >P> yongari 2006-08-22 02:32:48 UTC
> > E> >E> >P>
> > E> >E> >P> FreeBSD src repository
> > E> >E> >P>
> > E> >E> >P> Modified files:
> > E> >E> >P> sys/dev/em if_em.c
> > E> >E> >P> Log:
> > E> >E> >P> It seems that em(4) misses Tx completion interrupts under certain
> > E> >E> >P> conditions. The cause of missing Tx completion interrupts comes
> > E> >from
> > E> >E> >P> Tx interrupt moderation mechanism(delayed interrupts) or chipset
> > E> >bug.
> > E> >E> >P> If Tx interrupt moderation mechanism is the cause of false
> > E> >watchdog
> > E> >E> >P> timeout error we should have to fix all device drivers that have
> > E> >Tx
> > E> >E> >P> interrupt moderation capability. We may need more investigation
> > E> >E> >P> for this issue. Anyway, the fix is the same for both cases.
> > E> >E> >P>
> > E> >E> >P> This should fix occasional watchdog timeout errors seen on a few
> > E> >E> >P> systems.
> > E> >E> >P>
> > E> >E> >P> Reported by: -net, Patrick M. Hausen < hausen AT punkt DOT de >
> > E> >E> >P> Tested by: Patrick M. Hausen < hausen AT punkt DOT de >
> > E> >E> >
> > E> >E> >This look like a workaround, not a fix the root of the problem. Several
> > E> >E> >people on net said that this problem disappears if debug.mpsafenet=0.
> > E> >E> >So I think there is a problem in FreeBSD or driver, not in chip.
> > E> >E>
> > E> >E> And it also worked perfectly for a very very long time until 6.x tree.
> > E> >E> I went from 5-STABLE to 6-STABLE and started seeing it a lot ( a few
> > E> >E> times per day) on a couple servers.
> > E> >
> > E> >In 5-STABLE the watchdog events were not logged, but the watchdog was
> > E> >processed.
> > E>
> > E> But my interface never seemed to disappear (I page if the interface goes
> > E> down), and I'd still notice a link up/down, correct?
> >
> > In 5-STABLE the interface up/down events were not logged, either.
> >
>
>
> Ok. Well, I just recalled that on a separate system (my workstation
> actually), I went from 6.1-R to 6-STABLE as of about 8 days ago, and it
> now exhibits the problem too, which hasn't happened before.
Yes, there was an MFC of new em driver to 6-STABLE after 6.1-RELEASE.
I was badly hit by it too. But it appears only on some revisions of the
silicon...
--
Pav Lucistnik <pav@oook.cz>
<pav@FreeBSD.org>
Like 'Do Notte Buye Betamacks.' That was a prediction for 1972.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQBE61XCntdYP8FOsoIRAkw9AJ4krOL/2YRTRUD/60tNJNaF48nHBgCgtMl6
Jebi/xX8wfaT+kdu+LvOfPo=
=5ADz
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1156273602.91618.6.camel>