Re: Via-Rhine ethernet driver problem?

[walt]

Roger Luethi wrote:
> On Mon, 29 Mar 2004 09:24:25 -0800, walt wrote:
>
> > ECS K7VTA3 motherboard with built-in ethernet chip:
> >
> > 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 
> > 74)
> > [...]
> > I also discovered by using 'scp' to copy files between machines that the bad
> > performance is assymetrical:  copying a file *to* this machine runs at about
> > half-speed (5 MB/sec) whereas copying a file *from* this machine runs at
> > 45 KiloB/sec, about one percent of expected.


> If you have ACPI and/or IO-APIC enabled, does the behavior change if
> you turn them off?

I did have both -- no difference when I turned them both off.

> Any info in the kernel log? If not, what if you
> change the driver's debug level to 3? 

This is debug=4 since debug=3 didn't put out much:
Mar 30 04:27:58 k9 kernel: via-rhine.c:v1.10-LK1.1.19-2.5  July-12-2003  Written by Donald Becker
Mar 30 04:27:58 k9 kernel:   http://www.scyld.com/network/via-rhine.html
Mar 30 04:27:58 k9 kernel: via-rhine: Reset succeeded.
Mar 30 04:27:58 k9 kernel: eth0: VIA VT6102 Rhine-II at 0xe9041000, 00:0d:87:a2:ce:02, IRQ 11.
Mar 30 04:27:58 k9 kernel: eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
Mar 30 04:27:58 k9 kernel: eth0: MII PHY found at address 2, status 0x8000 advertising 0000 Link 8000.
Mar 30 04:27:58 k9 kernel: eth0: MII PHY found at address 3, status 0x8000 advertising 0000 Link 8000.
Mar 30 04:27:58 k9 kernel: eth0: MII PHY found at address 4, status 0x8000 advertising 0000 Link 8000.
Mar 30 04:28:37 k9 kernel: eth0: via_rhine_open() irq 11.
Mar 30 04:28:37 k9 kernel: eth0: Reset succeeded.
Mar 30 04:28:37 k9 kernel: eth0: Done via_rhine_open(), status 081a MII status: 786d.
Mar 30 04:28:37 k9 kernel: eth0: VIA Rhine monitor tick, status 0000.
Mar 30 04:29:17 k9 last message repeated 4 times
Mar 30 04:29:37 k9 last message repeated 2 times
Mar 30 04:29:44 k9 kernel: eth0: exiting interrupt, status=00000000.
Mar 30 04:29:44 k9 last message repeated 25 times
Mar 30 04:29:47 k9 kernel: eth0: VIA Rhine monitor tick, status 0000.
Mar 30 04:29:49 k9 kernel: eth0: exiting interrupt, status=00000000.
Mar 30 04:29:57 k9 last message repeated 543 times
[much more snipped]


> Is the slow transfer rate
> the result of short, fast bursts or actual sustained throughput at
> 45 KB/sec?

Just from watching the lights on the ethernet hub I would say that it
is bursting.  Is there a more accurate way to tell?

Thanks for the quick response!

BTW, this is from ethtool:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full
                        100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
                        100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Current message level: 0x00000004 (4)
Link detected: yes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/