Messages in this thread | | | Date | Tue, 29 Jan 2002 19:41:09 -0600 (CST) | From | rob2@rekl ... | Subject | Execssive network errors 2.4.18pre (tx error or tx frame is busy) |
| |
Hi. I've seen the following on both 2.4.18pre4 and 2.4.18pre7+preempt: Lots & lots of these get warnings/errors get printed to the console and syslog, and I don't know why. i586, eth0 is a natsemi at 10Mbs half duplex, eth1 is a natsemi at 100Mbs full duplex, eth2 is an Orinoco silver in adhoc mode. I didn't have this issue before I had 2.4.18pre4. I haven't noticed anything not "working", except my syslog is getting filled up.
More output, including .config and dmesg output is available at http://rekl.yi.org/lk_help/
Please cc: me on replies, since I'm not subscribed. Thanks.
eth0: tx frame #1359 is busy. eth0: tx frame #1359 is busy. eth0: tx frame #1360 is busy. eth2: Tx error, status 4 (FID=0192) eth0: tx frame #1368 is busy. eth0: tx frame #1370 is busy. eth0: tx frame #1372 is busy. eth2: Tx error, status 4 (FID=0156) eth1: tx frame #3832 is busy. eth2: Tx error, status 4 (FID=0156) eth2: Tx error, status 4 (FID=01E2) eth2: Tx error, status 4 (FID=0192) eth1: tx frame #4105 is busy. eth1: tx frame #4108 is busy. eth1: tx frame #4115 is busy. eth1: tx frame #4119 is busy.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |