RE: VirtualPC tulip bug, more info

On Fri, 30 Jan 2004, Schneider, Andrew wrote:

> Currently I've got the max_interrupt_work set to 50, RX_RING_SIZE to 128 and
> for now I've put the timeout back to 6*HZ.
> 
> With these settings I'm getting the following messages:
> 
> eth0: Too much work during an interrupt, csr5=0xfc670040.

Normal Rx interrupt, no Tx or other interrupts.  This means that the
driver did a whole bunch of work, but packets kept coming in.

> eth0: Too much work during an interrupt, csr5=0xfc6880c0.

This indicates that Rx ring filled, requiring a hardware restart.


> eth0: Restarted Rx at 57291 / 57291.

Which seemed to occur correctly.

> Let me know if changing the debug level to get more messages would help.

It might, although if this happens infrequently you'll get a lot of
messages between useful bits.

> I figured that the issue was due to a lack of fidelity in the emulation but
> since Microsoft won't share their source code I felt my best bet was to
> alter the network driver in Linux to work around this problem.

..And Microsoft has no motivation to make it work in any mode except
exactly how their driver uses the chip.

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster systems
Annapolis MD 21403			410-990-9993

_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip