Thread (7 messages) flat view 7 messages, 3 authors, 2012-09-15

Re: Remarks and comments about ipconfig behavior

From: Erwan Velu <hidden>
Date: 2012-09-13 20:37:56

Le 13/09/2012 22:31, David Miller a écrit :
From: Erwan Velu<redacted>
Date: Thu, 13 Sep 2012 22:21:15 +0200
quoted
That lever for me two points :
- why is this timeout setup for so long ? Even with a spantree
- configuration, not having a carrier for 2mn is *waow* ... Does a 30sec
- could not be enough ? What is the need of waiting so long time ?
I've seen PHY/switch/hub combinations that take longer than 30 seconds
to fully negotiate the link.

There is really no upper limit to the link speed/duplex/etc.
negoatiation process.

Even if the actual negoatiation protocol had an upper limit on
negoatiation time, hardware implementations do things like try
sampling the quality of the cable signal and may choose to
down-rev the advertised features and restart the negoatiation.
Ok but shouldn't we display some message to the user trying to explain 
why the kernel is stopped and perfectly silent during its booting 
process ? 2 minutes, that's a pretty long time with an almost frozen 
kernel isn't it ?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help