X-Spam-Check-By: sourceware.org Date: Thu, 18 May 2006 16:36:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ssh (protocol 2) crash on brand new T2600 dual core cpu (Dell Latitude D620) Message-ID: <20060518203600.GA20110@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <446CA289 DOT 5030403 AT zib DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <446CA289.5030403@zib.de> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 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/