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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
