e1000 still

[Ed Brown]

Interesting.  My experience with those tools is very limited, but that's
not my idea of how a "passive" device would behave!  

But I wonder why this is only an issue with the e1000 driver and
anaconda?  And why aren't 30-45 second delays seen at the beginning of
any install through a switch with spanning tree enabled?  Also, I've
moved network cables on switch ports and they are instantly working.  It
just doesn't add up to me that spanning tree calculations are really a
factor here, if they indeed take that long.

-Ed


On Wed, 2005-03-23 at 10:46, asterr wrote:
> Ed,
> 
> In my experience troubleshooting this issue, I have also seen that a passive
> analyzer (fluke) in between the host and the switch made the problem disappear.
> 
> On closer analysis, this was found to be due to the fact that the analyzer 
> we used established a circuit to the switch port, so the switch port was
> not shut down when the host was rebooted.  Because the switch port never went
> down, the spanning tree did not need to be recalculated.
> 
> -Aaron
> 
> On Tue, 22 Mar 2005, Ed Brown wrote:
> 
> > I don't believe there is a need to wait 30 or 45 seconds for spanning
> > tree calculations on the switch.  There is something much more subtle
> > going on here.  As I mentioned before, we've tried capturing traffic
> > with a passive analyzer between the box being built and the switch, and
> > just this change to the network connections allow the install to proceed
> > normally (as does inserting a small 10/100 hub inline, or replacing the
> > gig switch with a 100Mb switch.)  It isn't about spanning tree
> > calculations on the switch, I think there is some sub-second change in
> > the characteristics of the negotiation or anaconda's network setup, when
> > spanning tree is on or off, that make a difference.
> > 
> > -Ed
> > 
> > 
> > 
> > On Tue, 2005-03-22 at 07:51, James_Martin at ao.uscourts.gov wrote:
> > > I agree.  The less hacking the better.  Red Hat could easily put a sleep 
> > > variable in the init.c that is set at the syslinux command line.  Have you 
> > > type something like:
> > > 
> > > linux network_wait=30
> > > 
> > > That parameter would then be passed to init which would then wait the 
> > > specified amount of time.  Changing your network configuration to 
> > > accommodate a operating system install is ridiculous.
> > > 
> > > Jeremy/Paul, opinions?
> > > 
> > > 
> > > James
> > > 
> > > 
> > > James S. Martin, RHCE
> > > Contractor
> > > Administrative Office of the United States Courts
> > > Washington, DC
> > > (202) 502-2394
> > > 
> > > kickstart-list-bounces at redhat.com wrote on 03/21/2005 07:42:13 PM:
> > > 
> > > > On Mon, 2005-03-21 at 15:29, James_Martin at ao.uscourts.gov wrote:
> > > > > This is an age old problem going back to my RH 7.2 days. 
> > > > 
> > > > Yes, this is old news, hashed over on several lists, in many threads. 
> > > > James solution may help the original post-er to this thread, who was
> > > > doing remote installs, with no access to the switches. 
> > > > 
> > > > The point, or mine anyway, is that hacking the code or having to modify
> > > > switch configurations to be able to install the OS, are poor
> > > > alternatives to be faced with.  How is this not a problem with anaconda,
> > > > and why hasn't RedHat owned it / fixed it? 
> > > > 
> > > > -Ed 
> > > > 
> > > > _______________________________________________
> > > > Kickstart-list mailing list
> > > > Kickstart-list at redhat.com
> > > > https://www.redhat.com/mailman/listinfo/kickstart-list
> > > 
> > > _______________________________________________
> > > Kickstart-list mailing list
> > > Kickstart-list at redhat.com
> > > https://www.redhat.com/mailman/listinfo/kickstart-list
> > 
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> > 
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list