[eepro100] EEpro100, Red Hat 7.1, wait_for_cmd_done timeout errors
Thu Jan 9 17:39:02 2003
Not sure what to do.. the perplexing problem is I have another server
running RH 6.2 and the same NIC and the SAME 1999 driver by Don, and this
has WAY more IP addresses on it the the one I am having problems with and no
problems (server been installed and active for 3 or 4 years) This newer
server is only since Jun/Jul 2002 and only has about 30 IPs bound to it.
I have to find a fix, thank gawd someone was still at the office.. I had
them reboot it, and I did not have to spend 30 mins driving in (one way)
just for a quick reboot.
----- Original Message -----
From: "John Madden" <email@example.com>
Cc: <firstname.lastname@example.org>; <email@example.com>
Sent: Thursday, January 09, 2003 2:39 PM
Subject: Re: [eepro100] EEpro100, Red Hat 7.1, wait_for_cmd_done timeout
> > pci-scan.c:v1.11 8/31/2002 Donald Becker <firstname.lastname@example.org>
> > http://www.scyld.com/linux/drivers.html
> > eepro100.c:v1.26 11/17/2002 Donald Becker <email@example.com>
> > http://www.scyld.com/network/eepro100.html
> > Jan 8 20:12:50 corusent kernel: eth0: Restarting the chip...
> > Jan 8 20:12:50 corusent kernel: Command 0070 was not accepted after
> > 20001 polls! Current status 01700000.
> > Jan 8 20:12:55 corusent kernel: eth1: Transmit timed out: status 0000
> > 0010 at 79848671/79848749 commands 0001a000 0001a000 0001a000.
> Ouch -- so do we go with the Intel driver? Are they any more likely to
> have these things figured out? (No offense to the mighty Becker intended.
> John Madden
> UNIX Systems Engineer
> Ivy Tech State College
> eepro100 mailing list