public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: "Hyperthreading" problems
Date: Fri, 24 Dec 2004 15:50:00 -0000	[thread overview]
Message-ID: <20041224155136.GE22966@trixie.casa.cgf.cx> (raw)
In-Reply-To: <KPEOIHNCAFKIFOBNMPJCEEFCCEAA.stephane.donze@exalead.com>

On Fri, Dec 24, 2004 at 09:01:17AM +0100, St?phane Donz? wrote:
>we have encountered random hangs and crashes in cygwin (see output of
>cygcheck attached to this message) on a dual-processor server running
>Windows Server 2003. IMHO, the so-called "hyperthreading problems" reported
>recently on this mailing list just have nothing to do with hyperthreading,
>but are more generally related to multi-processor issues.

If you have followed the thread, then you know that I have a multi-processor
system and I don't have the problem.

>I used the following test (found on this mailing list archive, posted 6 Apr
>2004 by Chuck McDevitt):
>
><QUOTE>
>
>#! /bin/ksh
>mypath=$(pwd)
>while [[ ! -z $mypath ]]
>do
> mypath=$(pwd)
> if [[ -z $mypath ]]
> then
>  echo "Test Failed......Path is empty"
> fi
>done

There is no point in reposting scripts.  There is no point in
recapitulating the problem.  There is no point in making obvious
observations about what one would suspect the cause would be without
bothering to look at the code.

Your options are to fix the problem yourself or wait until I someday
have a system which demonstrates the problem.

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/

  reply	other threads:[~2004-12-24 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24  8:01 Stéphane Donzé
2004-12-24 15:50 ` Christopher Faylor [this message]
     [not found] <41D1D2B2.4030200@exalead.com>
2004-12-28 22:29 ` Stephane Donze
2004-12-28 23:15   ` Christopher Faylor
2004-12-29  0:50   ` Brian Bruns
2005-01-01 21:07     ` Stephane Donze
2005-01-02 19:19       ` Larry Hall
2004-12-29  1:26   ` Brian Dessent
2004-12-29  1:51     ` Christopher Faylor
2004-12-29 15:33       ` Volker Bandke
2004-12-28 22:50 Bakken, Luke
2004-12-28 22:53 Robb, Sam

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=20041224155136.GE22966@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=cygwin@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).