From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263764AbTDDPnI (for ); Fri, 4 Apr 2003 10:43:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263758AbTDDPmY (for ); Fri, 4 Apr 2003 10:42:24 -0500 Received: from havoc.daloft.com ([64.213.145.173]:44267 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id S263764AbTDDPhS (for ); Fri, 4 Apr 2003 10:37:18 -0500 Date: Fri, 4 Apr 2003 10:48:42 -0500 From: Jeff Garzik To: Justin Cormack Cc: Paul Rolland , "'Michael Knigge'" , Kernel mailing list Subject: Re: Strange e1000 Message-ID: <20030404154842.GA10607@gtf.org> References: <043501c2faaf$da061e10$3f00a8c0@witbe> <1049467531.2676.87.camel@lotte> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1049467531.2676.87.camel@lotte> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 04, 2003 at 03:45:25PM +0100, Justin Cormack wrote: > On Fri, 2003-04-04 at 14:41, Paul Rolland wrote: > > Hello, > > > > > when I load the e1000 module, my NIC is recognized. Then, "pump -i > > > eth0" is called (DHCP-Client), the message "e1000: eth0 NIC > > > Link is Up > > > 1000 Mbps Full Duplex" appears and after some time I get the message > > > "operation failed". > > > > > > When I sleep some time (currently 20 seconds) before doing > > > the "pump", > > > everything works as expected. > > > > > > What the hell is happening here? Ok, I got it working with the > > > 20-sec-sleep but this is not the way it sould work... > > > > > > My Board is a Gigabyte GA-7ZXR (1.0) and the Intel NIC is a PRO/1000 > > > MT (should be the 82540OEM Chip). The NIC is attached to a NetGear > > > FSM726S Switch (24x100 + 2x1000). It is currenty the only box > > > attached > > > > Could it be possible that the 1000MBps FD on the e1000 side is > > a local configuration, and that it needs some time to discuss with > > the Netgear switch to negotiate correctly speed and duplex before > > working correctly ? (i.e. 20 sec = negotiation time) > > It is probably something like this. For some reason the managed Netgear > switches take a very long time to do anything. Log into the switch and > watch the port status while this happens to confirm. I actually can't > netboot off these switches because if this. Hopefully Netgear will come > up with a fix. In another thread, Scott Feldman (one of the e1000 team) asked if spanning trees were enabled on the switch. That could be a potential cause. Jeff