X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Subject: RE: ssh with tunnel stacktrace on core duo
Date: Wed, 7 Jun 2006 14:18:31 -0400
Message-ID: <C874DBE9D30B584587F8CD0EC34DA8BE01BEAC93@EX00.idirect.net>
From: "Harig, Mark" <maharig AT idirect DOT net>
To: =?iso-8859-1?Q?J=FCrgen_Schmitz?= <juergen DOT schmitz AT philosys DOT de>,
   <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k57ILZvW025411

> -----Original Message-----
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Jürgen Schmitz
> Sent: Wednesday, June 07, 2006 6:36 AM
> To: cygwin AT cygwin DOT com
> 
> Hi!
> 
> I'm using cygwin SSH for a long time now on a centrino notebook. Now I
> have to switch over to a new core duo notebook with 2 GB ram.
> 
....
> 
> Any help is welcome,
> 

A number of users have reported what appear to be
related symptoms of this problem, that is, Cygwin's
ssh failing on computers (laptops only?) with dual-core
CPUs.  (Although I have seen this problem on three
(identical) dual-core laptops, I no longer have access
to those computers so I cannot investigate this problem
any further.)  If you are interested in helping to
resolve this problem, you might try the following:

   1. Use 'scp' to attempt to copy a file from your ssh
      server to your computer that has Cygwin installed on it.
      The file should be relatively large (greater than 100
      kilobytes).  If the problem is consistent, then you
      should see that scp fails to copy this large file (or
      try a set of "large" files).

   2. Retry the scp command but use 'strace' to get some
      idea about where the code is failing.

   3. Retry the command, but use 'gdb' to debug ssh or scp
      code.

---

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/