eepro100 Transmit timeouts - time to cut my losses? & misc
Erik Barker
erik@vip.net
Thu Sep 16 13:14:39 1999
I've since changed line 46 on the eepro100.c ver.1.09l to :
static int multicast_filter_limit = 3;
I recompiled (not as module) and have not experienced any loss of
communication or other issues discussed on this list (at least not yet [1
day] :).
Intel PRO/100+ (i82559)
eth0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3986321 errors:0 dropped:0 overruns:0 frame:0
TX packets:3688884 errors:3 dropped:0 overruns:331 carrier:3
collisions:3 txqueuelen:100
Interrupt:10 Base address:0x2000
(10MB/s)
eth1 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3669607 errors:0 dropped:0 overruns:0 frame:0
TX packets:3775288 errors:2 dropped:0 overruns:273 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x4000
(100MB/s)
Albeit it's not as clean as my 3Com Cards yet:
3Com 905B
eth0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6790431 errors:0 dropped:0 overruns:0 frame:0
TX packets:3462880 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x6800
(100MB/s)
I think I'll be trying the new v1.09p driver very shortly to see what the
results are like.
Erik