Re: kern/51531: Recent networking regression affecting installs

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR kern/51531; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: Roy Marples <roy%marples.name@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/51531: Recent networking regression affecting installs
Date: Wed, 23 Nov 2016 12:07:19 +0200

 Roy Marples wrote:
 > > It waits for about 5 seconds, not 15.  Here's the relevant part
 > > of the timestamped log (the big numbers are seconds since the epoch):
 > 
 > OK.
 > That tells me that the address is DETACHED during this time and not
 > TENTATIVE.
 
 Shouldn't there be a DETACHED flag in the ifconfig output, then?
 
 > In other words, the interface thinks there is no carrier.
 > 
 > Could you try changing my commit locally from -w 15 -W 5 to -w 15 -W 15
 > and see if that helps at all?
 
 Not easily.  The testbed in case is generating public reports that are
 supposed to reflect the true state of -current as a function of the
 CVS source date.  To test something that is not actually -current,
 I'd have to set up a separate instance of the testbed.
 
 > If not, do other numbers help? -w 120 -W 120 is insane, but it's worth
 > trying to see if my theory is right.
 > 
 > If so, we just have to increase the default numbers, and maybe in
 > rc.conf as well OR look into why the interface is taking more than 5
 > seconds to gain a carrier as sk0 is cabled yes?
 
 It is cabled to a 10baseT (sic) hub.  I could try a 100baseTX switch
 and see if that makes a difference.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost