Date: Thu, 19 Oct 2006 20:17:10 +0200 From: Remko Lodder <remko@FreeBSD.org> To: Kip Macy <kmacy@fsmware.com> Cc: freebsd-net <freebsd-net@freebsd.org>, freebsd-stable@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: em network issues Message-ID: <4537C126.5000207@FreeBSD.org> In-Reply-To: <20061018171704.A3851@demos.bsdclusters.com> References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <b1fa29170610181523t6d240839i887632d6d7576762@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> <20061018171704.A3851@demos.bsdclusters.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
--
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?4537C126.5000207>