lkml.org 
[lkml]   [1998]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject2.1.88 network problems
Date
Been running 2.1.88 for about 10 days now and have seen several
network-related problems.

#1 - On two different machines the network card (a 3c905) has hosed for
about 5-20 minutes and then started again:

Feb 26 05:32:30 picard kernel: eth0: transmit timed out, tx_status 00 status
e000.
Feb 26 05:32:50 picard last message repeated 2 times
Feb 26 05:32:50 picard kernel: eth0: Host error, FIFO diagnostic register
0400.
Feb 26 05:34:20 picard kernel: eth0: Transmit error, Tx status register d0.
Feb 26 05:36:29 picard kernel: eth0: transmit timed out, tx_status 00 status
e000.
Feb 26 05:36:59 picard last message repeated 3 times
Feb 26 05:37:59 picard last message repeated 6 times
Feb 26 05:38:59 picard last message repeated 6 times
....'Feb 26 05:40:49 picard kernel: eth0: transmit timed out, tx_status 00
status e000.
Feb 26 05:40:50 picard kernel: eth0: Host error, FIFO diagnostic register
0400.
Feb 26 05:40:50 picard kernel: eth0: Transmit error, Tx status register 90.

In this case I just did an "ifconfig eth0 down;ifconfig eth0 up" and all was
well.

The other machine just:
Mar 2 15:48:36 medusa kernel: eth0: transmit timed out, tx_status 00 status
e000.
Mar 2 15:48:36 medusa kernel: eth0: Host error, FIFO diagnostic register
0400.
and then started up again by itself.

#2 - After about 8 days one machine all-of-a-sudden lot it's default route
(!!)...not sure how that happened.




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:41    [W:0.017 / U:0.740 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site