From: Jon Mason <jdmason@us.ibm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: ethtool -d no longer works for e1000
Date: Wed, 9 Mar 2005 17:13:55 -0600 [thread overview]
Message-ID: <200503091713.55454.jdmason@us.ibm.com> (raw)
In-Reply-To: <422F822D.9010707@candelatech.com>
I don't see this problem at all on my 2.6.11-rc4-mm1 kernel (Athlon64 proc).
# ethtool -i eth0
driver: e1000
version: 5.7.6-k2
firmware-version: N/A
bus-info: 0000:00:07.0
# ethtool -d eth0
MAC Registers
-------------
0x00000: CTRL (Device control register) 0x00F00249
Duplex: full
Endian mode (buffers): little
Link reset: reset
Set link up: 1
Invert Loss-Of-Signal: no
Receive flow control: disabled
Transmit flow control: disabled
VLAN mode: disabled
Auto speed detect: disabled
Speed select: 1000Mb/s
Force speed: no
Force duplex: no
0x00008: STATUS (Device status register) 0x0000C343
Duplex: full
Link up: link config
TBI mode: disabled
Link speed: 100Mb/s
Bus type: PCI
Bus speed: 33MHz
Bus width: 32-bit
0x00100: RCTL (Receive control register) 0x00008002
Receiver: enabled
Store bad packets: disabled
Unicast promiscuous: disabled
Multicast promiscuous: disabled
Long packet: disabled
Descriptor minimum threshold size: 1/2
Broadcast accept mode: accept
VLAN filter: disabled
Cononical form indicator: disabled
Discard pause frames: filtered
Pass MAC control frames: don't pass
Receive buffer size: 2048
0x02808: RDLEN (Receive desc length) 0x00001000
0x02810: RDH (Receive desc head) 0x00000003
0x02818: RDT (Receive desc tail) 0x00000000
0x02820: RDTR (Receive delay timer) 0x00000000
0x00400: TCTL (Transmit ctrl register) 0x000400FA
Transmitter: enabled
Pad short packets: enabled
Software XOFF Transmission: disabled
Re-transmit on late collision: disabled
0x03808: TDLEN (Transmit desc length) 0x00001000
0x03810: TDH (Transmit desc head) 0x000000D8
0x03818: TDT (Transmit desc tail) 0x000000D8
0x03820: TIDV (Transmit delay timer) 0x00000040
PHY type: M88
# uname -a
Linux victory 2.6.11-rc4-mm1 #4 Fri Feb 25 18:19:43 CST 2005 x86_64 AMD
Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
On Wednesday 09 March 2005 05:09 pm, Ben Greear wrote:
> Ganesh Venkatesan wrote:
> > Ben:
> >
> > Are you using the e1000 that is included in the 2.6.11 kernel? ethtool
> > -d eth? works fine for me. What else is different in your env?
>
> I have patched the e1000 in my 2.6.11 kernel, but I see this -d problem
> on other un-patched systems as well, so it can't be (just) my patches
> that are the problem.
>
> I also tried this on my x86-64 opteron system, running FC3. I
> have not hacked up this kernel or user-space tools at all :)
>
> [root@grok lanforge]# ethtool -i eth3
> driver: e1000
> version: 5.5.4-k2-NAPI
> firmware-version: N/A
> bus-info: 0000:02:08.0
> [root@grok lanforge]# ethtool -d eth3
> Cannot dump registers: Success
> [root@grok lanforge]# uname -a
> Linux grok 2.6.10-1.766_FC3smp #1 SMP Wed Feb 9 23:17:48 EST 2005 x86_64
> x86_64 x86_64 GNU/Linux
>
>
> I'm using ethtool 1.8 on this system.
>
>
> What version of ethtool are you using?
--
Jon Mason
jdmason@us.ibm.com
next prev parent reply other threads:[~2005-03-09 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 21:35 ethtool -d no longer works for e1000 Ben Greear
2005-03-09 22:09 ` Ganesh Venkatesan
2005-03-09 23:09 ` Ben Greear
2005-03-09 23:13 ` Jon Mason [this message]
2005-03-09 23:31 ` Ben Greear
2005-03-09 23:42 ` Ben Greear
2005-03-11 8:54 ` Lennert Buytenhek
2005-03-11 8:55 ` Lennert Buytenhek
2005-03-09 22:59 ` Andre Tomt
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 22:25 cramerj
2005-03-09 23:02 ` Ben Greear
2005-03-10 0:35 cramerj
2005-03-10 0:54 ` Jon Mason
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=200503091713.55454.jdmason@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=ganesh.venkatesan@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
/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).