netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: paul.gortmaker@windriver.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipconfig: add informative timeout messages while waiting for carrier
Date: Tue, 02 Apr 2013 14:35:56 -0400 (EDT)	[thread overview]
Message-ID: <20130402.143556.1226949973977697625.davem@davemloft.net> (raw)
In-Reply-To: <1364911105-21734-1-git-send-email-paul.gortmaker@windriver.com>

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.

      reply	other threads:[~2013-04-02 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 13:58 [PATCH net-next] ipconfig: add informative timeout messages while waiting for carrier Paul Gortmaker
2013-04-02 18:35 ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130402.143556.1226949973977697625.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).