From: "Michael Chan" <mchan@broadcom.com>
To: "Jean-Louis Dupond" <info@dupondje.be>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Matthew Carlson" <mcarlson@broadcom.com>,
"David Christensen" <davidch@broadcom.com>
Subject: Re: tg3 driver not advertising 1000mbit
Date: Fri, 12 Jun 2009 15:01:46 -0700 [thread overview]
Message-ID: <1244844106.9225.92.camel@HP1> (raw)
In-Reply-To: <4A32CDE9.7020602@dupondje.be>
On Fri, 2009-06-12 at 14:51 -0700, Jean-Louis Dupond wrote:
> Hello!
>
> Here is a mii-tool -vvv on a box that doesn't advertise gbit speeds! It
> just doesn't advertise gbit @ random, sometimes it does, sometimes not!
> Without any logic in it!
>
> # mii-tool -vvv
> Using SIOCGMIIPHY=0x8947
> eth0: link ok
> registers for MII PHY 1:
> 1000 794d 0143 bed0 05e1 0000 0064 2001
> 0000 0300 0000 0000 0000 0000 0000 3000
Register 1 shows that autoneg did not complete (bit 5 is not set).
The tg3 device has advertised 10/100/1000 in register 4 and register 9,
but registers 5 and 0xa (link partner's advertisement registers are 0).
When it works, these registers should look very different.
Have you tried other cables? What is the link partner?
> 0000 0101 0000 0000 0000 0000 0000 0000
> 7477 0104 0000 ffff 2801 0000 8000 0000
> product info: vendor 00:50:ef, model 45 rev 0
> basic mode: autonegotiation enabled
> basic status: link ok
> capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
> 10baseT-FD 10baseT-HD
> advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-
> control
>
> # dmesg | grep tg3
> [ 3.331702] tg3.c:v3.92.1 (June 9, 2008)
> [ 18.238654] tg3: eth0: Link is up at 10 Mbps, half duplex.
> [ 18.238654] tg3: eth0: Flow control is off for TX and off for RX.
>
>
next prev parent reply other threads:[~2009-06-12 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 14:05 tg3 driver not advertising 1000mbit Jean-Louis Dupond
2009-06-12 18:37 ` Michael Chan
2009-06-12 21:51 ` Jean-Louis Dupond
2009-06-12 22:01 ` Michael Chan [this message]
2009-06-12 22:16 ` Jean-Louis Dupond
2009-06-13 1:31 ` Michael Chan
2009-06-23 18:21 ` Igor Widlinski
2009-06-24 17:36 ` Matt Carlson
2009-06-26 21:33 ` Jean-Louis Dupond
2009-06-27 2:26 ` Matt Carlson
2009-06-27 9:58 ` Jean-Louis Dupond
2009-06-29 18:50 ` Matt Carlson
2009-06-30 9:20 ` Jean-Louis Dupond
2009-07-02 16:42 ` Matt Carlson
2010-11-24 20:09 ` Krzysztof Olędzki
2010-11-24 22:27 ` Jean-Louis Dupond
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=1244844106.9225.92.camel@HP1 \
--to=mchan@broadcom.com \
--cc=davidch@broadcom.com \
--cc=info@dupondje.be \
--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).