From: "Peter Huang(Peng)" <peter.huangpeng@huawei.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Majun <harry.majun@huawei.com>, <netdev@vger.kernel.org>,
Zhoukang <zhoukang7@huawei.com>
Subject: intel 82580 nic hang problem.
Date: Tue, 2 Apr 2013 21:56:21 +0800 [thread overview]
Message-ID: <515AE385.7040006@huawei.com> (raw)
Hi Eric
Here I have a nic hang problem in our customer environment, from Intel's 82575
driver release notes, there was a similar problem, but only occurred with older
linux 2.6 kernel ( we are using 3.0.13-0.27-xen kernel).
We are using 82580 dual port NIC:
#ethtool -i eth1
driver: igb
version: 3.0.6-k2
firmware-version: 3.2-9
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
Below is the error message (this msg will repeated over 8 hours):
Mar 28 10:46:25 CNA001_0_010203 kernel: [ 4412.812078] igb 0000:02:00.1: eth1: Reset adapter
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816189] igb 0000:02:00.1: Detected Tx Unit Hang
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816191] Tx Queue <1>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816191] TDH <0>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816192] TDT <2>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816192] next_to_use <2>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816193] next_to_clean <0>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816193] buffer_info[next_to_clean]
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816194] time_stamp <1000fb54c>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816194] next_to_watch <0>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816195] jiffies <1000fb649>
Mar 28 10:46:31 CNA001_0_010203 kernel: [ 4418.816196] desc.status <118000>
Are you familiar with this problem, or could you give us any suggestion to move on?
Thanks very much!
Peter.Huang
reply other threads:[~2013-04-02 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=515AE385.7040006@huawei.com \
--to=peter.huangpeng@huawei.com \
--cc=eric.dumazet@gmail.com \
--cc=harry.majun@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=zhoukang7@huawei.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).