Bug report, as much information as I can give...

[Winged Wolf]

Also interesting: The MII is detecting when I disconnect the cable (I've
just accidentally found out what 7869 and 786d are status flags for :>),
as evidenced by mii-diag -wv eth0.

However, the link light on the hub still isn't showing up.  Would this be
a situation generated by a crossover ethernet cable, instead of a
straight-through cable?

-Mat


On Mon, 27 Dec 1999, Donald Becker wrote:

> On Mon, 27 Dec 1999, Winged Wolf wrote:
> 
> > With the L version of the driver, I get the same output from mii-diag, but
> > when I try to do the ping, I get:
> > 
> > eth0: Host error, FIFO diagnostic register 0000.
> 
> Hmmmm, that indicates a problem, usually a hardware problem.
> 
> > I get losts of these, then:
> > 
> > eth0: Too much work in interrupt, status 8003.  Temporarily disabling
> > functions (7ffc).
> 
> This is bad.  It's reporting that the machine is too slow to process the
> packets.  Do you have some sort of APM feature turned on?
> 
> > Then:
> > eth0: transmit timed out, tx_status 00 status e000.
> 
> This is because the card has most features disabled at this point.
> 
> You can work around the symptoms by setting the following module parameter:
> /* Maximum events (Rx packets, etc.) to handle at each interrupt. */
> static int max_interrupt_work = 20;
> 
> options 3c59x max_interrupt_work=200
> 
> Donald Becker
> Scyld Computing Corporation, and
> USRA-CESDIS,   becker@cesdis.gsfc.nasa.gov
>