Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

netxen_nic firmware hang detected

608 views
Skip to first unread message

Marco Barbero

unread,
Jun 27, 2012, 5:10:02 AM6/27/12
to
Hi.
HP Proliant with a HP NC375T (qlogic chipset)
Debian Squeeze amd64

# lsmod -k

07:00.0 Ethernet controller: NetXen Incorporated NX3031 Multifunction
1/10-Gigabit Server Adapter (rev 42)
Subsystem: Hewlett-Packard Company NC375T PCI Express Quad
Port Gigabit Server Adapter
Kernel driver in use: netxen_nic
07:00.1 Ethernet controller: NetXen Incorporated NX3031 Multifunction
1/10-Gigabit Server Adapter (rev 42)
Subsystem: Hewlett-Packard Company NC375T PCI Express Quad
Port Gigabit Server Adapter
Kernel driver in use: netxen_nic
07:00.2 Ethernet controller: NetXen Incorporated NX3031 Multifunction
1/10-Gigabit Server Adapter (rev 42)
Subsystem: Hewlett-Packard Company NC375T PCI Express Quad
Port Gigabit Server Adapter
Kernel driver in use: netxen_nic
07:00.3 Ethernet controller: NetXen Incorporated NX3031 Multifunction
1/10-Gigabit Server Adapter (rev 42)
Subsystem: Hewlett-Packard Company NC375T PCI Express Quad
Port Gigabit Server Adapter
Kernel driver in use: netxen_nic


# ethtool -i eth4
driver: netxen_nic
version: 4.0.77
firmware-version: 4.0.579
bus-info: 0000:07:00.2


# dpkg -l |grep netxen
ii firmware-netxen 0.35~bpo60+1
Binary firmware for QLogic Intelligent Ethernet (3000 and 3100
Series)

# uname -a
Linux firewall-slave 3.2.12 #1 SMP Wed Mar 21 17:33:10 CET 2012 x86_64 GNU/Linux


I'm experiencing 'firmware hang detected' issue on this quad
sometime it recovers after some seconds
sometime a reboot is needed

I have noticed HP has releases a very new firmware 5.0.0 (4 Jun 2012)
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=4038765&prodNameId=4038767&swEnvOID=4004&swLang=8&mode=2&taskId=135&swItem=MTX-9c4312ff7adb4e6482acf4c1f7

Looking at their docs they say:

Important Information
======================
1) The nx_nic driver uses host-based firmware load. When the user loads the
driver the host-based firmware image in the driver will be the version that
is displayed when checking the firmware version using ethtool. The burned-in
firmware on the device as well as the host-based firmware version can be
verified by checking dmesg for entries similiar to the following:
nx_nic: Flash Version: Firmware[4.0.516], BIOS[2.1.3]
nx_nic: File FW[nx3fwmn.bin] version[4.0.516:12818]


In short: do I need another host-based firmware image after flashing
new firmware from HP? I have checked logs but I cannot find any
entries about flash version, only info about host based firmware:
Jun 20 01:03:50 firewall-slave kernel: [ 8.898253] netxen_nic
0000:07:00.0: loading firmware from phanfw.bin
Jun 20 01:03:50 firewall-slave kernel: [ 10.621102] netxen_nic
0000:07:00.0: firmware v4.0.579 [legacy]
Jun 20 01:03:50 firewall-slave kernel: [ 10.622516] netxen_nic
0000:07:00.1: firmware v4.0.579 [legacy]
Jun 20 01:03:50 firewall-slave kernel: [ 10.623869] netxen_nic
0000:07:00.2: firmware v4.0.579 [legacy]
Jun 20 01:03:50 firewall-slave kernel: [ 10.625266] netxen_nic
0000:07:00.3: firmware v4.0.579 [legacy]


And then (but this is a bit OT, still I try to ask since HP does not
support debian):
HP release the firmware in a file .scexe
This file contain a sh script and a tar.gz
When I run it I get:
gzip: stdin: unexpected end of file

sh -x reveals: tail -n +418 CP017666.scexe gzip -cd
gzip: stdin: unexpected end of file

it looks like a bad tar.gz but according HP this file works on RedHat.
Striping sh part and then issuing 'file' I get:
gzip compressed data, was "scexe_tmp6975", from Unix, last modified:
Mon May 21 23:06:04 2012, max compression

issuing tar xvzf manually, gives always gzip: stdin: unexpected end of file
Have you any clue about that?

thanks


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAOy6k=QEcj8EqNqU1G5G7UKi28Hu...@mail.gmail.com

Camaleón

unread,
Jun 27, 2012, 1:30:02 PM6/27/12
to
On Wed, 27 Jun 2012 11:01:25 +0200, Marco Barbero wrote:

> HP Proliant with a HP NC375T (qlogic chipset) Debian Squeeze amd64
>
> # lsmod -k

(...)

> # dpkg -l |grep netxen
> ii firmware-netxen 0.35~bpo60+1
> Binary firmware for QLogic Intelligent Ethernet (3000 and 3100
> Series)
>
> # uname -a
> Linux firewall-slave 3.2.12 #1 SMP Wed Mar 21 17:33:10 CET 2012 x86_64
> GNU/Linux

Self-compiled kernel with a firmware from backports?

> I'm experiencing 'firmware hang detected' issue on this quad sometime it
> recovers after some seconds sometime a reboot is needed
>
> I have noticed HP has releases a very new firmware 5.0.0 (4 Jun
> 2012)
> http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=4038765&prodNameId=4038767&swEnvOID=4004&swLang=8&mode=2&taskId=135&swItem=MTX-9c4312ff7adb4e6482acf4c1f7
>
> Looking at their docs they say:

(...)

> In short: do I need another host-based firmware image after flashing new
> firmware from HP? I have checked logs but I cannot find any entries
> about flash version, only info about host based firmware:

(...)

How a bout a mass search?

grep -i firmware /var/log/*"

The listed prerequisites are:

***
HP NC-Series QLogic (nx_nic) driver rpm version >= 4.0.540
Firmware version >= 3.4.336 for NC510C and NC510F
Firmware version >= 4.0.230 for all other Products
***

The only problem I see here for using the provided package is that you're
not using a rpm, other than that it should be fine.

> And then (but this is a bit OT, still I try to ask since HP does not
> support debian):
> HP release the firmware in a file .scexe This file contain a sh script
> and a tar.gz When I run it I get:

(...)

> issuing tar xvzf manually, gives always gzip: stdin: unexpected end of
> file Have you any clue about that?

The readme file has more info about it:

***
http://ftp.hp.com/pub/softlib2/software1/sc-linux-fw/p2100299690/v78243/CP017666.txt

Packaging
=========
The firmware upgrade utility is released in scexe format. The file is a single
self-extracting executable that unpacks the component, runs it, and cleans
up the component. This one-step process replaces the rpm format which would
require three steps to install, execute, and remove.
***

In brief, the problem I see here for using that file is the packaging method,
though there's more abut that ".scexe" here:

http://www.lackof.org/matt/hacking/proliant/Debian-ProLiant-Guide.html#firmware-systems

Anyway, have you considered in requesting a firmware update to the BPO guys?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/jsffcq$eg$1...@dough.gmane.org

Marco Barbero

unread,
Jun 28, 2012, 8:20:02 AM6/28/12
to
2012/6/27 Camaleón <noel...@gmail.com> wrote:

>> # uname -a
>> Linux firewall-slave 3.2.12 #1 SMP Wed Mar 21 17:33:10 CET 2012 x86_64
>> GNU/Linux
>
> Self-compiled kernel with a firmware from backports?


Yes, not a smart decision?



>> In short: do I need another host-based firmware image after flashing new
>> firmware from HP? I have checked logs but I cannot find any entries
>> about flash version, only info about host based firmware:

> How a bout a mass search?
>
> grep -i firmware /var/log/*"


nothing only host based firmware entries


> The only problem I see here for using the provided package is that you're
> not using a rpm, other than that it should be fine.

> Anyway, have you considered in requesting a firmware update to the BPO guys?


what is not clear to me is if I need to update both flash based and
host based firmware
Or maybe I just need to update host based and don't touch flash at all?

Looking at debian wiki:
"Many devices require a firmware to operate. Historically, firmware
were built-into the device's ROM or Flash memory, but more and more
often, the firmware has to be loaded into the device by the driver
during the device initialization"


Thanks for your help


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAOy6kTiEAGsdfojL6nQPOhPq...@mail.gmail.com

Camaleón

unread,
Jun 28, 2012, 12:10:02 PM6/28/12
to
On Thu, 28 Jun 2012 14:11:38 +0200, Marco Barbero wrote:

> 2012/6/27 Camaleón <noel...@gmail.com> wrote:
>
>>> # uname -a
>>> Linux firewall-slave 3.2.12 #1 SMP Wed Mar 21 17:33:10 CET 2012 x86_64
>>> GNU/Linux
>>
>> Self-compiled kernel with a firmware from backports?
>
>
> Yes, not a smart decision?

No way, I was kinda thinking out loud ;-)

>>> In short: do I need another host-based firmware image after flashing
>>> new firmware from HP? I have checked logs but I cannot find any
>>> entries about flash version, only info about host based firmware:
>
>> How a bout a mass search?
>>
>> grep -i firmware /var/log/*"
>
>
> nothing only host based firmware entries

Mmm, let's re-read the HP info:

***
When the user loads the driver the host-based firmware image in the
driver will be the version that is displayed when checking the firmware
version using ethtool.
***

So, does it mean that when the kernel module is loaded (netxen_nic →
phanfw.bin) the embedded flash firmware of the adapter becames the same
that the loaded .bin file? If I read it correctly, this is only a notice
not a warning nor a requirement to fulfill :-?

>> The only problem I see here for using the provided package is that
>> you're not using a rpm, other than that it should be fine.
>
>> Anyway, have you considered in requesting a firmware update to the BPO
>> guys?
>
>
> what is not clear to me is if I need to update both flash based and host
> based firmware
> Or maybe I just need to update host based and don't touch flash at all?

(...)

As I see it (but I can be wrong), what happens is that when you load the
kernel module for the card which calls the firmware file, the embedded
flash firmware is superseded by the uploaded bin file, thus not enabled/
used.

My guess is that the embedded flash firmware is only used when the kernel
module cannot locate nor load the required firmware (*.bin) file so it
has to use then the outdated/stock firmware version.

Does it make any sense? O:-)

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/jshvig$no$9...@dough.gmane.org
0 new messages