public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Rouman <jsr@dex.edzone.net>
To: Baoquan He <bhe@redhat.com>
Cc: Frank Reppin <frank@undermydesk.org>,
	pmenzel@molgen.mpg.de, linux-kernel@vger.kernel.org,
	jroedel@suse.de
Subject: Re: bnx2: broken firware loading
Date: Thu, 10 Nov 2016 13:19:04 -0500 (EST)	[thread overview]
Message-ID: <E1c4twG-0003Bq-JR@dex.edzone.net> (raw)
In-Reply-To: <20161109001909.GB3598@x1>

Did this get pushed upstream?  I see a new patch for 4.8.7 but the BNX2
regression doesn't seem to be fixed.  Or am I missing something?
-- 
Jay Rouman (jsr@edzone.net)
Gratiot/Isabella RESD, Ithaca, MI

> Yes, Paul has reported this. Sorry about this!
> 
> Will work on it right away.
> 
> Thanks
> Baoquan
> 
> On 11/08/16 at 11:50pm, Frank Reppin wrote:
> > Hellos,
> > 
> > ... firmware loading seems to be somewhat broken now with/since
> > 
> > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/ethernet/broadcom/bnx2.c?id=3e1be7ad2d38c6bd6aeef96df9bd0a7822f4e51c
> > 
> > which gives me - on 4.8.6:
> > 
> > bnx2 0000:05:00.0: Direct firmware load for bnx2/bnx2-mips-06-6.2.3.fw
> > failed with error -2
> > 
> > Reverting this commit does fix it (tested on 4.8.6 too) - but it's ofcourse
> > not what you've initially intended.
> > 
> > TIA,
> > Frank Reppin
> > 
> > -- 
> > 43rd Law of Computing:
> >         Anything that can go wr
> > fortune: Segmentation violation -- Core dumped

  reply	other threads:[~2016-11-10 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 22:50 bnx2: broken firware loading Frank Reppin
2016-11-09  0:19 ` Baoquan He
2016-11-10 18:19   ` Jay Rouman [this message]
2016-11-11 12:52     ` Paul Menzel
2016-11-11 13:44       ` Jay Rouman
2016-11-11 13:50         ` 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=E1c4twG-0003Bq-JR@dex.edzone.net \
    --to=jsr@dex.edzone.net \
    --cc=bhe@redhat.com \
    --cc=frank@undermydesk.org \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    /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