From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-GLgANOly0l1BDLzU/O5InQ@public.gmane.org
Subject: Re: NFSROOT mount fails on SPARC after 2.6.37
Date: Fri, 04 Nov 2011 22:03:34 -0400 (EDT) [thread overview]
Message-ID: <20111104.220334.1213367819937218830.davem@davemloft.net> (raw)
In-Reply-To: <119BC4C8-E1AB-4415-AF00-B183FC7EB16A-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Should be fixed by:
commit 3fb72f1e6e6165c5f495e8dc11c5bbd14c73385c
Author: Micha Nelissen <micha-NMpVyAPB7R5Fb86tMAXRjw@public.gmane.org>
Date: Thu May 19 10:14:06 2011 +0000
ipconfig wait for carrier
v3 -> v4: fix return boolean false instead of 0 for ic_is_init_dev
Currently the ip auto configuration has a hardcoded delay of 1 second.
When (ethernet) link takes longer to come up (e.g. more than 3 seconds),
nfs root may not be found.
Remove the hardcoded delay, and wait for carrier on at least one network
device.
Signed-off-by: Micha Nelissen <micha-NMpVyAPB7R5Fb86tMAXRjw@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Signed-off-by: David S. Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-05 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1320429339.53513.YahooMailNeo@web24704.mail.ird.yahoo.com>
2011-11-04 23:15 ` NFSROOT mount fails on SPARC after 2.6.37 Chuck Lever
[not found] ` <119BC4C8-E1AB-4415-AF00-B183FC7EB16A-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-11-05 2:03 ` David Miller [this message]
[not found] ` <20111104.220334.1213367819937218830.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-11-05 2:38 ` Trond Myklebust
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=20111104.220334.1213367819937218830.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-GLgANOly0l1BDLzU/O5InQ@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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