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>,
dvteam@molgen.mpg.de, dyoung@redhat.com
Subject: Re: [bnx2] [Regression 4.8] Driver loading fails without firmware
Date: Mon, 31 Oct 2016 11:59:30 +0800 [thread overview]
Message-ID: <20161031035930.GB7138@x1> (raw)
In-Reply-To: <1477825531.980.9.camel@molgen.mpg.de>
Hi Paul,
On 10/30/16 at 12:05pm, Paul Menzel wrote:
> Dear Baoquan,
>
>
> Am Samstag, den 29.10.2016, 10:55 +0800 schrieb Baoquan He:
> > On 10/27/16 at 03:21pm, 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 saw your mail but I am also not familiar with bnx2 driver. As the
> > > > commit log says I just tried to make bnx2 driver reset itself earlier.
> > > >
> > > > So you did a git bisect and found this commit caused the regression,
> > > > right? If yes, and network developers have no action, I will look into
> > > > the code and see if I have idea to fix it.
> > >
> > > Well, I looked through the commits and found that one, which would explain
> > > the changed behavior.
> > >
> > > To be sure, and to follow your request, I took Linux 4.8.4 and reverted your
> > > commit (attached). Then I deleted the firmware again from the initramfs, and
> > > rebooted. The devices showed up just fine as before.
> > >
> > > So to summarize, the commit is indeed the culprit.
>
> > Sorry for this.
> >
> > Could you tell the steps to reproduce? I will find a machine with bnx2
> > NIC and check if there's other ways.
>
> Well, delete the bnx2 firmware files from the initramfs, and start the
> system.
>
> Did you read my proposal, to try to load the firmware twice, that means,
> basically revert only the deleted lines of your commit, and add an
> additional check?
Thanks for your information!
I got a x86_64 system with bnx2 NIC, and clone Linus's git tree into
that system. Then building a new kernel 4.9.0-rc3+ with new initramfs.
But when I uncompressed the new initramfs, didn't find bnx2 related
firmware, no bnx2 files under lib/firmware of uncompressed initramfs
folder. While I did see them in /lib/firmware/bnx2/bnx2-xxxxx.fw. Could
you please say it more specifically how I should do to reproduce the
failure you encountered? I think your proposal looks good, just need a
test before post.
Thanks
Baoquan
next prev parent reply other threads:[~2016-10-31 3:59 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 [this message]
2016-10-31 6:38 ` Baoquan He
2016-10-31 10:09 ` Baoquan He
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=20161031035930.GB7138@x1 \
--to=bhe@redhat.com \
--cc=Dept-HSGLinuxNICDev@qlogic.com \
--cc=davem@davemloft.net \
--cc=dvteam@molgen.mpg.de \
--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 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).