ssh (protocol 2) crash on brand new T2600 dual core cpu (Dell Latitude D620)

ssh (protocol 2) crash on brand new T2600 dual core cpu (Dell Latitude D620)

[Andreas Loebel]

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/

Re: ssh (protocol 2) crash on brand new T2600 dual core cpu (Dell Latitude D620)

[Christopher Faylor]

On Thu, May 18, 2006 at 06:36:25PM +0200, 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.

I think the saga of the dual core cpu (not to be confused with the epic
of the multithreading cpu) was proven to be just a myth.

The current expert thinking is that any problems are either due to fan
speed or case color.

cgf

--
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/

Re: ssh (protocol 2) crash on brand new T2600 dual core cpu (Dell Latitude D620)

[Andreas Loebel]

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/