On Mon, 2004-08-23 at 05:56, Nigel Metheringham wrote:
On Mon, 2004-08-23 at 12:48, Alan Cox wrote:
> The problem with that view (which indeed was certainly my view and I fixed
> some drivers) is that from "up" it can take 60 seconds to get gigabit
> negotiation completed. In addition it really mucks up power management
> code in all the drivers.
I have a set of IBM servers with E1000 type ethernet NICs onboard which
are incapable of DHCP because they take longer to negotiate onto the
network than the DHCP timeouts. More amusingly, if coupled with cisco
switches they can badly negotiate to a state where ping and packet
turn-round time is of the order of 10 seconds. Where the hell it stores
the data I have no idea...
It isn't just NIC to switch negotiation.
What I've seen in many many environments is the spanning tree protocol
is-there-a-layer-2-loop detection taking longer than the DHCP client
will wait.
I wager that spanning tree is the bigger problem vs ethernet
negotiation.
Dax Kelson
Guru Labs