[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: freezing Ethernet crossover link.



peasthope@shaw.ca put forth on 12/12/2009 4:17 PM:
> This is a phenomenon in Squeeze for the recent 
> few weeks.
> 
> A Linux router and workstation are connected 
> with a crossover cable.  This is on the router.  
> Communication appears normal until after 
> some minutes or hours it freezes so that  
> "/etc/init.d/networking restart" fails.

Interesting.

> dalton:/home/peter# ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:1d:7e:00:e5:da
>           inet addr:172.24.1.1  Bcast:172.24.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::21d:7eff:fe00:e5da/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 
> dalton:/home/peter# uname -a
> Linux dalton 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686 GNU/Linux
> 
> Any ideas about the 0s from ifconfig?

Yes, it's not sending or receiving any packets.  /etc/init.d/networking
restart may have failed to bring the NIC back up to a working state, but
it may have reset all the counters to zero.  I'm not familiar with the
networking code--just a user, making an educated guess.

What changed the day before this started happening?  Has the
kernel/driver changed, or just userspace stuff?  Also, what NIC/driver
are you using?  Does this situation occur only on eth1 or does eth0 also
exhibit this behavior?  How many ethernet interfaces does the router
have?  What is the make/model of each interface?

Are you sure it's a software problem?  Could the PHY on this NIC be
going south?  Have you swapped in a new crossover cable?  Have you tried
swapping the 'flaky' NIC out?

--
Stan


Reply to: