FWIW, I have a dual-proc SuperMicro motherboard P3DM3 with integrated
Adaptec SCSI and Intel 8255x built-in NIC.
Sometimes on a cold boot I get the "kernel: eth0: card reports no RX
buffers" that repeats, but if I follow it with a warm boot the message
doesn't appear (even on subsequent warm boots). So this is definitely
reproducible, but it doesn't happen every time.
I can't offer much more than that, but at least you know you're not the only
one experiencing this.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 10, 2000 9:00 AM
To: [EMAIL PROTECTED]
Subject: intel etherpro100 on 2.2.18p21 vs 2.2.18p17
We have several Supermicro 370DL3 boards (scsi, built into epro100, dual
pentium iii) - which are giving the following ethernet card error on
2.2.18p21, but not on 2.2.18p17. This error has happened on 3 out of 4
boards with this configuration.
Oct 18 12:17:34 db1 kernel: eth0: card reports no RX buffers.
The above message repeats itself and the ethernet card does not work.
On bootup:
<SNIP>
Oct 18 12:17:34 db1 kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro10$
Oct 18 12:17:34 db1 kernel: eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31
Modified by Andrey V. Savochkin <[EMAIL PROTECTED]$
Oct 18 12:17:34 db1 kernel: eth0: Intel PCI EtherExpress Pro100 82557,
00:30:48:21:2F:9E, I/O at 0xd400, IRQ 31.
Oct 18 12:17:34 db1 kernel: Board assembly 000000-000, Physical
connectors present: RJ45
Oct 18 12:17:34 db1 kernel: Primary interface chip i82555 PHY #1.
Oct 18 12:17:34 db1 kernel: General self-test: passed.
Oct 18 12:17:34 db1 kernel: Serial sub-system self-test: passed.
Oct 18 12:17:34 db1 kernel: Internal registers self-test: passed.
Oct 18 12:17:34 db1 kernel: ROM checksum self-test: passed (0x04f4518b).
Oct 18 12:17:34 db1 kernel: Receiver lock-up workaround activated.
<SNIP>
Oct 18 12:17:34 db1 kernel: eth0: card reports no RX buffers.
I believe this has been an ongoing issue for these intel nics?
--Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
