Re: Any way to tell where the network problem is?
On Tue, 14 Feb 2012 12:14:50 -0800, Ross Boylan wrote:
> On Thu, 2012-02-09 at 14:51 +0000, Camaleón wrote:
>> On Wed, 08 Feb 2012 22:44:45 -0800, Ross Boylan wrote:
>>
>> > I've been losing network connections between my laptop and main
>> > machine. The logs from the main machine are below.
>>
>> I can't see them, neither attached nor linked :-?
> Thanks for your response. I've been having some mail problems and only
> just noticed it.
>
> It's odd you don't see the logs; they show up in the archive. I'll try
> pasting them here:
Thanks!
It has to be a problem with my newsreader (pan) that was not capable of
showing the logs. Weird.
> Feb 8 19:45:40 corn kernel: [1987612.981170] ethfast: Detected Tx Unit Hang:
(...)
> Feb 8 19:45:49 corn kernel: [1987622.027816] NETDEV WATCHDOG: ethfast: transmit timed out
> Feb 8 19:45:52 corn kernel: [1987624.923313] ethfast: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
By reading the logs, I can point you to these two bugs:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518182
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657689
As you are using lenny, I would try with an updated kernel (2.6.32) from
backports or better yet, take this as an opportunity to upgrade to
Squeeze or another supported version :-)
>> > Is there any way of telling from them if the network problem is
>> > occurring on the local or remote (laptop) machine?
>>
>> Ping from/to both machines and see the output.
> How will that tell me where the problem lies?
Sure! I didn't see the logs, sorry. I thought you were having some sort
of disconnects from one of the computers.
> Here's what I get from the server while things are working OK:
> $ ping 192.168.40.30
> PING 192.168.40.30 (192.168.40.30) 56(84) bytes of data. 64 bytes from
> 192.168.40.30: icmp_seq=1 ttl=128 time=0.565 ms 64 bytes from
> 192.168.40.30: icmp_seq=2 ttl=128 time=0.533 ms
> $ traceroute 192.168.40.30
> traceroute to 192.168.40.30 (192.168.40.30), 30 hops max, 40 byte
> packets
> 1 cotton.betterworld.us (192.168.40.30) 24.460 ms * *
> There aren't any intermediate steps so that I could see the packets
> going part-way.
Mmm, okay. But are you pinging and tracerouting from/to the same host?
>> How are the computers connected, directly with a crossover network
>> cable, using a switch, Internet (remote) connection...?
> Using a new D-Link Gigabit switch (Model DGS-1008G) and ethernet. I've
> also tried wireless, which additionally uses a new D-Link Wireless N
> router (Model DIR-601), i.e., laptop-> wireless -> switch -> server; the
> laptop only has wireless G. It's basically impossible to keep a good
> connection up, though it works for awhile after I start up. The failure
> is not limited to SAMBA. The laptop is definitely not in good shape.
I see. Anyway, although the laptop is not at its bests, the logs are
concerning the linux box (the ethernet driver "hangs"). And one more
thing... "ethfast" looks like a 10/100 driver though it says "link up
1000 Mbps". What kernel modules are you loading for both cards?
Greetings,
--
Camaleón
Reply to: