| Message ID | 1364911105-21734-1-git-send-email-paul.gortmaker@windriver.com |
|---|---|
| State | Accepted, archived |
| Delegated to: | David Miller |
| Headers | show |
From: Paul Gortmaker <paul.gortmaker@windriver.com> Date: Tue, 2 Apr 2013 09:58:25 -0400 > Commit 3fb72f1e6e6165c5f495e8dc11c5bbd14c73385c ("ipconfig wait > for carrier") added a "wait for carrier on at least one interface" > policy, with a worst case maximum wait of two minutes. > > However, if you encounter this, you won't get any feedback from > the console as to the nature of what is going on. You just see > the booting process hang for two minutes and then continue. > > Here we add a message so the user knows what is going on, and > hence can take action to rectify the situation (e.g. fix network > cable or whatever.) After the 1st 10s pause, output now begins > that looks like this: > > Waiting up to 110 more seconds for network. > Waiting up to 100 more seconds for network. > Waiting up to 90 more seconds for network. > Waiting up to 80 more seconds for network. > ... > > Since most systems will have no problem getting link/carrier in the > 1st 10s, the only people who will see these messages are people with > genuine issues that need to be resolved. > > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> This is fine, applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/net/ipv4/ipconfig.c b/net/ipv4/ipconfig.c index bf6c5cf..efa1138 100644 --- a/net/ipv4/ipconfig.c +++ b/net/ipv4/ipconfig.c @@ -206,7 +206,7 @@ static int __init ic_open_devs(void) struct ic_device *d, **last; struct net_device *dev; unsigned short oflags; - unsigned long start; + unsigned long start, next_msg; last = &ic_first_dev; rtnl_lock(); @@ -263,12 +263,23 @@ static int __init ic_open_devs(void) /* wait for a carrier on at least one device */ start = jiffies; + next_msg = start + msecs_to_jiffies(CONF_CARRIER_TIMEOUT/12); while (jiffies - start < msecs_to_jiffies(CONF_CARRIER_TIMEOUT)) { + int wait, elapsed; + for_each_netdev(&init_net, dev) if (ic_is_init_dev(dev) && netif_carrier_ok(dev)) goto have_carrier; msleep(1); + + if time_before(jiffies, next_msg) + continue; + + elapsed = jiffies_to_msecs(jiffies - start); + wait = (CONF_CARRIER_TIMEOUT - elapsed + 500)/1000; + pr_info("Waiting up to %d more seconds for network.\n", wait); + next_msg = jiffies + msecs_to_jiffies(CONF_CARRIER_TIMEOUT/12); } have_carrier: rtnl_unlock();
Commit 3fb72f1e6e6165c5f495e8dc11c5bbd14c73385c ("ipconfig wait for carrier") added a "wait for carrier on at least one interface" policy, with a worst case maximum wait of two minutes. However, if you encounter this, you won't get any feedback from the console as to the nature of what is going on. You just see the booting process hang for two minutes and then continue. Here we add a message so the user knows what is going on, and hence can take action to rectify the situation (e.g. fix network cable or whatever.) After the 1st 10s pause, output now begins that looks like this: Waiting up to 110 more seconds for network. Waiting up to 100 more seconds for network. Waiting up to 90 more seconds for network. Waiting up to 80 more seconds for network. ... Since most systems will have no problem getting link/carrier in the 1st 10s, the only people who will see these messages are people with genuine issues that need to be resolved. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> --- net/ipv4/ipconfig.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)