From owner-freebsd-stable@FreeBSD.ORG Thu Oct 19 19:14:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 797F416A40F for ; Thu, 19 Oct 2006 19:14:40 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6476043D60 for ; Thu, 19 Oct 2006 19:14:07 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so926599pye for ; Thu, 19 Oct 2006 12:13:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JIFh2XGGrHiIa6tohaCFkoR6YL4FQQTdcMZEHtd+Zz9dYzfxSSeGa6/v8jc3OQwQdxWLS0mBDtkv6ijxGWiu+PTv4kVHRHKTnNDS4SjHgXWpfK2Bl0nEvgH57avzPe3FGsZa2faJFjXL+qa4nAFuwgbK7SNiB6Mw04JLWD4Kohg= Received: by 10.35.123.10 with SMTP id a10mr477767pyn; Thu, 19 Oct 2006 12:13:33 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Thu, 19 Oct 2006 12:13:33 -0700 (PDT) Message-ID: <2a41acea0610191213k659c3b7l59092e8b436e210d@mail.gmail.com> Date: Thu, 19 Oct 2006 12:13:33 -0700 From: "Jack Vogel" To: freebsd-stable@freebsd.org In-Reply-To: <20061019190221.GH71000@droso.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> <20061018171704.A3851@demos.bsdclusters.com> <4537C126.5000207@FreeBSD.org> <2a41acea0610191140j13d43e12q72fc7697652e222a@mail.gmail.com> <20061019190221.GH71000@droso.net> Subject: Re: em network issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2006 19:14:40 -0000 On 10/19/06, Erwin Lansing wrote: > On Thu, Oct 19, 2006 at 11:40:16AM -0700, Jack Vogel wrote: > > On 10/19/06, Remko Lodder 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? > > > A bit more helpfull, but unfortunately not much is a datapoint saying no > problems April 3rd and watchdog timeouts after September 28 RELENG_6. I > know, probably too vague to be of any use, but there it is. > > Intel(R) PRO/1000 Network Connection Version - 6.1.4 on a workstation > with next to no traffic. so, you mean you did a cvsup on 9/28, and one was done on april 3?