From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Problems with ssh/scp/sftp on a dual core Dell Latitude D820
Date: Fri, 26 May 2006 17:54:00 -0000 [thread overview]
Message-ID: <20060526175404.GC8739@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20060526174326.GD11150@implementation>
On Fri, May 26, 2006 at 07:43:26PM +0200, Samuel Thibault wrote:
>Chris Richardson, le Fri 26 May 2006 06:22:32 -0700, a ?crit :
>> Does anyone have a fix for this?
>
>Disable the second core. Cygwin seems to not work very well with SMP
>systems.
Also check the fan speed. High RPMs cause vibration which has been
known to derail bits from the CPU. If you open your case and see a lot
of "dust" that's probably extra lost bits caused by vibration. Running
your fan at the wrong speed can eventually completely deplete your CPU
of bits, effectively turning it into a 16MHZ Z80.
cgf
next parent reply other threads:[~2006-05-26 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8392298c0605260622q5038ceb3i6cc6531b06d76824@mail.gmail.com>
[not found] ` <20060526174326.GD11150@implementation>
2006-05-26 17:54 ` Christopher Faylor [this message]
2006-05-26 18:28 ` One Angry User
2006-05-26 19:00 ` mwoehlke
2006-05-26 19:13 ` One Angry User
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060526175404.GC8739@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).