[tulip] Careful with Conexant LANfinity and 2.4

Kent Hunt kenthunt@yahoo.com
Sun, 29 Jul 2001 14:06:13 -0700 (PDT)


> > This doesn't happen with 2.2 kernels.
> This is caused by a locking change in the 2.4
> kernel.
> Try adding these two lines in tulip.c line 2668
> 	if ( ! tp->tx_full)
> 		netif_unpause_tx_queue(dev);
> +	else
> +		netif_stop_tx_queue(dev);
> Please send a report.

This was a two-liner fix. Yes, it did make the tx
sync error go away. I tested with a few times with 
a 76Mb file and I saw no complaints regarding
Out-of-sync dirty pointers. Thanks! I guess we have
a semi-tested working version for 2.4. At least no
lockups and the driver keeps holding even in stressed

> > 	Another thing that I noticed that is when I try
> to
> > remove tulip.o out of the kernel I get:
> > Trying to free nonexistent resource
> <d09dc000-d09dc07f>
> I'm still trying to work out cross-compatible
> semantics for this.  The
> 2.4 kernel doesn't seem to match up
> request_region/release_region calls.

Okay. Is this related to the fact that mii-diag
doesn't work with 2.4? SIOCGMIIPHY on eth0 failed:
Operation not supported.


Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger