This is the mail archive of the
mailing list for the Cygwin project.
RE: scp timeout on dual-core processor
- From: "Steve Baldwin" <stbaldwin at multiservice dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 18 Jul 2006 05:35:35 +1000
- Subject: RE: scp timeout on dual-core processor
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org] On Behalf
> Of Christopher Faylor
> Sent: Tuesday, 18 July 2006 5:33 AM
> To: email@example.com
> Subject: Re: scp timeout on dual-core processor
> On Tue, Jul 18, 2006 at 05:06:07AM +1000, Steve Baldwin wrote:
> >> -----Original Message-----
> >> From: firstname.lastname@example.org [mailto:email@example.com] On
> >> Of Larry Hall (Cygwin)
> >> Sent: Tuesday, 18 July 2006 4:54 AM
> >> To: firstname.lastname@example.org
> >> Subject: Re: scp timeout on dual-core processor
> >> Kurt T Stam wrote:
> >> > I have the same exact problem as Steve:
> >> >
> >> > "I have a (what appears to be) similar problem also with a dual core
> >> >
> >> > (Centrino Duo) machine. My problem manifests when I attempt to paste
> >> an
> >> > X window (i.e. click the middle mouse button). I immediately (100%
> >> > reproducible) get "Disconnecting: Timeout, server not responding.",
> >> my
> >> > ssh session dies."
> >> >
> >> > I just got a new machine with a centrino duo, dual core processor...
> >> > Just another data point.. If there is anything I can do in terms of
> >> > diagnosis please let me know.
> >> Well according to <http://sourceware.org/ml/cygwin/2006-
> >> Steve believes this has more to do with locally installed software than
> >> hardware. Perhaps you can help him narrow down the software causing
> >> trouble? In the past, there have been problems with Dell machines of
> >> configuration coming with Embasy software which was really gumming up
> >> works. Maybe you can investigate this avenue if you also have this
> >> software.
> >Just to confirm - removing the Embassy Trust Suite (the s/w that drives
> >fingerprint reader) solved this exact problem for me (and several other
> And, presumably you also chiselled out the second CPU from the surrounding
> epoxy, too. Don't forget that crucial step.
> This is a "dual core problem" after all...
Yep. Nuked quite a few laptops in the process but got there in the end.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html