linux-kernel - RE: bnx2x in 4.6rc7 with FW 7.13.1.0 not present

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 10 May 2016 05:22:38 +0000
From:	Yuval Mintz <Yuval.Mintz@...gic.com>
To:	"Elliott, Robert (Persistent Memory)" <elliott@....com>
CC:	netdev <netdev@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ariel Elior <Ariel.Elior@...gic.com>,
	"David Miller" <davem@...emloft.net>
Subject: RE: bnx2x in 4.6rc7 with FW 7.13.1.0 not present

> Upgrading a system from kernel 4.2 to 4.6rc7, there is an extra 2 minute delay
> while booting due to these problems:
> 
>     [   47.977221] bnx2x 0000:04:00.1: Direct firmware load for bnx2x/bnx2x-e2-
> 7.13.1.0.fw failed with error -2
... 
> Could the driver fall back to an older firmware version more gracefully?

No.

The internal FW isn't necessarily backward compatible [there are some
Compatibility in fastpath in order to support VFs, but not in general].
Doing what you ask would means filling the driver with a lot of legacy code
for older FWs, adding per-FW version HSI files, etc.

So in short - if you've installed a fresh kernel on top of an existing distro
that lacked the latest firmware in its filesystem, getting that missing 
.bin file from linux-firmware is the way to go.

Cheers,
Yuval