From owner-freebsd-current@FreeBSD.ORG  Tue May 15 03:46:11 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 1079F16A403
	for <freebsd-current@freebsd.org>; Tue, 15 May 2007 03:46:11 +0000 (UTC)
	(envelope-from randy@psg.com)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by mx1.freebsd.org (Postfix) with ESMTP id EE50013C447
	for <freebsd-current@freebsd.org>; Tue, 15 May 2007 03:46:10 +0000 (UTC)
	(envelope-from randy@psg.com)
Received: from cust16202.lava.net ([64.65.95.74] helo=[192.168.0.101])
	by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.66 (FreeBSD)) (envelope-from <randy@psg.com>)
	id 1HnnzF-000Jr3-BA; Tue, 15 May 2007 03:46:09 +0000
Message-ID: <46492CFC.6060506@psg.com>
Date: Tue, 15 May 2007 05:46:04 +0200
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: LI Xin <delphij@delphij.net>
References: <17993.9973.237807.213217@roam.psg.com>
	<46492B3B.3020305@delphij.net>
In-Reply-To: <46492B3B.3020305@delphij.net>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: em driver
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2007 03:46:11 -0000

LI Xin wrote:
> Randy Bush wrote:
>> could the em driver have been borked by the recent changes such that
>> once a day or so it went out for a few minutes to an hour?  if so, did
>> the changes three days ago fix it?
> What do you mean by "went out"?  According to my understanding 1.175 of 
> if_em.c seems to fix the case where em(4) fails to attach on certain 
> hardware...

running fine.  stops moving packets for five to 60 minutes.  starts moving
packets again.  all with no intervention, in rack, long way away.  e.g. see
two stops in

    http://rip.psg.com/~randy/070514.em0-borkage.png

no other hosts with same symptom, though three with em ethers updated at
same time.

and, of course, it used to work fine until cvsup of May 8 12:03 (gmt).
everything always "used to work." :)

randy