netdev - "NIG timer max" messages from bnx2x

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-next>] [day] [month] [year] [list]

Message-ID: <4B168F04.60309@redpill-linpro.com>
Date:	Wed, 02 Dec 2009 17:00:04 +0100
From:	Tore Anderson <tore.anderson@...pill-linpro.com>
To:	netdev@...r.kernel.org
Subject: "NIG timer max" messages from bnx2x

Hello list,

I'm having a strange error condition I'm hoping someone here might be
able to help me get to the bottom of.  I've got a HP blade enclosure
with a Nortel switch module, and one of the blades are running VMWare
ESX.  When I turn on this blade (or enable its switch port), the entire
network stops working after a short while.  Other server blades can no
longer communicate, for instance.  The only clue I've found so far is
the following error message from one of the other blades that's running
CentOS 5.4:

[bnx2x_hw_stats_update:3701(eth0)]NIG timer max (426)

The line is logged every two seconds and the number in parenthesis is
incrementing each time.  Once I disable the port to the ESX server, the
network instantly recovers.

I have no reason to believe the Linux kernel/bnx2x is doing anything
wrong here, but I'm wondering if anybody has any idea on what this error
message means and what could be causing it?  I can't see anything
unusual going on with tcpdump, and the error counters in "ip -s -s link
show eth0" are all zero.

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html