From: Kostas Nikoloudakis <kostas@corp124.com>
To: linux-kernel@vger.kernel.org
Subject: eepro100 error messages
Date: Tue, 16 Jan 2001 19:02:52 -0800 [thread overview]
Message-ID: <3A650B5B.EE1CCB07@corp124.com> (raw)
Message from syslogd@zeus at Tue Jan 16 00:17:29 2001 ...
zeus kernel: 0000000000000000000000000000000000 to4 0 0 0 00100001001.
Message from syslogd@zeus at Tue Jan 16 00:26:38 2001 ...
zeus kernel: 0:0: 0:0:0: 0: 0:0: 0:0: 0:0: 0:0:0: 0:0:0: 0:0: 0:0: 0
ind.
Message from syslogd@zeus at Tue Jan 16 00:49:15 2001 ...
zeus kernel: 00001.000000000.000000.000001 ether 1HY i0 >tePHY index 1
register 5 is 41e1.
Hello,
Does anybody know what the exact cause for the following messages is:
Jan 16 00:49:04 cd20 kernel: eth0: card reports no resources.
Jan 16 00:49:06 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:06 cd20 kernel: eth0: restart the receiver after a possible
hang.
Jan 16 00:49:06 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:06 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:06 cd20 kernel: eth0: card reports no resources.
Jan 16 00:49:08 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:08 cd20 kernel: eth0: restart the receiver after a possible
hang.
Jan 16 00:49:09 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:09 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:09 cd20 kernel: eth0: card reports no resources.
Jan 16 00:49:09 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:09 cd20 kernel: eth0: restart the receiver after a possible
hang.
Jan 16 00:49:09 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:09 cd20 kernel: eth0: card reports no resources.
Jan 16 00:49:12 cd20 kernel: 000ca000.
Jan 16 00:49:12 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:12 cd20 last message repeated 6 times
Jan 16 00:49:12 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:12 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:13 cd20 last message repeated 15 times
Jan 16 00:49:13 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:13 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:13 cd20 last message repeated 7 times
Jan 16 00:49:13 cd20 kernel: eth0: card reports no resources.
Jan 16 00:49:13 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:13 cd20 last message repeated 7 times
Jan 16 00:49:13 cd20 kernel: 000ca000.
Jan 16 00:49:13 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Hello there,
Does anyone know the cause and a potential fix for the following
error messages reported in syslogd by my eepro100 card?
The machine is running under heavy CPU + memory + network load.
It seems that the card has problems finding the required resources.
Is there a way to "guarantee" that the card will have the necessary
resources even at high loads?
I'm using kernel version 2.2.14.
Thank you,
Sincerely
Kostas Nikoloudakis
Jan 16 00:49:13 cd20 kernel: eth0: card reports no resources.
Jan 16 00:49:15 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:15 cd20 kernel: eth0: restart the receiver after a possible
hang.
Jan 16 00:49:15 cd20 kernel: eth0: can't fill rx buffer (force 0)!
Jan 16 00:49:15 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:15 cd20 last message repeated 6 times
Jan 16 00:49:15 cd20 kernel: 000ca000.
Jan 16 00:49:15 cd20 kernel: eth0: can't fill rx buffer (force 1)!
Jan 16 00:49:15 cd20 last message repeated 16 times
Jan 16 00:49:15 cd20 kernel: 00000 t4
000000000000000020.0020.020002020.
Jan 16 00:49:15 cd20 kernel: 00001.000000000.000000.000001 ether 1HY i0
>tePHY index 1 register 5 is 41e1.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-17 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 3:02 Kostas Nikoloudakis [this message]
2001-01-17 8:35 ` eepro100 error messages bert hubert
2001-01-17 18:29 ` Lukasz Trabinski
2001-01-21 6:45 ` Andrey Savochkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A650B5B.EE1CCB07@corp124.com \
--to=kostas@corp124.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.