RE: WATCHDOG timeout

> 
> What driver version?
> What is the detection message?

eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html

eepro100.c: $Revision: 1.5.2.1 $ 2000/11/17 Modified by Andrey V. Savochkin
<[email protected]> and others

<4>eth0: Invalid EEPROM checksum 0x552b, check settings before activating
this device!

<6>eth0: Intel Corp. 82559ER (#2), 00:90:D7:00:10:20, IRQ 15.

<6>  Board assembly 729757-005, Physical connectors present: RJ45

<6>  Primary interface chip i82555 PHY #1.

<6>  General self-test: passed.

<6>  Serial sub-system self-test: passed.

<6>  Internal registers self-test: passed.

<6>  ROM checksum self-test: passed (0xdbd8681d).


> What does
>    eepro100-diag --force -a -ee
> report while the problem is happening?
> 
I compiled eepro100-diag.c for xscale and ran it, it failed at while trying
to do 
if (iopl(3)<0) {
	perror("Nework adapter diagnosgtic: iopl()");
	fprintf(stderr, "This program must be run as root.\n");
	return 2;
}

ignored this part by #if 0, then I was able to run, but gave segment core. I
was not running it while this problem was going on but it failed anyway.

[email protected]:~# eepro100-diag --force -a -ee
eepro100-diag.c:v2.08 4/17/2002 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Index #1: Found a Intel 82559ER EtherExpressPro/100+ adapter at 0x1ffff80.
i82557 chip registers at 0x1ffff80:
Segmentation fault



> -- 
> Donald Becker				[email protected]
> Scyld Computing Corporation		http://www.scyld.com
> 410 Severn Ave. Suite 210		Second Generation 
> Beowulf Clusters
> Annapolis MD 21403			410-990-9993
>