tulip driver: errors instead TX packets?

Piotr Kaczuba
2004-01-10T14:48:36Z

I've got a ADMtek Centaur (3cSOHO100B-TX) running with the tulip driver
on 2.6.1. I wonder if anyone has noticed that ifconfig shows the
packets sent in the errors field instead of the TX packets field. At
least, this is what I assume because it shows 0 TX packets and 11756
errors.

Here's the ifconfig output for eth0, which is used for PPPoE:

eth0 Link encap:Ethernet HWaddr 00:04:75:B1:E0:77
inet6 addr: fe80::204:75ff:feb1:e077/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9130 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:11756 dropped:0 overruns:0 carrier:23473
collisions:0 txqueuelen:1000
RX bytes:1723335 (1.6 MiB) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0x5000

I had the same behaviour with 2.4 and the tulip driver from scyld.

This is what tulip-diag reports:

tulip-diag.c:v2.18 11/12/2003 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3Com 3cSOHO100B-TX (ADMtek Centaur) adapter at
0xd000.
Comet duplex is reported in the MII status registers.
Transmit started, Receive started.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
Comet MAC address registers b1750400 ffff77e0
Comet multicast filter 8000000040001000.
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.

Is it okay for the TX process to be in idle state although there
definitly is outgoing traffic?

Please CC any replies to me as I'am not subscribed.