AW: [vortex] Slow connection in local domain

[Suikat, Reiner]

Andrew,

thanks for your rapid reply!!
Here is the output you asked for:

insmod 3c59x debug=7
/etc/init.d/network start

May 17 15:25:20 beetlejuice kernel: 3c59x.c:LK1.1.13 27 Jan 2001  Donald
Becker and others. http://www.scyld.com/network/vortex.html
May 17 15:25:20 beetlejuice kernel: See Documentation/networking/vortex.txt
May 17 15:25:20 beetlejuice kernel: eth0: 3Com PCI 3c905C Tornado at 0xfb00,
00:00:39:71:33:24, IRQ 11
May 17 15:25:20 beetlejuice kernel:   product code 0000 rev 00.11 date
00-00-00
May 17 15:25:20 beetlejuice kernel: Full duplex capable
May 17 15:25:20 beetlejuice kernel:   8K byte-wide RAM 5:3 Rx:Tx split,
autoselect/Autonegotiate interface.
May 17 15:25:20 beetlejuice kernel:   MII transceiver found at address 24,
status 782d.
May 17 15:25:20 beetlejuice kernel:   Enabling bus-master transmits and
whole-frame receives.
May 17 15:25:20 beetlejuice kernel: eth0: scatter/gather enabled. h/w
checksums enabled
Mai 17 15:25:27 beetlejuice sysctl: net.ipv4.ip_forward = 0
Mai 17 15:25:27 beetlejuice sysctl: net.ipv4.conf.all.rp_filter = 1
Mai 17 15:25:27 beetlejuice network: Setting network parameters:  succeeded
Mai 17 15:25:27 beetlejuice network: Bringing up interface lo:  succeeded
May 17 15:25:28 beetlejuice kernel: eth0: using NWAY device table, not 8
May 17 15:25:28 beetlejuice kernel: eth0: MII #24 status 782d, link partner
capability 0021, info1 8010, setting full-duplex.
Mai 17 15:25:28 beetlejuice network: Bringing up interface eth0:  succeeded


vortex-diag -aaee

vortex-diag.c:v2.05 5/15/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xfb00.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
  Window 0: 0000 0000 0000 0000 fdfd 00bf ffff 0000.
  Window 1: FIFO FIFO 0700 0000 0000 003f 0000 2000.
  Window 2: 0000 7139 2433 0000 0000 0000 0002 4000.
  Window 3: 0000 0180 05ea 0020 000a 0800 0800 6000.
  Window 4: 0000 0000 0000 0cf6 0001 8880 0300 8000.
  Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000.
  Window 6: 0000 0000 0000 9f01 0100 58b3 0000 c000.
  Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xfb00
  0xFB10: **FIFO** 00000000 0000000a *STATUS*
  0xFB20: 00000020 00000000 00080000 00000004
  0xFB30: 00000000 c1ff3e01 063771c0 00080004
 Indication enable is 06c6, interrupt enable is 06ce.
 No interrupt sources are pending.
 Transceiver/media interfaces available:  100baseTx 10baseT.
Transceiver type in use:  Autonegotiate.
 MAC settings: full-duplex.
 Station address set to 00:00:39:71:33:24.
 Configuration options 0002.
EEPROM contents (64 words, offset 0):
 0x000: 0000 3971 3324 9200 0000 0000 0000 0000
 0x008: 2940 0000 0000 3971 3324 8010 0000 00aa
 0x010: 72a2 0000 0000 0180 0000 0000 0429 1179
 0x018: 0001 000a 0002 2900 ff6b 6b6b 0000 0000
 0x020: 0000 ffff fff0 0000 0000 0000 0000 0000
 0x028: 0000 0000 0000 0000 0000 0000 0000 0000
 0x030: ffff ffff ffff ffff ffff ffff ffff ffff
 0x038: ffff ffff ffff ffff ffff ffff ffff ffff
 The word-wide EEPROM checksum is 0x32aa.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
 3Com Node Address 00:00:39:71:33:24 (used as a unique ID only).
 OEM Station address 00:00:39:71:33:24 (used as the ethernet address).
 Manufacture date (MM/DD/YYYY) 0/0/2000, division  , product   .
 Options: force full duplex, link beat required.
  Vortex format checksum is incorrect (0090 vs. 1179).
  Cyclone format checksum is incorrect (0xde vs. 00).
  Hurricane format checksum is incorrect (0x61 vs. 00).



mii-diag -v

mii-diag.c:v2.01a 5/15/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
 MII PHY #24 transceiver registers:
   3000 782d 0040 6174 05e1 0021 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   1000 0001 0000 0000 0000 0000 0100 0000
   003c d006 0f00 ff40 002c 0000 0080 000b The autonegotiated capability is
0000.
No common media type was autonegotiated!
This is extremely unusual and typically indicates a configuration error.
Perhaps the advertised capability set was intentionally limited.
 Basic mode control register 0x6d64: Auto-negotiation disabled, with
 Speed fixed at 100 mbps, full-duplex.
  Transceiver isolated from the MII!
  Transceiver powered down!
  Transceiver in loopback mode!
 Basic mode status register 0x4001 ... 782d.
   Link status: previously broken, but now reestablished.
   This transceiver is capable of  100baseTx-FD.
   Unable to perform Auto-negotiation, negotiation not complete.
 Your link partner advertised 4001:.

at least mii-diag is reporting a problem.

Hope this helps!

Thanks
Reiner


> -----Ursprüngliche Nachricht-----
> Von: Andrew Morton [mailto:andrewm@uow.edu.au]
> Gesendet: Donnerstag, 17. Mai 2001 15:15
> An: Suikat, Reiner
> Cc: 'vortex@scyld.com'
> Betreff: Re: [vortex] Slow connection in local domain
> 
> 
> "Suikat, Reiner" wrote:
> > 
> > Hello,
> > 
> > I'm experiencing a strange problem with Linux on my laptop. 
> Any connection
> > within the local domain is extremely slow (< 5kB/sec), 
> anything going
> > outside is normal (up to 200kB/sec).
> > 
> > ...
> > May 17 09:27:13 beetlejuice kernel: eth0: using NWAY device 
> table, not 8
> 
> hmm..  I hope I haven't goofed that transceiver selection. Here
> it's saying "your EEPROM says you have autoselect enabled, 
> but you have
> NWAY. I'm using NWAY".  It *should* work OK.
> 
> Could you please run the diagnostics mentioned in the
> final section of Documentation/networking/vortex.txt?
> There's a copy at http://www.uow.edu.au/~andrewm/linux/vortex.txt
> 
> Mainly, 'vortex-diag -aaee' and 'mii-diag -v' and the output
> with `debug=7'.
> 
> Thanks.
> 
> _______________________________________________
> vortex mailing list
> vortex@scyld.com
> http://www.scyld.com/mailman/listinfo/vortex
>