From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Bernhard Schmidt" <berni@birkenwald.de>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
"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 11:15:36 -0700 [thread overview]
Message-ID: <20090319181536.GA13368@xw6200.broadcom.net> (raw)
In-Reply-To: <20090319180644.GA30702@lxbsc01>
On Thu, Mar 19, 2009 at 11:06:44AM -0700, Bernhard Schmidt wrote:
> On Thu, Mar 19, 2009 at 09:58:42AM -0700, Matt Carlson wrote:
>
> Hello Matt,
>
> > Hi Bernhard. I talked to Michael about this and we'd like you to try
> > two things.
> >
> > 1) Can you disable iLo2 and see if you can still reproduce the problem?
>
> That will take a few days, I'll ask the on-site guys to check whether we
> have an external IP-KVM available.
>
> 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?
> > 2) Can you apply the following patch to get more information on when
> > MMIO gets disabled?
>
> Applied, I'll send you the information as soon as it happens again
> (which seems to be happening rather often the last couple of days).
Thanks.
next prev parent reply other threads:[~2009-03-19 18:16 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 [this message]
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=20090319181536.GA13368@xw6200.broadcom.net \
--to=mcarlson@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=berni@birkenwald.de \
--cc=bugme-daemon@bugzilla.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).