From: "Matt Carlson" <mcarlson@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "mikpe@it.uu.se" <mikpe@it.uu.se>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Matthew Carlson" <mcarlson@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>
Subject: Re: [2.6.35-rc1 regression] tg3 vpd r/w failed
Date: Tue, 1 Jun 2010 16:28:47 -0700 [thread overview]
Message-ID: <20100601232847.GA16274@mcarlson.broadcom.com> (raw)
In-Reply-To: <20100601.153209.135521213.davem@davemloft.net>
On Tue, Jun 01, 2010 at 03:32:09PM -0700, David Miller wrote:
>
> Mikael I'm getting tired of continuing to add the proper
> mailing list CC: for your sparc bug reports. Please make
> sure to add sparclinux@vger.kernel.org to your reports
> in the future.
>
> Thanks.
>
> > Booting 2.6.35-rc1 on a Sun Blade 2500 Red with builtin tg3 I get:
> >
> > tg3.c:v3.110 (April 9, 2010)
> > PCI: Enabling device: (0000:00:03.0), cmd 2
> > ...
> > tg3 0000:00:03.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update.
> > tg3 0000:00:03.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update.
> > tg3 0000:00:03.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update.
> > tg3 0000:00:03.0: eth0: Tigon3 [partno(none) rev 1002] (PCI:66MHz:64-bit) MAC address ...
> > tg3 0000:00:03.0: eth0: attached PHY is 5703 (10/100/1000Base-T Ethernet) (WireSpeed[1])
> > tg3 0000:00:03.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
> > tg3 0000:00:03.0: eth0: dma_rwctrl[763f0000] dma_mask[32-bit]
> > ...
> > tg3 0000:00:03.0: eth0: No firmware running
> > tg3 0000:00:03.0: eth0: Link is up at 100 Mbps, full duplex
> > tg3 0000:00:03.0: eth0: Flow control is on for TX and on for RX
> >
> > The three 'vpd r/w failed' messages are new and did not occur with 2.6.34
> > or earlier kernels.
These messages are originating from the PCI layer. It looks like your
device does not have NVRAM, which is a known issue. I have an idea on
how to reduce the noise, but let me investigate it a little more before
I commit to it.
prev parent reply other threads:[~2010-06-01 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 20:03 [2.6.35-rc1 regression] tg3 vpd r/w failed Mikael Pettersson
2010-06-01 22:32 ` David Miller
2010-06-01 23:28 ` Matt Carlson [this message]
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=20100601232847.GA16274@mcarlson.broadcom.com \
--to=mcarlson@broadcom.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@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