Problem with EPIC/100 latching up on RX

[Terry Barnaby]

Thanks for the reply.
I have tried 1.06 to no avail.
Some additional information:

We have a simple test program that demonstrates the problem.
The test application ping-pongs a 2568 byte lump of data between two
processes running on two nodes. The TCP/IP socket has been set to TCP_NODELAY.
When not locked up the test program reports a bi-directional data rate of
5.708708 MBytes per second.

Setting the EPIC100.c drivers debug level to 4 does not provide and messages.
There are no errors reported in /proc/net/dev

The /proc/tcp file has the following entry when locked up
  sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   
uid  timeout inode
   0: 0200A8C0:13D8 0100A8C0:041B 01 00000454:00000000 01:0000037C 00000006  
1002        0 1663
   1: 0200A8C0:13D8 00000000:0000 0A 00000000:00000000 00:FFFF405E 00000000  
1002        0 1660

When Running normally it has the following
  sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   
uid  timeout inode
   0: 0200A8C0:13D8 0100A8C0:041B 01 00000A08:00000000 01:00000014 00000000  
1002        0 1663
   1: 0200A8C0:13D8 00000000:0000 0A 00000000:00000000 00:FFFEFC69 00000000  
1002        0 1660

Terry

> The driver you use is not the latest. The actual version is 1.06. It may
> fix your problem.
> Have a look at http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html.
> 
> Cheers.
> 
> Emmanuel Croze
> 
> At 15:25 25/02/99 +0000, you wrote:
> >We have a problem with networking under Linux. We believe it is
> >associated with
> >the EPIC/100 Ethernet card driver, but it could be the Linux netwoking
> >system.
> >The problem is that the ethernet interface seems to lock up occassionly.
> >It
> >appears that the system will accept no more packets until a packet is
> >transmitted.
> >
> >It appears to be timing or packet size related. Using a tcp/ip test
> >program
> >the systems lock up when a transmitted buffer size of around 2568 bytes
> >is
> >sent via a write() call. With this saturated test the system will lock
> >up
> >about once per second.
> >
> >The systems are:
> >
> > Motherboard: Supermicro P6DBU
> > Processors: Pentium II 450Mhz
> > Ethernet: SMC Etherpower II
> > Linux:  RedHat 5.2
> > Kernel:  2.0.36
> > Driver:  EPIC/100 v1.03
> > Hub:  Allied telesyn MR904TX
> >
> >We have noticed this problem for around 6 months now with other
> >motherboards,
> >processors, hubs and switches, kernel versions and EPIC driver versions,
> >but have finaly got
> >around to trying to track down the problem.
> >
> >Does anyone have any ideas ?
> >
> >Cheers
> >
> >
> >Terry
> >
> >--
> >  Dr Terry Barnaby                     BEAM Ltd
> >  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
> >  Fax:   +44 1454 313172               Yate, Bristol, BS17 5NH, UK
> >  Email: terry@beam.demon.co.uk        Web: www.beam.demon.co.uk
> >  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
> >                         "Tandems are twice the fun !"
> >
> >
> >
> > | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within
> the
> > |  body of the mail, include only the text:
> > |   unsubscribe this-list-name youraddress@wherever.org
> > | You will be unsubscribed as speedily as possible.
> > 

-- 
  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS17 5NH, UK
  Email: terry@beam.demon.co.uk        Web: www.beam.demon.co.uk
  BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
                         "Tandems are twice the fun !"


 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
 |  body of the mail, include only the text:
 |   unsubscribe this-list-name youraddress@wherever.org
 | You will be unsubscribed as speedily as possible.