From: Baoquan He <bhe@redhat.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Sony Chacko <sony.chacko@qlogic.com>,
Dept-HSGLinuxNICDev@qlogic.com, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
dyoung@redhat.com
Subject: Re: [bnx2] [Regression 4.8] Driver loading fails without firmware
Date: Mon, 31 Oct 2016 18:09:44 +0800 [thread overview]
Message-ID: <20161031100944.GE7138@x1> (raw)
In-Reply-To: <b0675854-41f9-e7b6-4ad0-85ff59b98977@molgen.mpg.de>
Hi Paul,
On 10/26/16 at 12:31pm, Paul Menzel wrote:
> Baoquan, could you please fix this regression. My suggestion is, that you
> add the old code back, but check if the firmware has been loaded. If it
> hasn’t, load it again.
>
> That way, people can update their Linux kernel, and it continues working
> without changing the initramfs, or anything else.
I checked code and this looks good to me. I can post a patch with this
change to upstream, see what maintainers and other reviewers say.
The thing is I don't understand quite well about your requirement. With
my understanding, you just didn't add bnx2 firmware into initramfs, but
later opening the interface can still request that firmware with "ifup
eth-xxx" command. Is that correct? If yes, requeting firmware twice in
probing path and opening path looks good.
However I am wondering what's your exact steps to do this.
What I tried to do is I execute command "dracut --add-drivers bnx2 -f
/boot/initramfs-4.9.0-rc3+.img 4.9.0-rc3+" to build a new initramfs,
meanwhile make sure bnx2.ko is included, then uncompressed initramfs and
deleted bnx2 folder under lib/firmware/ of uncompressed initramfs. Then
pack them to be /boot/initramfs-4.9.0-rc3+.img and restart. I did saw
below failure message. But later how did you really make the bnx2
network interface up? Could you say it more specifically?
[ 7.364186] bnx2: QLogic bnx2 Gigabit Ethernet Driver v2.2.6 (January 29, 2014)
[ 7.371706] ACPI: PCI Interrupt Link [LN44] enabled at IRQ 44
[ 7.378128] bnx2 0000:01:00.0: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
[ 7.387619] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"
[ 7.387888] bnx2: probe of 0000:01:00.0 failed with error -2
[ 7.388990] ACPI: PCI Interrupt Link [LN45] enabled at IRQ 45
[ 7.389370] bnx2 0000:01:00.1: Direct firmware load for bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
[ 7.389371] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"
[ 7.389475] bnx2: probe of 0000:01:00.1 failed with error -2
Thanks
Baoquan
next prev parent reply other threads:[~2016-10-31 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 14:33 [bnx2] [Regression 4.8] Driver loading fails without firmware Paul Menzel
2016-10-25 15:24 ` Rick Jones
2016-10-25 15:31 ` Paul Menzel
2016-10-25 15:40 ` Rick Jones
2016-10-26 10:31 ` Paul Menzel
2016-10-26 12:00 ` Baoquan He
2016-10-27 13:21 ` Paul Menzel
2016-10-27 18:16 ` Mody, Rasesh
2016-10-29 2:55 ` Baoquan He
2016-10-30 11:05 ` Paul Menzel
2016-10-31 3:59 ` Baoquan He
2016-10-31 6:38 ` Baoquan He
2016-10-31 10:09 ` Baoquan He [this message]
2016-10-31 10:43 ` Paul Menzel
2016-11-01 2:40 ` Baoquan He
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=20161031100944.GE7138@x1 \
--to=bhe@redhat.com \
--cc=Dept-HSGLinuxNICDev@qlogic.com \
--cc=davem@davemloft.net \
--cc=dyoung@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=sony.chacko@qlogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.