Hi.
Look at this (you can try youself, i wont reboot it for a few days):
PING 164.8.233.107 (164.8.233.107) 56(84) bytes of data.
64 bytes from 164.8.233.107: icmp_seq=1 ttl=64 time=8366 ms
64 bytes from 164.8.233.107: icmp_seq=2 ttl=64 time=7367 ms
64 bytes from 164.8.233.107: icmp_seq=3 ttl=64 time=6367 ms
64 bytes from 164.8.233.107: icmp_seq=4 ttl=64 time=5367 ms
64 bytes from 164.8.233.107: icmp_seq=5 ttl=64 time=4367 ms
64 bytes from 164.8.233.107: icmp_seq=6 ttl=64 time=3367 ms
64 bytes from 164.8.233.107: icmp_seq=7 ttl=64 time=2368 ms
64 bytes from 164.8.233.107: icmp_seq=8 ttl=64 time=1368 ms
64 bytes from 164.8.233.107: icmp_seq=9 ttl=64 time=368 ms
This is the third time, and i don't know how to reproduce it. Some uptime
seem to help (between 13.2 days and 14.5 days in this case).
It's not heavily loaded, serves mainly as ftp server on 100 mbit LAN.
uname -a:
Linux nd47 2.6.7 #9 SMP Wed Jun 16 12:19:56 CEST 2004 i686 unknown unknown GNU/Linux
(SMP kernel on UP machine, no proprietary modules)
dmesg:
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xd000. Vers LK1.1.19
There's nothing in dmesg since the problem appeared.
lspci:
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
ifconfig eth0:
eth0 Link encap:Ethernet HWaddr 00:50:DA:C9:7C:44
inet addr:164.8.233.107 Bcast:164.8.255.255 Mask:255.255.255.0
inet6 addr: fe80::250:daff:fec9:7c44/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14776725 errors:0 dropped:0 overruns:0 frame:0
TX packets:15194923 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1492628905 (1423.4 Mb) TX bytes:4070977122 (3882.3 Mb)
Interrupt:5 Base address:0xd000
mii-tool -v:
eth0: negotiated 100baseTx-FD, link ok
product info: vendor 00:00:00, model 0 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
Anything i can try, to help resolve this? (Preferably not something that
involves rebooting, because it can take months for this to happen again)
Domen
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
