From: "Patrick R. McManus" <mcmanus@ducksong.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Justin Cormack <justin@street-vision.com>,
Paul Rolland <rol@as2917.net>,
"'Michael Knigge'" <Michael.Knigge@set-software.de>,
Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Strange e1000
Date: Fri, 4 Apr 2003 12:02:14 -0500 [thread overview]
Message-ID: <20030404170214.GA1457@ducksong.com> (raw)
In-Reply-To: <20030404154842.GA10607@gtf.org>
[Jeff Garzik: Apr 04 10:48]
> 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.
> > > >
[..]
> > 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.
I can confirm this is isolated to the managed netgear switches.. I
started the other thread jeff mentions and, just this morning, cobbled
together a network without them and had no problems. I'll see if I can
create a setup without spanning tree to test that explicitly.
next prev parent reply other threads:[~2003-04-04 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 7:25 Strange e1000 Michael Knigge
2003-04-04 13:41 ` Paul Rolland
2003-04-04 14:00 ` Michael Knigge
2003-04-04 14:19 ` Abhishek Agrawal
2003-04-04 18:14 ` Jeff Garzik
2003-04-05 8:41 ` Henning P. Schmiedehausen
2003-04-04 14:45 ` Justin Cormack
2003-04-04 15:48 ` Jeff Garzik
2003-04-04 17:02 ` Patrick R. McManus [this message]
2003-04-04 17:09 ` Patrick R. McManus
2003-04-07 7:45 ` Strange e1000 - SOLVED Michael Knigge
-- strict thread matches above, loose matches on Subject: below --
2003-04-07 21:52 Strange e1000 Mroczek, Joseph T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030404170214.GA1457@ducksong.com \
--to=mcmanus@ducksong.com \
--cc=Michael.Knigge@set-software.de \
--cc=jgarzik@pobox.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.