[eepro100] eepro strange lock-up

[Alisdair McDiarmid]

On Mon, Jan 29, 2001 at 06:59:01PM -0500, Donald Becker wrote:
> On Mon, 29 Jan 2001, Alisdair McDiarmid wrote:
> > On Mon, Jan 29, 2001 at 09:14:05PM +0000, Alisdair McDiarmid wrote:
> > > On Mon, Jan 29, 2001 at 11:22:57AM -0500, Donald Becker wrote:
> > > 
> > > > Have you tried the updated driver?
> > > >    http://www.scyld.com/network/eepro100.html
> > > 
> > > Not yet, I'm downloading and compiling right now.
> > 
> > And I can't get it to compile. I downloaded (with wget) the driver
> > from ftp://ftp.scyld.com/pub/network/eepro100.c and compiled with
> > the given command line:
> > 
> > [piped ~] $ gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c eepro100.c
> > eepro100.c: In function `speedo_open':                              
> > eepro100.c:853: structure has no member named `tbusy'
> 
> This is the Red Hat 7.0 bug.  See
>     http://www.scyld.com/network/updates.html#redhat7.0

I think it can now also be called the `Debian sid' bug :-)

Anyway, having compiled the module and installed it, I still have
the same problem. Turning debug to level 6 gives me lots of data,
but I don't know what any of it means; the following is the log
when the receive stalls:

eth1: Interface monitor tick, chip status 0050.
eth1: Interface monitor tick, chip status 0050.
eth1: Interface monitor tick, chip status 0050.
eth1: Interface monitor tick, chip status 0050.
eth1: Interface monitor tick, chip status 0050.
eth1: Interface monitor tick, chip status 0050.
eth1: Interface monitor tick, chip status 0050.
eth1: interrupt  status=0x2050.
 scavenge candidate 17 status 400ca000.
eth1: interrupt  status=0x0050.
eth1: exiting interrupt, status=0x0050.
eth1: interrupt  status=0x2050.
 scavenge candidate 18 status 400ca000.
eth1: interrupt  status=0x0050.
eth1: exiting interrupt, status=0x0050.
eth1: interrupt  status=0x2050.
 scavenge candidate 19 status 400ca000.
eth1: interrupt  status=0x0050.
eth1: exiting interrupt, status=0x0050.
eth1: interrupt  status=0x2050.
 scavenge candidate 20 status 400ca000.
eth1: interrupt  status=0x0050.
eth1: exiting interrupt, status=0x0050.
eth1: interrupt  status=0x2050.
 scavenge candidate 21 status 400ca000.
eth1: interrupt  status=0x0050.
eth1: exiting interrupt, status=0x0050.
eth1: interrupt  status=0x2050.
 scavenge candidate 22 status 400ca000.
eth1: interrupt  status=0x0050.
eth1: exiting interrupt, status=0x0050.
eth1: Interface monitor tick, chip status 0050.

Does anyone have any other suggestions?

Thanks for your help,
-- 
Alisdair McDiarmid                    <http://wasters.org/pubkey.asc>