X-Spam-Check-By: sourceware.org Message-ID: <447FE81C.8010605@zib.de> Date: Fri, 02 Jun 2006 09:26:20 +0200 From: Andreas Loebel Reply-To: loebel AT zib DOT de User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.2) Gecko/20060409 SeaMonkey/1.0.1 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: ssh (protocol 2) crash on brand new T2600 dual core cpu (Dell Latitude D620) References: <446CA289 DOT 5030403 AT zib DOT de> In-Reply-To: <446CA289.5030403@zib.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, The crash comes from the biolsp.dll provided by the TPM software from wave.com. A biolsp.dll fix provided by www.wave.com solves the problem. Andreas Andreas Loebel wrote: > Hi all, > > I observed a ssh (protocol 2) crash (using cvs, rsync, scp, unison, > etc.) only on my brand new T2600 dual core cpu whenever the load on > the ssh tunnel raises. > > I have also noticed a thread about "scp timeout on dual-core > processor", which sounds very similar, but provides no solution. > > The only information I can provide is a ssh.exe.stackdump: > > Exception: STATUS_ACCESS_VIOLATION at eip=00F449B9 > eax=00000015 ebx=002298AC ecx=2F54534E edx=00229778 esi=7C809BF5 > edi=2F54534E > ebp=00229674 esp=002287F8 program=C:\cygwin\bin\ssh.exe, pid 4888, > thread main > cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 > Stack trace: > Frame Function Args > 00229674 00F449B9 (00000000, 00229668, 610FD4BC, 0022FBB8) > End of stack trace > > However, using the insecure protocol 1 works. But this is only some > workaround that I do not really want to use and that might not be > available on many servers. > > Any ideas? > > Andreas -- 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/