I have an HP 6005 workstation with a fresh install of Debian Squeeze,
and I am seeing some very strange networking behavior. The network
connection seems to drop periodically, but it comes back if you hit a
key on the keyboard plugged into the machine.
Here's the general way it happens:
1. I am logged into the machine via SSH
2. I attempt to transfer a large file to or from the machine via SFTP
3. At some point during the transfer, my SSH session will just hang and
all connectivity to the machine is lost (I can't ping it, start a new
SSH session, etc.)
4. If I walk over to the physical machine and hit any key on the
keyboard, all network connectivity immediately resumes.
I can reproduce this with pretty good consistency. It seems to happen
any time I am doing something fairly network intensive (large file
transfer, X11 forwarding, etc.) This is a clean command-line-only
install of Squeeze (64-bit) with the default kernel (2.6.32-5-amd64).
The information for the onboard NIC is as follows:
On Wed, 09 Mar 2011 14:11:41 -0500
"David A. Parker" <dparker@utica.edu> wrote:
> Hello,
>
> I have an HP 6005 workstation with a fresh install of Debian Squeeze,
> and I am seeing some very strange networking behavior. The network
> connection seems to drop periodically, but it comes back if you hit a
> key on the keyboard plugged into the machine.
>
> Here's the general way it happens:
...
> I can reproduce this with pretty good consistency. It seems to happen
> any time I am doing something fairly network intensive (large file
> transfer, X11 forwarding, etc.) This is a clean command-line-only
> install of Squeeze (64-bit) with the default kernel (2.6.32-5-amd64).
I doubt I'll be able to help, but just to clarify: you're pretty
certain that the problem doesn't occur when the connection is not under
load, such as during an ordinary interactive ssh session?
One might suspect some sort of sleep / suspend behavior, but I
really don't know.
Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110309163047.380821e8.celejar@gmail.com">http://lists.debian.org/20110309163047.380821e8.celejar@gmail.com
03-09-2011, 09:32 PM
"David A. Parker"
Network connection drops in Squeeze
On 03/09/2011 04:30 PM, Celejar wrote:
On Wed, 09 Mar 2011 14:11:41 -0500
"David A. Parker"<dparker@utica.edu> wrote:
Hello,
I have an HP 6005 workstation with a fresh install of Debian Squeeze,
and I am seeing some very strange networking behavior. The network
connection seems to drop periodically, but it comes back if you hit a
key on the keyboard plugged into the machine.
Here's the general way it happens:
...
I can reproduce this with pretty good consistency. It seems to happen
any time I am doing something fairly network intensive (large file
transfer, X11 forwarding, etc.) This is a clean command-line-only
install of Squeeze (64-bit) with the default kernel (2.6.32-5-amd64).
I doubt I'll be able to help, but just to clarify: you're pretty
certain that the problem doesn't occur when the connection is not under
load, such as during an ordinary interactive ssh session?
One might suspect some sort of sleep / suspend behavior, but I
really don't know.
Thanks Celejar.
So far, this has never happened randomly during an SSH session. It
always seems to be triggered by some sort of network activity. What's
especially frustrating is that absolutely nothing gets logged in the
system logs when this happens.
I originally suspected that the network adapter was being put to sleep,
but that doesn't explain why I can sustain a normal SSH connection for
long periods of time. I can even leave the computer on overnight and
nothing stops working. If it were a sleep or suspend issue, I would
think it would happen when the interface was idle, but I haven't ruled
this out.
Does anyone know what I should check to see if this is some sort of
power management issue? I stopped acpid, but the behavior persists.
Thanks!
Dave
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
So far, this has never happened randomly during an SSH session. It
always seems to be triggered by some sort of network activity. What's
especially frustrating is that absolutely nothing gets logged in the
system logs when this happens.
I originally suspected that the network adapter was being put to sleep,
but that doesn't explain why I can sustain a normal SSH connection for
long periods of time. I can even leave the computer on overnight and
nothing stops working. If it were a sleep or suspend issue, I would
think it would happen when the interface was idle, but I haven't ruled
this out.
Does anyone know what I should check to see if this is some sort of
power management issue? I stopped acpid, but the behavior persists.
The behavior I'm seeing is very similar to what's described here:
So far, this has never happened randomly during an SSH session. It
always seems to be triggered by some sort of network activity. What's
especially frustrating is that absolutely nothing gets logged in the
system logs when this happens.
I originally suspected that the network adapter was being put to sleep,
but that doesn't explain why I can sustain a normal SSH connection for
long periods of time. I can even leave the computer on overnight and
nothing stops working. If it were a sleep or suspend issue, I would
think it would happen when the interface was idle, but I haven't ruled
this out.
Does anyone know what I should check to see if this is some sort of
power management issue? I stopped acpid, but the behavior persists.
The behavior I'm seeing is very similar to what's described here:
I triggered one of these wird lock-ups and then let it sit in the
"frozen" state for several minutes. It eventually corrected the
problem, and the following messages got dumped to the logs: