LinkSys LNE100TX overruns - More info

Charles Calkins
Mon Apr 10 13:16:55 2000


	Some more info regarding my overrun problem with an LNE100TX
when used in a Linux firewall:

  It was suggested that a high overrun count indicates tulip.c wasn't compiled
for SMP correctly - the gcc command line appears to be correct however:

gcc -D__KERNEL__ -I/ex/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586   -c -o tulip.o tulip.c

  and SMP_CHECK is defined in tulip.c

  In case SMP is an issue, I compiled a uniprocessor kernel.  The data 
rate when FTPing from NT (ako->firewall) actually has increased somewhat,
although I still see approximately 10% of the packet count as overruns:

eth0      Link encap:Ethernet  HWaddr 00:A0:CC:36:BD:13
          inet addr:  Bcast:  Mask:
          RX packets:23257 errors:1845 dropped:0 overruns:1845 frame:0
          TX packets:17174 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:9 Base address:0xe800

  As before (when in SMP), the overruns are only on the receiving side.  Any 
suggestions would be greatly appreciated.  Thanks.

ako: Dual PII-450, running NT4 SP6 or Linux 2.2.14 (SMP), Intel EtherExpress
10/100 on the motherboard
firewall: Dual P5-90 running Linux 2.2.14 with firewall options set, 
LinkSys LNE100TX 10/100 LAN Card
Machines are connected to each other via a category 5 crossover cable.

Charles Calkins
Vice President
Applied Intelligence, Inc.	St. Louis, MO

To unsubscribe send a message body containing "unsubscribe"