> On Thu, 2005-08-04 at 20:31 +0200, Alexander Dalloz wrote: > > Am Do, den 04.08.2005 schrieb FC4 um 20:14: > > > > No HTML formatted list posts please. > > > > > I installed FC4 with no issue and it has been running for a month. > > > Just got everything running good. So what did I do? I selected > > > up2date and pick all. > > > > > > Now I get the following network errors. System is running 98% idle.. > > > > > > ifconfig eth0 > > > eth0 Link encap:Ethernet HWaddr 00:A0:CC:E6:94:AE > > > inet addr:192.168.20.12 Bcast:192.168.20.255 > > > Mask:255.255.255.0 > > > inet6 addr: fe80::2a0:ccff:fee6:94ae/64 Scope:Link > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:1313 errors:51 dropped:0 overruns:0 frame:17 > > > TX packets:1360 errors:66 dropped:0 overruns:0 carrier:30 > > > collisions:0 txqueuelen:1000 > > > RX bytes:661901 (646.3 KiB) TX bytes:117653 (114.8 KiB) > > > Interrupt:5 Base address:0x8000 > > > > Errors to be seen in both directions (TX and RX). > > > > > [root@redhat ~]# uptime > > > 13:52:51 up 16 min, 3 users, load average: 0.04, 0.34, 0.32 > > > > > > When I ping the system from another box... > > > Reply from 192.168.20.12: bytes=32 time=3995ms TTL=64 > > > Reply from 192.168.20.12: bytes=32 time<1ms TTL=64 > > > Reply from 192.168.20.12: bytes=32 time<1ms TTL=64 > > > Request timed out. > > > Reply from 192.168.20.12: bytes=32 time=714ms TTL=64 > > > Request timed out. > > > Reply from 192.168.20.12: bytes=32 time=2214ms TTL=64 > > > Request timed out. > > > Reply from 192.168.20.12: bytes=32 time=2714ms TTL=64 > > > Reply from 192.168.20.12: bytes=32 time<1ms TTL=64 > > > Request timed out. > > > Reply from 192.168.20.12: bytes=32 time=1714ms TTL=64 > > > Reply from 192.168.20.12: bytes=32 time<1ms TTL=64 > > > > > > > > > > > > SSH is unusable as it is to slow. > > > > > > I have changed out ethernet cards ,cables and move > > > it to another network switch with no change. > > > > Missing information: > > a) kernel running: uname -a > > b) which NIC model / manufacturer, info from: /sbin/lspci > > c) which kernel module used for that NIC: /sbin/lsmod + / grep "eth0" > > /etc/modprobe.conf > > > > Alexander > > > > > > port speed mismatch? > > what's the output of > mii-tool eth0 > mii-diag eth0 > > > > -- > Tony Placilla, RHCT > anthony_placilla@xxxxxxxx port speed mismatch? That was my first guess... It even fails on my wireless card which was working before the update. I changed the switch to a 100FD and had the same problem. I verify the setting after changing switch types with mii-diag [root@redhat ~]# mii-diag eth0 Basic registers of MII PHY #32: 1000 784c 0000 0000 03e1 45e1 0000 0000. The autonegotiated capability is 01e0. The autonegotiated media type is 100baseTx-FD. Basic mode control register 0x1000: Auto-negotiation enabled. You have link beat, and everything is working OK. Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control. End of basic transceiver information. [root@redhat ~]# mii-tool eth0 eth0: link ok
