[eepro100] cmd_wait issues

John Madden jmadden@ivy.tec.in.us
Mon, 11 Jun 2001 09:20:59 -0500


*This message was transferred with a trial version of CommuniGate(tm) Pro*
I'm having trouble on one machine out of about 20 that run with eepro100's. 
This one in particular happens to be a dual port.  I searched through the
archives for this, but I didn't find any definite solutions.  

I get a lot of kernel messages like the following:

kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)!
kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)!

I'd like to assume that this is bad hardware, but since the problem only
happens every 30 days or so (and every 30 days or so), I wanted to check here to
make sure it wasn't a driver issue.

The only solution I've found that works is to reboot, and since this is
probably the most production machine I'm responsible for (couldn't be any other
one, right?), I'd like to make sure I don't have to scedule a reboot every 29
days or something.

More info: 
Kernel 2.2.19 SMP, 
lspci: 
01:04.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 05)
        Subsystem: Intel Corporation EtherExpress PRO/100+ Dual Port Adapter
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at fafff000 (32-bit, prefetchable)
        I/O ports at ece0
        Memory at fcf00000 (32-bit, non-prefetchable)
        Expansion ROM at fd000000 [disabled]
        Capabilities: [dc] Power Management version 1

01:05.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 05)
        Subsystem: Intel Corporation EtherExpress PRO/100+ Dual Port Adapter
        Flags: bus master, medium devsel, latency 32, IRQ 5
        Memory at faffe000 (32-bit, prefetchable)
        I/O ports at ecc0
        Memory at fce00000 (32-bit, non-prefetchable)
        Expansion ROM at fd000000 [disabled]
        Capabilities: [dc] Power Management version 1

Thanks!

John


-- 
John Madden
UNIX Systems Engineer
Ivy Tech State College
jmadden@ivy.tec.in.us