Date: Thu, 19 Oct 2006 21:44:32 +0200 From: Remko Lodder <remko@FreeBSD.org> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org>, Kip Macy <kmacy@fsmware.com>, freebsd-stable@freebsd.org Subject: Re: em network issues Message-ID: <4537D5A0.6090004@FreeBSD.org> In-Reply-To: <2a41acea0610191140j13d43e12q72fc7697652e222a@mail.gmail.com> References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <b1fa29170610181523t6d240839i887632d6d7576762@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> <20061018171704.A3851@demos.bsdclusters.com> <4537C126.5000207@FreeBSD.org> <2a41acea0610191140j13d43e12q72fc7697652e222a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote:
> On 10/19/06, Remko Lodder <remko@freebsd.org> wrote:
>> Kip Macy wrote:
>> >
>> > On Wed, 18 Oct 2006, Jack Vogel wrote:
>> >> I'm a bit confused from the way you worded this, do you have watchdogs
>> >> with em, or you use em to avoid them?
>> >
>> > I have watchdogs with the current (post vendor update) em driver, but
>> > not with an older (pre vendor update) version of it.
>> >
>>
>> Same here!
>>
>> Didn't had the problem prior to the update, after the update it
>> started doing watchdog timeouts, occassionaly the interface goes
>> up/down after the watchdog error. I did not spot this on my other
>> servers yet, but the traffic passing the if_em interface is not that
>> much (just normal webtraffic, mail traffic etc).
>>
>> cheers,
>> remko
>
> LOL, you arent helping, i need to know WHAT CVS deltas work vs dont,
> in other words, which delta in the REL_ENG_6 stream broke things??
> If you quantify what 'the update' means that might help me, was this
> the 6.2 BETA or what?
>
> Thanks,
>
> Jack
It wasn't 6.2-BETA it was after the new driver import, around 2 months
ago if I remember correctly. It appears to be only on machines with some
data traffic.
I updated to the 6-STABLE when the new intel driver was imported, after
that the problems started , so my best guess is that it has something to
do with that driver update.
Hope this helps some more (see pciconf for more details about my cards)
pciconf:
em0@pci0:9:0: class=0x020000 card=0x11138086 chip=0x10768086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = '82547EI Gigabit Ethernet Controller'
class = network
subclass = ethernet
em1@pci0:10:0: class=0x020000 card=0x11138086 chip=0x10768086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = '82547EI Gigabit Ethernet Controller'
class = network
subclass = ethernet
--
Kind regards,
Remko Lodder ** remko@elvandar.org
FreeBSD ** remko@FreeBSD.org
/* Quis custodiet ipsos custodes */
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4537D5A0.6090004>