netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Didier Raboud <didier@raboud.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Netdev <netdev@vger.kernel.org>,
	bugme-daemon@bugzilla.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10903] New: ssh connections hang with 2.6.26-rc5
Date: Wed, 18 Jun 2008 02:04:43 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806180152410.32420@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <200806172359.33768.didier@raboud.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=utf-8, Size: 3090 bytes --]

On Tue, 17 Jun 2008, Didier Raboud wrote:

> Le lundi 16 juin 2008 15:21:25 Ilpo Järvinen, vous avez écrit :
> > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=10903
> > > > > >
> > > > > >            Summary: ssh connections hang with 2.6.26-rc5
> > > > > >            Product: Networking
> > > > > >            Version: 2.5
> > > > > >      KernelVersion: 2.6.26-rc5
> > > > > >           Platform: All
> > > > > >         OS/Version: Linux
> > > > > >               Tree: Mainline
> > > > > >             Status: NEW
> > > > > >           Severity: normal
> > > > > >           Priority: P1
> > > > > >          Component: Other
> > > > > >         AssignedTo: acme@ghostprotocols.net
> > > > > >         ReportedBy: didier@raboud.com
> > > > > >
> > > > > >
> > > > > > Latest working kernel version: 2.6.25-2
> > > > > > Earliest failing kernel version: 2.6.26-rc5
> > > > > > Distribution: Debian (Lenny + Sid)
> > > > > > Hardware Environment: amd64 (Dell Latitude D630)
> > > > > > Software Environment: KDE
> > > > > > Problem Description:
> > > > > >
> > > > > > With kernel version 2.6.26-rc5, the ssh connections to remote
> > > > > > servers randomly
> > > > > > hang (no error message). No amelioration despite the activation of
> > > > > > "ServerAliveInterval" on both sides.
> > > > (...)
> > > 
> > > The common point is my use of "iwl3945" : I have always tried the ssh
> > > connections through WiFi.
> > > 
> > > > So please gather this information (at least for the relevant
> > > > connections):
> > > >
> > > > $ netstat -pn
> > > > $ cat /proc/net/tcp
> 
> I used a script which logged both every 15 seconds on both sides (in "screen" 
> on server side). I then triggered a hang with several "seq 1 100" in the ssh 
> session. The logs are in the attached debug_ssh_hang.tar.gz . The hang 
> appeared between 234327 and 234342 on the client side (so somewhere between 
> 234324, 234339 and 234354 on the server side).
> 
> I hope it'll help.

Thanks, a quick look didn't indicate anything similar to one other report 
from Håkon... I'd probably need a tcpdump.

> > You probably run it under X, no? Please switch beforehand to some other vt
> > (a textual one) then (Ctrl-Alt-Fn, where n < 6) and then log in and
> > running that command there and see if you get some output into screen
> > there. If you see something (e.g., a sudden OOPS message or some other
> > warning printed) when it locks up, the easiest things is to take a shot
> > with a digicam (or write it down somewhere else) and send that shot (or
> > those details) to us please.
> 
> I tried the following in vt1 (under the new 2.6.26-rc6 with kdm stopped):
> 
> # tcpdump -i wlan0 -w /tmp/tcpdump.wlan0
> 
> and I got the attached "soft lockup".

Thanks, I guess the folks at linux-wireless can continue in resolving this 
one with you (I'm out of time anyway now).

> > ...Once you have a tcpdump, I can probably figure at least something out
> > (though it might still just point to the right direction rather than
> > exposing the actual cause).
> 
> I can't get one... :)

...Ok.

-- 
 i.

  parent reply	other threads:[~2008-06-17 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10903-10286@http.bugzilla.kernel.org/>
2008-06-13  9:58 ` [Bugme-new] [Bug 10903] New: ssh connections hang with 2.6.26-rc5 Andrew Morton
2008-06-14 20:45   ` Ilpo Järvinen
2008-06-15 13:37     ` Didier Raboud
2008-06-16 13:21       ` Ilpo Järvinen
     [not found]         ` <200806172359.33768.didier@raboud.com>
2008-06-17 23:04           ` Ilpo Järvinen [this message]
     [not found]             ` <Pine.LNX.4.64.0806180152410.32420-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2008-06-18  7:24               ` Johannes Berg
2008-06-18  8:05                 ` David Miller
     [not found]                   ` <20080618.010528.05757230.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-06-18  8:26                     ` David Miller
     [not found]                 ` <1213773887.3803.158.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-18 11:34                   ` Didier Raboud
     [not found]                     ` <200806181334.10654.didier-efQUOpnRmEvQT0dZR+AlfA@public.gmane.org>
2008-06-18 11:39                       ` Michael Buesch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0806180152410.32420@wrl-59.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=didier@raboud.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).