Messages in this thread | | | Date | Mon, 20 Jul 1998 18:31:59 +0200 | From | tilo winkler <> | Subject | 2.0.34 and 3c595: transmit error, tx status register .. |
| |
Hi,
I had been using 2.0.33 without problems for a long time. I had to upgrade to 2.0.34 because of the bugs in the tcp/ip code which caused my machine to crash. Anyway, since the upgrade to 2.0.34 I have the following messages in my syslog sporadically. Its not only that they get logged, the machine is also sometimes not available via network, but this also recovers after a minute or so.
Jul 20 17:59:34 snafu kernel: eth0: Transmit error, Tx status register 90. Jul 20 18:02:38 snafu kernel: eth0: Transmit error, Tx status register c0. Jul 20 18:03:22 snafu kernel: eth0: Transmit error, Tx status register 90.
netstat also seems to report some problems.
# netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR X-DRP TX-OVR Flags lo 3584 0 39560 0 0 0 39560 0 0 0 BLRU eth0 1500 0 614082 24 24 0 716544 0 0 4 BRU
The machine is a p200 (uni-processor) connected to a 100mbit ethernet. The (unmodified) kernel was compiled with gcc 2.7.2. Load average was about 0 when that happened.
If there is more information needed I would be happy to provide it.
--
-winkler-
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
| |