[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: eth0: card reports no RX buffers. (eepro100)



Interesting...

One of these days, maybe I'll be able to figure out what actually causes
it and be able to put in a proper bug report.  I hate turning in bug
reports unless I know generally where the problem is.

Sounds like quite a few people have seen it.

On Sun, Sep 03, 2000 at 08:22:39PM -0700, Alvin Oga wrote:
> 
> hi ya nate...
> 
> i've seen that silly "card reports noRX buffer" errors...
> 
> i usually just rerun lilo and it seems to clear it up
> on my D815EEAAL mb w/ onboard nic..
> and if i have other pci-based nics...i still go those RX buffer
> problems...so its just "timing" ?? somewhere on the mb or bios
> or network driver...but since tulip drivers and eepro is different...
> think its the mb itself or disk latency ????
> 
> c ya
> alvin
> 
> On Sun, 3 Sep 2000, Nate Duehr wrote:
> 
> > Hi Nate!  :)
> > 
> > If it's any help for anyone smarter than I, I've seen this same problem
> > on a Dell GX100 with on-board EEPRO100 card and the Intel810i chipset
> > (which I know requires much joy and the agpart module loaded to get X
> > working) at the office...
> > 
> > A complete hardware restart usually clears it?
> > 
> > On Wed, Aug 30, 2000 at 01:28:41PM -0700, Nate Amsden wrote:
> > > This started happening recently. Sometimes when i boot up my screen
> > > floods with :
> > > 
> > > eth0: card reports no RX buffers.
> > > eth0: card reports no resources.
> > > eth0: card reports no RX buffers.
> > > 
> > > over and over again.. at first i thought it was an IRQ conflict but
> > > nothing in the system had changed it just started out of nowhere
> > > apparently(after a reboot once) i figured a way around it, to
> > > /etc/init.d/networking stop then start it again after a few
> > > seconds(haven't tried to issue just a restart) and the errors stop. was
> > > wondering if this could be the result of the system booting too fast ?
> > > my system takes about 6 seconds from when init loads to when X
> > > launches(probably more like 4-5 seconds) the same hardware when i was
> > > running slower stuff(128MB as opposed to 512MB and 466mhz as opposed to
> > > 800mhz) this never happened. Running on an Asus CUV4X(VIA Apollo
> > > Pro133A). I did move the NIC from PCI#4 to PCI#2 with no difference.
> > > 
> > > really odd.
> > > 
> > > Running debian 2.2r0 linux 2.2.17pre18
> > > 
> > > 
> > > 
> > > eth0: Intel PCI EtherExpress Pro100 82557, 00:90:27:9B:16:D6, I/O at
> > > 0xa800, IRQ 10.
> > >   Receiver lock-up bug exists -- enabling work-around.
> > >   Board assembly 721383-006, 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).
> > > 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 <saw@saw.sw.com.sg> and others
> > > 
> > > 
> > > more info:
> > > 
> > > aphro@aphro:~$ cat /proc/interrupts 
> > >            CPU0       
> > >   0:      47060          XT-PIC  timer
> > >   1:       2469          XT-PIC  keyboard
> > >   2:          0          XT-PIC  cascade
> > >   8:          1          XT-PIC  rtc
> > >  10:        797          XT-PIC  eth0
> > >  11:          0          XT-PIC  es1370
> > >  12:      17762          XT-PIC  PS/2 Mouse
> > >  13:          1          XT-PIC  fpu
> > >  14:          0          XT-PIC  usb-uhci, usb-uhci
> > >  15:      26279          XT-PIC  aic7xxx
> > > aphro@aphro:~$ cat /proc/ioports 
> > > 0000-001f : dma1
> > > 0020-003f : pic1
> > > 0040-005f : timer
> > > 0060-006f : keyboard
> > > 0070-007f : rtc
> > > 0080-008f : dma page reg
> > > 00a0-00bf : pic2
> > > 00c0-00df : dma2
> > > 00f0-00ff : fpu
> > > 02e8-02ef : serial(set)
> > > 02f8-02ff : serial(set)
> > > 0378-037f : parport0
> > > 03c0-03df : vga+
> > > 03f8-03ff : serial(set)
> > > 0778-077a : parport0
> > > a000-a03f : es1370
> > > a400-a4fe : aic7xxx
> > > a800-a81f : Intel Speedo3 Ethernet
> > > b000-b013 : usb-uhci
> > > b400-b413 : usb-uhci
> > > e800-e807 : via2-smbus
> > > 
> > > 
> > > 
> > > any idea ?  thanks for any input!
> > > 
> > > nate
> > > 
> > > -- 
> > > :::
> > > ICQ: 75132336
> > > http://www.aphroland.org/
> > > http://www.linuxpowered.net/
> > > aphro@aphroland.org
> > > 
> > > 
> > > -- 
> > > Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> > > 
> > 
> > -- 
> > Nate Duehr <nate@natetech.com>
> > 
> > GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
> > Public Key available upon request, or at wwwkeys.pgp.net and others.
> > 
> 

-- 
Nate Duehr <nate@natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.

Attachment: pgpbVMAvKBwHV.pgp
Description: PGP signature


Reply to: