[tulip-bug] troublesome linksys NIC

[Donald Becker]

On Tue, 18 Dec 2001, Keith Warno wrote:

> > Did you see a messge that reported
> >     printk(KERN_WARNING "%s: Tx hung, %d vs. %d.\n",
> 
> Yes I have seen this message before, as recent as today, but not with 
> this current driver version (not yet anyway), only with the previous 
> driver version which was "tulip.c:v0.92 4/17/2000".

Hmmm, OK, that means that the timeout was triggered by a new transmit
attempt, not in the timer-based monitoring code.

> So we're missing a Tx done interrupt eh?  Perhaps is not seated 
> properly?

No, this is entirely a software issue, not a hardware problem.

Likely the Tx interrupt mitigation, or some part of the transmit flow
control, has a "hole" somewhere that allows scavenging a full Tx queue
without marking it as empty.  I don't see this in the code...


Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993