Anand,
Have you tried www.scyld.com? The "nasa" address is quite old.
"Complete" documentation can be obtained from the scyld site. I, too, have
been having trouble with the Intel eepro 100 (but for very different
reasons).
G. Cox
>From: Anand Buddhdev <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: intel eepro100 receiver bug
>Date: Mon, 23 Oct 2000 17:11:30 +0200
>
>I have a Redhat linux box, kernel 2.2.16. When it boots up, I see the
>following bootup message:
>
>eepro100.c:v1.09j-t 9/29/99 Donald Becker
>http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by Andrey V.
>Savochkin <[EMAIL PROTECTED]> and others
>eth0: Intel PCI EtherExpress Pro100 82557, 00:D0:B7:21:86:0E, IRQ 10.
> Receiver lock-up bug exists -- enabling work-around.
> Board assembly 721383-008, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x04f4518b).
>
>So I realise that there's a bug in the ethernet card, but that the driver
>has a work-around for it. However, in the past 2 months, there have been 3
>occasions when the machine has stopped responding to the network. Even
>after waiting a few minutes for the 'work-around' to reset the card,
>nothing happened. After a CTRL-ALT-DEL warm boot, I got the following in
>the syslog:
>
>Oct 19 08:01:21 picasso kernel: eth0: card reports no RX buffers.
>Oct 19 08:01:22 picasso kernel: eth0: card reports no resources.
>
>This message is repeated many times. Finally, only a cold boot (shutdown,
>switch off and switch on) has helped.
>
>I looked at the source code of the driver:
>
>/usr/src/linux/drivers/net/eepro100.c
>
>and there's a web site mentioned there for more info about this driver, but
>I can't reach the web site. There's also a mailing list, but mail sent to
>the list doesn't get transferred to the mailhost and bounces after a
>timeout.
>
>Does anyone have any more info on this particular card and bug? Is there an
>updated driver somewhere that can deal with it, or will I have to replace
>the card? The box is in a remote location, so I want to avoid changing the
>card if possible.
>
>--
>Anand
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
