[eepro100] RE: WATCHDOG timeout
Donald Becker
becker@scyld.com
Mon Jun 24 15:50:01 2002
On Mon, 24 Jun 2002, Afzal, Naeem M wrote:
> From: "Afzal, Naeem M" <naeem.m.afzal@intel.com>
I note that are from Intel -- you have access to current information,
while I have to figure out the chip operation from its behavior.
> > 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
Try a current version, which works around the bugs (at least the ones we
know about) in the newer chips.
> <4>eth0: Invalid EEPROM checksum 0x552b, check settings before activating
> this device!
This is curious. Has something changed the EEPROM configuration?
> <6>eth0: Intel Corp. 82559ER (#2), 00:90:D7:00:10:20, IRQ 15.
> > 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
Ahhh, I didn't know this was for the Xscale architecture.
> if (iopl(3)<0) {
> perror("Nework adapter diagnosgtic: iopl()");
> fprintf(stderr, "This program must be run as root.\n");
> return 2;
OK, that means your libc doesn't have the functions needed to run
diagnostics.
Someone should fix that.
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993