From: "Michael Chan" <mchan@broadcom.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>,
"berni@birkenwald.de" <berni@birkenwald.de>
Subject: Re: [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC
Date: Mon, 16 Mar 2009 14:23:21 -0700 [thread overview]
Message-ID: <1237238601.8839.85.camel@HP1> (raw)
In-Reply-To: <20090315143214.90c71fb7.akpm@linux-foundation.org>
On Sun, 2009-03-15 at 14:32 -0700, Andrew Morton wrote:
> > [784063.389142] tg3: eth0: transmit timed out, resetting
> > [784063.447106] tg3: DEBUG: MAC_TX_STATUS[ffffffff] MAC_RX_STATUS[ffffffff]
> > [784063.524104] tg3: DEBUG: RDMAC_STATUS[ffffffff] WDMAC_STATUS[ffffffff]
At the time of tx timeout, the registers all return 0xffffffff. Does
the subsequent reset bring the device back? If the device is brought
back, there should be a link up message and traffic should resume. If
not, please provide lspci -vvvxxx on the eth0 device after the failure.
Also, when one ethernet port fails, does the other port (from the same
dual port device) function ok?
Thanks.
next prev parent reply other threads:[~2009-03-16 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12877-10286@http.bugzilla.kernel.org/>
2009-03-15 21:32 ` [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC Andrew Morton
2009-03-16 21:23 ` Michael Chan [this message]
2009-03-16 22:46 ` Bernhard Schmidt
2009-03-17 22:09 ` Bernhard Schmidt
2009-03-17 23:30 ` Michael Chan
2009-03-19 16:58 ` Matt Carlson
2009-03-19 18:06 ` Bernhard Schmidt
2009-03-19 18:15 ` Matt Carlson
2009-03-19 18:19 ` Bernhard Schmidt
2009-03-22 13:21 ` Bernhard Schmidt
2009-03-23 18:18 ` Matt Carlson
2009-03-24 0:35 ` Bernhard Schmidt
2009-03-31 16:26 ` Matt Carlson
2009-03-31 22:16 ` Bernhard Schmidt
2009-04-13 21:54 ` Bernhard Schmidt
2009-04-14 18:29 ` Matt Carlson
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=1237238601.8839.85.camel@HP1 \
--to=mchan@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=berni@birkenwald.de \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).