netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eilon Greenstein" <eilong@broadcom.com>
To: "Tore Anderson" <tore.anderson@redpill-linpro.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Benjamin Li" <benli@broadcom.com>
Subject: Re: "NIG timer max" messages from bnx2x
Date: Wed, 2 Dec 2009 20:41:03 +0200	[thread overview]
Message-ID: <1259779263.2020.6.camel@lb-tlvb-eilong> (raw)
In-Reply-To: <4B168F04.60309@redpill-linpro.com>

On Wed, 2009-12-02 at 08:00 -0800, Tore Anderson wrote:
> 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.

This message indicates that for over 1 second, the device could not
transmit anything to the network (the same packet was not transmitted
for over one second) - this usually happens when the network is in fatal
condition - usually because some device is sending constant pause stream
that halts all traffic. In this case, the device is incrementing the
counter and drains outgoing traffic - without this action, the device
will not be able to unload since even the commands from the driver will
not be processed due to this excessive back pressure.

As you indicated - once you remove the server that halts all other
traffic, everything else resumes - that indicates that this server is
sending constant pause that ultimately halts the entire switch.

Regards,
Eilon



  reply	other threads:[~2009-12-02 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 16:00 "NIG timer max" messages from bnx2x Tore Anderson
2009-12-02 18:41 ` Eilon Greenstein [this message]
2009-12-03  7:36   ` Tore Anderson
2009-12-03  7:47     ` Eilon Greenstein

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=1259779263.2020.6.camel@lb-tlvb-eilong \
    --to=eilong@broadcom.com \
    --cc=benli@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=tore.anderson@redpill-linpro.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).