From: "Michael Chan" <mchan@broadcom.com>
To: "Mills, Tony" <tony.mills@jagex.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2 cards intermittantly going offline
Date: Tue, 18 Jan 2011 09:55:58 -0800 [thread overview]
Message-ID: <1295373358.8131.4.camel@HP1> (raw)
In-Reply-To: <6DD3782C33561D44B47071B09946026405F63853AB@exchange1>
On Tue, 2011-01-18 at 02:54 -0800, Mills, Tony wrote:
> Last night i setup a machine to monitor overnight and at 3:52 this
> morning it became unresponsive.
>
When it becomes unresponsive, please send some packets to the NIC (such
as ping) and monitor statistics with ethtool -S. See if the packets are
being received or discarded. Also, run tcpdump on the machine to see if
the packets are properly received by the stack. Thanks.
next prev parent reply other threads:[~2011-01-18 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 10:54 bnx2 cards intermittantly going offline Mills, Tony
2011-01-18 17:55 ` Michael Chan [this message]
2011-01-26 12:44 ` Mills, Tony
2012-09-13 13:51 ` Marc A. Donges
2012-09-13 15:45 ` Sven Ulland
2012-09-13 20:30 ` Michael Chan
2012-09-16 3:47 ` Ben Hutchings
2011-11-15 17:41 ` Ken
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=1295373358.8131.4.camel@HP1 \
--to=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=tony.mills@jagex.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).