[tulip-bug] Tulip vs LNE100TX v4 and Kernel 2.4.4 vs 2.4.6

[Hal Brand]

I just joined this group so I don't know if this has been discussed.
Just in case it hasn't, here goes.

I have a LinkSys LNE100TX v4 PCI network adapter that installed and
worked fine with Win98 and kernel 2.4.4 (tulip driver compiled into
kernel). With kernel 2.4.6 (didn't try 2.4.5), I get mixed results:
  * After power-on the tulip driver works fine and continues to work
	thru as many reboots of Linux (2.4.6 or 2.4.4) as I tried.
  * However, after Win98 has booted, the 2.4.6 driver fails.
	Booting 2.4.4 works fine. The problem with 2.4.6 can only
	be cleared by a power-down - the reset button is not sufficient!
  * Linux 2.4.6 boot-time diagnostics show a difference:
	2.4.6 booting and working:
		Floppy drive(s): fd0 is 1.44M
		FDC 0 is a post-1991 82077
		Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
		PCI: Found IRQ 11 for device 00:0c.0
		eth0: ADMtek Comet rev 17 at 0xb400, 00:04:5A:41:9C:CB, IRQ 11.
		Linux agpgart interface v0.99 (c) Jeff Hartmann
	2.4.6 booting after Win98 and failing at the first transmit attempt:
		Floppy drive(s): fd0 is 1.44M
		FDC 0 is a post-1991 82077
		Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
		PCI: Found IRQ 11 for device 00:0c.0
		eth0: ADMtek Comet rev 17 at 0xb400, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11.
		Linux agpgart interface v0.99 (c) Jeff Hartmann
	    The diagnostic message from the 2.4.6 kernel is:
		NETDEV WATCHDOG: eth0: transmit timed out, status ffffffff, csr12 ffffffff reseting...

(I can do other tests if it will help.)

Has then problem been reported? Has it been addressed?
Thanks.
-- 
//*****************
// Hal Brand
// hbrand@home.com
//*****************