public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-linux-net@schottelius.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-net@vger.kernel.org
Subject: Re: Slow Networking in 2.5/2.6 [reasons]
Date: Sun, 18 Jan 2004 23:13:08 +0100	[thread overview]
Message-ID: <20040118221308.GA13026@schottelius.org> (raw)
In-Reply-To: <20040114091207.GA8207@schottelius.org>


[-- Attachment #1.1: Type: text/plain, Size: 1261 bytes --]

Well, now I have some more information, which make me wonder:

I am currently trying to debug the rtl8139 card:

00:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)

00:05.0 Class 0200: 10ec:8139 (rev 10)

Subsystem: 10ec:8139
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
        Latency: 64 (8000ns min, 16000ns max)
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at d600 [size=256]
        Region 1: Memory at effaee00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3h
ot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

What makes me wondering is the attached output of mii-diag and
8139-diag, can somebody tell me why the values are non standard and
why the flow control is disabled?

Greetings,

Nico

-- 
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A          | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org

[-- Attachment #1.2: rtldiag --]
[-- Type: text/plain, Size: 2084 bytes --]

rtl8139-diag.c:v2.12 12/03/2003 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a RealTek RTL8139 adapter at 0xd600.
The RealTek chip appears to be active, so some registers will not be read.
To see all register values use the '-f' flag.
RealTek chip registers at 0xd600
 0x000: bae60a00 0000c2f6 80000000 40000040 0010a10a 0010a5ea 0010a08a 0010a5ea
 0x020: 0cb76000 0cb76600 0cb76c00 0cb77200 13530000 0d0a0000 658c657c 0000c07f
 0x040: 74400680 0000f78e f0a87d28 00000000 008d1000 00000000 0088c510 00100000
 0x060: 1100f00f 01e1782d 000141e1 00000000 00000704 000207c8 60f60c59 7b732660.
Realtek station address 00:0a:e6:ba:f6:c2, chip type 'rtl8139C'.
  Receiver configuration: Normal unicast and hashed multicast
     Rx FIFO threshold 2048 bytes, maximum burst 2048 bytes, 32KB ring
  Transmitter enabled with NONSTANDARD! settings, maximum burst 1024 bytes.
    Tx entry #0 status 0010a10a complete, 266 bytes.
    Tx entry #1 status 0010a5ea complete, 1514 bytes.
    Tx entry #2 status 0010a08a complete, 138 bytes.
    Tx entry #3 status 0010a5ea complete, 1514 bytes.
  Flow control: Tx disabled  Rx disabled.
  The chip configuration is 0x10 0x8d, MII half-duplex mode.
  No interrupt sources are pending.
Decoded EEPROM contents:
   PCI IDs -- Vendor 0xd942, Device 0xffff.
   PCI Subsystem IDs -- Vendor 0x10ec, Device 0x8139.
   PCI timer settings -- minimum grant 32, maximum latency 64.
  General purpose pins --  direction 0xe5  value 0x12.
  Station Address 00:0A:E6:BA:F6:C2.
  Configuration register 0/1 -- 0x8d / 0xc2.
 EEPROM active region checksum is 0c88.
 The RTL8139 does not use a MII transceiver.
 It does have internal MII-compatible registers:
   Basic mode control register   0x1100.
   Basic mode status register    0x782d.
   Autonegotiation Advertisement 0x01e1.
   Link Partner Ability register 0x41e1.
   Autonegotiation expansion     0x0001.
   Disconnects                   0x0000.
   False carrier sense counter   0x0000.
   NWay test register            0x0704.
   Receive frame error count     0x0000.

[-- Attachment #1.3: miidiag --]
[-- Type: text/plain, Size: 432 bytes --]

Using the default interface 'eth0'.
Basic registers of MII PHY #32:  1100 782d 0000 0000 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x1100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-01-18 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14  9:12 Slow Networking in 2.5/2.6 Nico Schottelius
2004-01-18 22:13 ` Nico Schottelius [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=20040118221308.GA13026@schottelius.org \
    --to=nico-linux-net@schottelius.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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