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: Mon, 23 Mar 2009 11:18:59 -0700 [thread overview]
Message-ID: <20090323181859.GA5473@xw6200.broadcom.net> (raw)
In-Reply-To: <20090322132121.GA7871@pest>
On Sun, Mar 22, 2009 at 06:21:21AM -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?
> > 2) Can you apply the following patch to get more information on when
> > MMIO gets disabled?
>
> Not sure this is going to help you. NIC crashed two times tonight, logs
> look like this
Actually, it does. :)
> Mar 22 04:06:46 svr02 kernel: [1392136.468921] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:47 svr02 kernel: [1392137.520288] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:48 svr02 kernel: [1392138.568267] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:49 svr02 kernel: [1392139.616266] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:50 svr02 kernel: [1392140.664266] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:51 svr02 kernel: [1392141.712276] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:52 svr02 kernel: [1392142.760297] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:53 svr02 kernel: [1392143.808258] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:54 svr02 kernel: [1392144.856256] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:55 svr02 kernel: [1392145.904266] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:56 svr02 kernel: [1392146.952276] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:57 svr02 kernel: [1392148.000267] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:58 svr02 kernel: [1392149.048271] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:06:59 svr02 kernel: [1392150.096268] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:00 svr02 kernel: [1392151.144277] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:01 svr02 kernel: [1392152.192287] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:02 svr02 kernel: [1392153.240268] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:03 svr02 kernel: [1392154.288267] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:04 svr02 kernel: [1392155.336267] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:05 svr02 kernel: [1392156.384268] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:07 svr02 kernel: [1392157.432267] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:08 svr02 kernel: [1392158.480266] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:09 svr02 kernel: [1392159.528289] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:10 svr02 kernel: [1392160.576297] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:11 svr02 kernel: [1392161.624277] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:12 svr02 kernel: [1392162.672267] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:13 svr02 kernel: [1392163.720266] PCI Memory Mapped IO Disabled!!!!
> Mar 22 04:07:14 svr02 kernel: [1392164.768266] PCI Memory Mapped IO Disabled!!!!
>
> at this point the "watchdog" kicked in and did rmmod/modprobe, so I
> think the only thing you can read out of this debugging log is that
> there was no kernel message right before MMIO got disabled and it takes
> quite a while to fire the Tx timeout.
So traffic on this box must be pretty light for the watchdog to fire off
30 seconds after the MMIO problem was detected, right? Interesting.
> Mar 22 04:07:15 svr02 kernel: [1392165.540078] tg3 0000:03:04.1: PCI INT B disabled
> Mar 22 04:07:16 svr02 kernel: [1392166.817125] tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
> Mar 22 04:07:18 svr02 kernel: [1392168.398844] tg3: eth0: No firmware running.
> Mar 22 04:07:29 svr02 kernel: [1392179.793309] tg3: eth0: Link is down.
> Mar 22 04:07:31 svr02 kernel: [1392181.896030] tg3 0000:03:04.0: PCI INT A disabled
> Mar 22 04:07:33 svr02 kernel: [1392183.957132] tg3.c:v3.94 (August 14, 2008)
> Mar 22 04:07:33 svr02 kernel: [1392184.020034] tg3 0000:03:04.0: enabling device (0000 -> 0002)
> Mar 22 04:07:33 svr02 kernel: [1392184.086083] tg3 0000:03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>
> I'm now switching to eth1.
O.K. I eagerly await your results.
next prev parent reply other threads:[~2009-03-23 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
2009-03-22 13:21 ` Bernhard Schmidt
2009-03-23 18:18 ` Matt Carlson [this message]
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=20090323181859.GA5473@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).