From: Robert Lynch <rmlynch@best.com>
To: linux-kernel@vger.kernel.org
Subject: Spew from test11-pre1
Date: Wed, 08 Nov 2000 16:14:39 -0800 [thread overview]
Message-ID: <3A09EC6F.C87A7729@best.com> (raw)
No oops, but right after I installed test11-pre1, then tried to
access a Windows box as a VNC client, this message started
getting continuously dumped by syslog:
===
...
Nov 8 15:32:01 ives kernel: eth0: card reports no RX buffers.
Nov 8 15:32:04 ives kernel: eth0: card reports no resources.
Nov 8 15:32:04 ives kernel: eth0: card reports no RX buffers.
Nov 8 15:32:04 ives kernel: eth0: card reports no resources.
Nov 8 15:32:05 ives kernel: eth0: card reports no RX
buffers.
...
Nov 8 15:36:18 ives kernel: eth0: card reports no resources.
Nov 8 15:36:35 ives kernel: eth0: card reports no RX buffers.
Nov 8 15:36:49 ives kernel: SysRq: Emergency Sync
Nov 8 15:36:49 ives kernel: Syncing device 03:03 ... OK
..
===
eth0 seems OK, I regularly check ifconfig after installing a new
kernel:
===
$ /sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:D0:B7:7A:00:B0
inet addr:172.16.1.3 Bcast:172.16.1.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9
...
===
Doing a Yahoo search it seems this was previously reported
eepro100 bug, which appears to have resurfaced.
FWIW, Bob L.
-
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:[~2000-11-09 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 0:14 Robert Lynch [this message]
2000-11-09 6:53 ` Spew from test11-pre1 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=3A09EC6F.C87A7729@best.com \
--to=rmlynch@best.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.