From: Chad Dupuis <chad.dupuis-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: chad.dupuis-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org
Subject: [PATCH] fcoe: Allow more time for the bnx2x link negotiation before brining up fcoe interfaces.
Date: Wed, 12 Oct 2016 11:32:47 -0400 [thread overview]
Message-ID: <1476286367-30606-1-git-send-email-chad.dupuis@cavium.com> (raw)
bnx2x can take no longer than 3 seconds to initialize the link in some setups
which can cause fipvlan to fail and thus the fcoe interface(s) won't be
created.
Add another 10 seconds to give the link enough time to initialize.
Signed-off-by: Chad Dupuis <chad.dupuis-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
---
modules.d/95fcoe/fcoe-up.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/modules.d/95fcoe/fcoe-up.sh b/modules.d/95fcoe/fcoe-up.sh
index fb3b4c4..ddc87b1 100755
--- a/modules.d/95fcoe/fcoe-up.sh
+++ b/modules.d/95fcoe/fcoe-up.sh
@@ -84,8 +84,8 @@ elif [ "$netdriver" = "bnx2x" ]; then
# If driver is bnx2x, do not use /sys/module/fcoe/parameters/create but fipvlan
modprobe 8021q
udevadm settle --timeout=30
- # Sleep for 3 s to allow dcb negotiation
- sleep 3
+ # Sleep for 13 s to allow dcb negotiation
+ sleep 13
fipvlan "$netif" -c -s
else
vlan="no"
--
1.8.5.6
next reply other threads:[~2016-10-12 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 15:32 Chad Dupuis [this message]
[not found] ` <1476286367-30606-1-git-send-email-chad.dupuis-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2016-10-12 17:02 ` [PATCH] fcoe: Allow more time for the bnx2x link negotiation before brining up fcoe interfaces Dracut GitHub Import Bot
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=1476286367-30606-1-git-send-email-chad.dupuis@cavium.com \
--to=chad.dupuis-ygcgfspz5w/qt0dzr+alfa@public.gmane.org \
--cc=initramfs-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).