Re: Any way to tell where the network problem is?
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:
Feb 8 19:45:40 corn kernel: [1987612.981170] ethfast: Detected Tx Unit Hang:
Feb 8 19:45:40 corn kernel: [1987612.981170] TDH <e6>
Feb 8 19:45:40 corn kernel: [1987612.981170] TDT <ea>
Feb 8 19:45:40 corn kernel: [1987612.981170] next_to_use <ea>
Feb 8 19:45:40 corn kernel: [1987612.981170] next_to_clean <e6>
Feb 8 19:45:40 corn kernel: [1987612.981170] buffer_info[next_to_clean]:
Feb 8 19:45:40 corn kernel: [1987612.981170] time_stamp <1cc1a41e>
Feb 8 19:45:40 corn kernel: [1987612.981170] next_to_watch <e6>
Feb 8 19:45:40 corn kernel: [1987612.981170] jiffies <1cc1a609>
Feb 8 19:45:40 corn kernel: [1987612.981170] next_to_watch.status <0>
Feb 8 19:45:42 corn kernel: [1987614.987049] ethfast: Detected Tx Unit Hang:
Feb 8 19:45:42 corn kernel: [1987614.987053] TDH <e6>
Feb 8 19:45:42 corn kernel: [1987614.987055] TDT <ea>
Feb 8 19:45:42 corn kernel: [1987614.987057] next_to_use <ea>
Feb 8 19:45:42 corn kernel: [1987614.987059] next_to_clean <e6>
Feb 8 19:45:42 corn kernel: [1987614.987061] buffer_info[next_to_clean]:
Feb 8 19:45:42 corn kernel: [1987614.987062] time_stamp <1cc1a41e>
Feb 8 19:45:42 corn kernel: [1987614.987064] next_to_watch <e6>
Feb 8 19:45:42 corn kernel: [1987614.987066] jiffies <1cc1a7fc>
Feb 8 19:45:42 corn kernel: [1987614.987068] next_to_watch.status <0>
Feb 8 19:45:44 corn kernel: [1987616.993948] ethfast: Detected Tx Unit Hang:
Feb 8 19:45:44 corn kernel: [1987616.993951] TDH <e6>
Feb 8 19:45:44 corn kernel: [1987616.993953] TDT <ea>
Feb 8 19:45:44 corn kernel: [1987616.993955] next_to_use <ea>
Feb 8 19:45:44 corn kernel: [1987616.993957] next_to_clean <e6>
Feb 8 19:45:44 corn kernel: [1987616.993959] buffer_info[next_to_clean]:
Feb 8 19:45:44 corn kernel: [1987616.993961] time_stamp <1cc1a41e>
Feb 8 19:45:44 corn kernel: [1987616.993963] next_to_watch <e6>
Feb 8 19:45:44 corn kernel: [1987616.993965] jiffies <1cc1a9f0>
Feb 8 19:45:44 corn kernel: [1987616.993966] next_to_watch.status <0>
Feb 8 19:45:46 corn kernel: [1987619.008884] ethfast: Detected Tx Unit Hang:
Feb 8 19:45:46 corn kernel: [1987619.008888] TDH <e6>
Feb 8 19:45:46 corn kernel: [1987619.008890] TDT <ea>
Feb 8 19:45:46 corn kernel: [1987619.008892] next_to_use <ea>
Feb 8 19:45:46 corn kernel: [1987619.008893] next_to_clean <e6>
Feb 8 19:45:46 corn kernel: [1987619.008896] buffer_info[next_to_clean]:
Feb 8 19:45:46 corn kernel: [1987619.008898] time_stamp <1cc1a41e>
Feb 8 19:45:46 corn kernel: [1987619.008899] next_to_watch <e6>
Feb 8 19:45:46 corn kernel: [1987619.008901] jiffies <1cc1abe4>
Feb 8 19:45:46 corn kernel: [1987619.008903] next_to_watch.status <0>
Feb 8 19:45:48 corn kernel: [1987621.030882] ethfast: Detected Tx Unit Hang:
Feb 8 19:45:48 corn kernel: [1987621.030882] TDH <e6>
Feb 8 19:45:48 corn kernel: [1987621.030882] TDT <ea>
Feb 8 19:45:48 corn kernel: [1987621.030882] next_to_use <ea>
Feb 8 19:45:48 corn kernel: [1987621.030882] next_to_clean <e6>
Feb 8 19:45:48 corn kernel: [1987621.030882] buffer_info[next_to_clean]:
Feb 8 19:45:48 corn kernel: [1987621.030882] time_stamp <1cc1a41e>
Feb 8 19:45:48 corn kernel: [1987621.030882] next_to_watch <e6>
Feb 8 19:45:48 corn kernel: [1987621.030882] jiffies <1cc1add9>
Feb 8 19:45:48 corn kernel: [1987621.030882] next_to_watch.status <0>
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
>
> > 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? 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.
>
> > The local machine is running Debian Lenny 2.6.26-2-686 #1 SMP
> > (Hyperthreaded P4): 02:00.0 Ethernet controller: Intel Corporation
> > 82573V Gigabit Ethernet Controller (Copper) (rev 03)
> > 05:01.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet
> > Pro 100 (rev 10)
> >
> > I believe the Gigabit one has the connection. The failures typically
> > occur during copies of large file to the local Samba share; the laptop
> > is running Vista.
>
> 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.
Thanks.
Ross
Reply to: