From owner-freebsd-stable@FreeBSD.ORG Sun Oct 1 18:43:00 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 2FF9F16A403 for ; Sun, 1 Oct 2006 18:43:00 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8C2F43D46 for ; Sun, 1 Oct 2006 18:42:59 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k91Igq9M045972; Sun, 1 Oct 2006 12:42:58 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <45200C2A.2030102@samsco.org> Date: Sun, 01 Oct 2006 12:42:50 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Martin Nilsson References: <451A1375.5080202@gneto.com> <45200654.6030103@gneto.com> In-Reply-To: <45200654.6030103@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org 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:43:00 -0000 Martin Nilsson wrote: > 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 Multiple instances of the driver have no knowledge of each other. Nothing between them is shared. Even if they share an interrupt, it is a detail that is hidden. Scott