tulip driver & Asante Fast 10/100 card

Bob Farmer ucs_brf@unx1.shsu.edu
Tue Oct 26 07:02:12 1999


> On Sun, 24 Oct 1999, Bob Farmer wrote:
> 
> > The net cards we've been buying, Asante Fast 10/100, recently switched
> > from 21140A chips to the PNIC chips.  On startup, the driver reports the
> > chip as a "Lite-On 82c168 PNIC rev 32".  It works for a bit, but as soon
> 
> What's the whole detection message?
> Is the an MII transceiver, or does it use the internal encoder and an
> external twister (SYM PHY)? 

The whole detection message is this (with 0.89H):

tulip.c:v0.89H 5/23/98 becker@cesdis.gsfc.nasa.gov
eth0: Lite-On 82c168 PNIC at 0xe400, 00 00 b4 94 e0 99, IRQ 10.
eth0:  MII transceiver found at MDIO address 1, config 3100 status 7829.
eth0:  Advertising 01e1 on PHY 1, previously advertising 01e1.
eth0: Changing PNIC configuration to full-duplex, CSR6 812e0200.

> > as you try to transfer more than about 50K of data through the card, it
> > locks, and the interface has to be taken down and brought back up again to
> > restore connectivity.
> 
> What kind of motherboard?  Old 486 systems are known to have bugs that
> can be worked around with a csr0=0x01a04800 setting.

I am using Intel BX chipset Pentium II motherboards.  

After some more testing, I've found more details on the problem...

All of this is with the 0.89H driver:

If you are using half-duplex on either end (ie these combinations:
half-duplex on both ends, half-duplex on machine and full-duplex on
switch, or full-duplex on machine and half-duplex on switch), it never
locks up.  If, however, you are using full-duplex on both ends, it always
locks up once you try to receive a large file with FTP.  If, again while
both ends are at full-duplex, I try to _send_ a large file with FTP, I get
this (also easily reproduceable):

Kernel panic: skput:over: c4856b30:5296 put:5296 dev:eth0
In swapper task - not syncing

Followed by a system hang, etc...

If, while doing the receive-file test, I turn on "debug=3" on the module,
I get this output when the interface hangs:

eth0: Oversized Ethernet frame spanned multiple buffers, status 7fff0200!
eth0: Oversized Ethernet frame spanned multiple buffers, status 08018192!

When using half-duplex those warnings above never appear.

Now, retrying all of the above things with 0.91g, everything's the same
except one thing: no crash or interface hang when I send a large file with
FTP.  Just a ton of the "Oversized Ethernet frame spanned multiple
buffers" warnings (debug=3).  Still the same interface hang when receiving
a large file with FTP, though, at full-duplex.

-- 
Bob Farmer                                     ucs_brf@shsu.edu
Computer Services, Sam Houston State University; Huntsville, TX