From: Bernhard Schmidt <berni@birkenwald.de>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Michael Chan <mchan@broadcom.com>,
Andrew Morton <akpm@linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC
Date: Thu, 19 Mar 2009 19:19:11 +0100 [thread overview]
Message-ID: <20090319181911.GB30702@lxbsc01> (raw)
In-Reply-To: <20090319181536.GA13368@xw6200.broadcom.net>
On Thu, Mar 19, 2009 at 11:15:36AM -0700, Matt Carlson wrote:
> > Would switching the uplink connection to eth1 (and not use eth0 in
> > Linux) give some more clue as well?
> Sure, let's try that. Maybe this is the better way to go anyways. I just
> learned that disabling iLo2 doesn't necessarily disable the management
> firmware on the network device.
>
> For this to be a meaningful test though, we need to verify that the
> driver sign-on messages have a line that reads "ASF[0]" on eth1. Can
> you confirm?
Yes:
[1186598.218205] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1]
WireSpeed[1] TSOcap[1]
[1186598.281314] eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0]
WireSpeed[1] TSOcap[1]
I'll keep the traffic on eth0 now until it breaks again, hopefully
spewing out more debugging info with your patch and then I'll switch to
eth1.
Bernhard
next prev parent reply other threads:[~2009-03-19 18:19 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
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 [this message]
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=20090319181911.GB30702@lxbsc01 \
--to=berni@birkenwald.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@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