From owner-freebsd-stable@FreeBSD.ORG Sun Oct 1 18:18:03 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 BE9F016A4C9 for ; Sun, 1 Oct 2006 18:18:03 +0000 (UTC) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEBF543D76 for ; Sun, 1 Oct 2006 18:17:57 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ironport2.bredband.com ([195.54.107.84] [195.54.107.84]) by mxfep02.bredband.com with ESMTP id <20061001181756.ZHHL21247.mxfep02.bredband.com@ironport2.bredband.com> for ; Sun, 1 Oct 2006 20:17:56 +0200 Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30]) by ironport2.bredband.com with ESMTP; 01 Oct 2006 20:17:56 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id C981C67922; Sun, 1 Oct 2006 20:17:55 +0200 (CEST) Message-ID: <45200654.6030103@gneto.com> Date: Sun, 01 Oct 2006 20:17:56 +0200 From: Martin Nilsson User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: Martin Nilsson References: <451A1375.5080202@gneto.com> In-Reply-To: <451A1375.5080202@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2 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: Sun, 01 Oct 2006 18:18:03 -0000 Just an observation. All the boxes I've had this problem on have _two_ em interfaces. I have never seen it on my boxes with just one em NIC. The error is always em0 timeout - never em1 (I haven't seen any!) Yesterday my local network got completely wacky, the gateway had em0 timeouts on the screen: but em0 is the _outside_ the windows box that I had to reboot was attached to the inside on em1! Could there be something wrong in the driver if we have more than one em interface? Regards, Martin