After roughly 30 days of uptime, 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 schedule 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
dmesg:
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/driv
ers/eepro100.html
eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V. Savochkin <s
aw@saw.sw.com.sg> and others
eepro100.c: VA Linux custom, Dragan Stancevic <visitor@valinux.com> 2000/11/15
Thanks!
John
-- John Madden UNIX Systems Engineer Ivy Tech State College jmadden@ivy.tec.in.us - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/