On Sun, Aug 29, 2004 at 08:00:13AM -0400, Christopher Faylor wrote:
>The problem has not been either identified or resolved and it won't be
>resolved until someone debugs the problem or someone sends me a system
>which manifests the problem so that I can resolve the problem.
Just to make it clear,
[snip problems building under cygwin on HT machines]
>
> FWIW,
> Kate Ebneter
> iPod Build Engineer
> Apple Computer, Inc.
Um, just out of curiosity... Why is Apple using a Unix emulation running on
Microsoft Windows to do their builds?
;-)
--
Gary R. Van Sickle
--
Unsubscribe info: htt
On Aug 30, 2004, at 2:55 PM, Christopher Faylor wrote:
On Mon, Aug 30, 2004 at 02:49:09PM -0700, Kate Ebneter wrote:
We had serious problems using GNU Make out of cygwin that we were only
able to resolve by turning off hyperthreading on the relevant
machines.
I've tried various newer cygwins wit
On Aug 30, 2004, at 9:20 AM, Pierre A. Humblet wrote:
Huh? I don't even own a single dog, just a WinME.
It has crossed my mind that the fork bug has something to do with
the hyperthreaded machine problem, and even that it might well be
the last bug in Cygwin.
Processor affinity not helping is consi
On Mon, Aug 30, 2004 at 02:49:09PM -0700, Kate Ebneter wrote:
>On Aug 28, 2004, at 10:49 PM, David Chatterton wrote:
>>There was some discussion back in April regarding problems with loaded
>>hyperthreaded machines including thread activation errors and other
>>strange problems.
>>
>>Were these pro
On Aug 28, 2004, at 10:49 PM, David Chatterton wrote:
There was some discussion back in April regarding problems
with loaded hyperthreaded machines including thread activation
errors and other strange problems.
Were these problems identified and resolved, or are they
still outstanding?
We had serio
Chuck,
We have a build environment for a reasonably large piece of code
that several people could be building at the same time. On a dual
800MHz P3 and even a quad 550MHz box we had no problems, but upgrading
to a dual 1.8GHz AMD box improved build times dramatically but
the vast majority of builds
On Sun, Aug 29, 2004 at 03:49:57PM +1000, David Chatterton wrote:
>There was some discussion back in April regarding problems
>with loaded hyperthreaded machines including thread activation
>errors and other strange problems.
>
>Were these problems identified and resolved, or are they
>still outsta
There was some discussion back in April regarding problems
with loaded hyperthreaded machines including thread activation
errors and other strange problems.
Were these problems identified and resolved, or are they
still outstanding?
Thanks,
David
--
Unsubscribe info: http://cygwin.com/ml/#unsu
> Christopher Faylor wrote:
> > >FYI, the win98 testcase that I reported
> > >(http://cygwin.com/ml/cygwin/2004-07/msg01120.html) locks
> up in the
> > >same way (as the testcase in this thread) on my
> hyperthreaded machine
> > >at work (P4, XPPro), but runs fine fine with HT disabled in BIOS
Christopher Faylor wrote:
>FYI, the win98 testcase that I reported
>(http://cygwin.com/ml/cygwin/2004-07/msg01120.html) locks up in the
>same way (as the testcase in this thread) on my hyperthreaded machine
>at work (P4, XPPro), but runs fine fine with HT disabled in BIOS.
>Maybe seeing what the tw
> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Faylor
> Sent: 05 August 2004 12:31
> On Thu, Aug 05, 2004 at 07:28:26PM +1000, Errol Smith wrote:
> >Christopher Faylor wrote:
> >>For the record I have never doubted that people were reporting real
> >>problems. I doubt
On Thu, Aug 05, 2004 at 07:28:26PM +1000, Errol Smith wrote:
>Christopher Faylor wrote:
>>For the record I have never doubted that people were reporting real
>>problems. I doubt that Corinna has either.
>>
>>No more "me toos" are required here. So, as Larry implied, either
>>debugging of the prob
Christopher Faylor wrote:
>For the record I have never doubted that people were reporting real
>problems. I doubt that Corinna has either.
>
>No more "me toos" are required here. So, as Larry implied, either
>debugging of the problem or the donation of a system is necessary.
FYI, the win98 testc
On Mon, Aug 02, 2004 at 10:59:28AM -0400, Larry Hall wrote:
>At 02:10 PM 7/30/2004, you wrote:
>>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>Larry,
>>
>>this may be a language thing - English is not my native language) -
>>but the script I provided does show the stated behaviour -it pr
At 02:10 PM 7/30/2004, you wrote:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Larry,
>
>this may be a language thing - English is not my native language) -
>but the script I provided does show the stated behaviour -it provides
>enough load in and of itself. As I said, it sometimes fails
At 02:42 PM 7/30/2004, you wrote:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>> Is it fair to assume that you've run the same thing with HT turned
>off and that you don't see the problem?
>
>It is. I cancelled the script the next morning, don't remember the
>number of iterations display
from my fortune cookie jar)
- -Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Friday, July 30, 2004 8:23 PM
To: Volker Bandke; Cygwin List
Subject: [cygwin] Re: cygwin1.dll problem with Hyperthreaded machines
(reprise)
At 02:10 PM 7/30/2004, you wrote:
>
>
At 02:10 PM 7/30/2004, you wrote:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Larry,
>
>this may be a language thing - English is not my native language) -
>but the script I provided does show the stated behaviour -it provides
>enough load in and of itself. As I said, it sometimes fails
al Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf
Of Larry Hall
Sent: Friday, July 30, 2004 7:01 PM
To: Volker Bandke; [EMAIL PROTECTED]
Subject: [cygwin] Re: cygwin1.dll problem with Hyperthreaded machines
(reprise)
At 12:17 PM 7/30/2004, you wrote:
>
>-BEGIN PGP
At 12:17 PM 7/30/2004, you wrote:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>>FWIW, I have a multi-cpu machine and have, in the past, run the
>>supposedly failing tests for days without problem.
>
>On my single-CPU, Hyperthreading machine the error occurs within 30
>minutes, latest, even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>FWIW, I have a multi-cpu machine and have, in the past, run the
>supposedly failing tests for days without problem.
On my single-CPU, Hyperthreading machine the error occurs within 30
minutes, latest, even if no other activity is going on...
On Fri, Jul 30, 2004 at 12:03:16PM -0400, Chuck McDevitt wrote:
>On Fri, Jul 30, 2004 at 11:41:39AM -0400, Chuck McDevitt wrote:
>>I've also been trying to convince my company to donate a hyperthreaded
>>machine to someone on the cygwin project, but so far, management's
>>reaction is "How do we kno
On Fri, Jul 30, 2004 at 11:41:39AM -0400, Chuck McDevitt wrote:
>I've also been trying to convince my company to donate a hyperthreaded
>machine to someone on the cygwin project, but so far, management's
>reaction is "How do we know anyone will work on the problem, even if we
>give them a machine?"
On Fri, Jul 30, 2004 at 11:41:39AM -0400, Chuck McDevitt wrote:
>I've also been trying to convince my company to donate a hyperthreaded
>machine to someone on the cygwin project, but so far, management's
>reaction is "How do we know anyone will work on the problem, even if we
>give them a machine?"
"Volker Bandke" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/30/2004 09:30 AM
To
<[EMAIL PROTECTED]>
cc
Subject
Cygwin1.dll problem with Hyperthreaded machines (reprise)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
This msg relates to an
On Fri, Jul 30, 2004 at 03:30:20PM +0200, Volker Bandke wrote:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Hi everyone,
>
>
>This msg relates to an earlier one at
>
>
>http://sources.redhat.com/ml/cygwin/2004-04/msg00223.html
>
>
>with tit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
This msg relates to an earlier one at
http://sources.redhat.com/ml/cygwin/2004-04/msg00223.html
with title "Cygwin1.dll problem with Hyperthreaded machines"
I have a ASUS P4-P800E DELUXE Motherboard in my P
Did this ever get resolved ? I found this issue in the archives
http://www.cygwin.com/ml/cygwin/2004-04/msg00219.html
but it wasn't clear what ever became of it. I have a simmilar problem on
an HT machine but haven't tried yet to isolate or diagnose.
Thanks.
--
Unsubscribe info: http://cygwin
On Tue, 20 Apr 2004, Brian Ford wrote:
> Here is the stack dump:
BTW, stack traces lately have been showing the return address instead of
the calling one. That makes this trace a bit harder to read.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety
On Fri, 16 Apr 2004, Brian Ford wrote:
> On Fri, 16 Apr 2004, Christopher Faylor wrote:
>
> > On Fri, Apr 16, 2004 at 11:45:50PM +0200, Corinna Vinschen wrote:
> > >On Apr 16 17:03, Chuck McDevitt wrote:
> > >>Has anyone had a chance to try reproducing my problem with Cygwin1.dll
> > >>and Hyperth
PM
Please respond to cygwin
To: [EMAIL PROTECTED]
cc:
Subject: Re: Fw: cygwin1.dll problem with Hyperthreaded
machines.
Please don't do this.
If you screw up in your first attempt to send email here, *please* edit
the message and resend it. Don't f
On Fri, 16 Apr 2004, Christopher Faylor wrote:
> On Fri, Apr 16, 2004 at 11:45:50PM +0200, Corinna Vinschen wrote:
> >On Apr 16 17:03, Chuck McDevitt wrote:
> >>Has anyone had a chance to try reproducing my problem with Cygwin1.dll
> >>and Hyperthreaded machines?
> >
> >I, for one, have no hyperth
Please don't do this.
If you screw up in your first attempt to send email here, *please* edit
the message and resend it. Don't forward it to the list, complete with
email addresses for spam harvesters.
I've never understood why people like to advertise their failed attempts
to send email in this
On Fri, Apr 16, 2004 at 11:45:50PM +0200, Corinna Vinschen wrote:
>On Apr 16 17:03, Chuck McDevitt wrote:
>>Has anyone had a chance to try reproducing my problem with Cygwin1.dll
>>and Hyperthreaded machines?
>
>I, for one, have no hyperthreading machine available.
I have one available but it's no
- Forwarded by Chuck McDevitt/AbInitio on 04/16/2004 07:09 PM -
Chuck McDevitt/AbInitio
04/16/2004 07:01 PM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject:Re: Cygwin1.dll problem with Hyperthreaded
machines
At 05:03 PM 4/16/2004, you wrote:
>Has anyone had a chance to try reproducing my problem with Cygwin1.dll and
>Hyperthreaded machines?
It's on my list but caught behind another dependency. Hopefully, I can
resolve or remove the dependency soon.
--
Larry Hall http
On Apr 16 17:03, Chuck McDevitt wrote:
> Has anyone had a chance to try reproducing my problem with Cygwin1.dll and
> Hyperthreaded machines?
I, for one, have no hyperthreading machine available.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Co-Proj
Has anyone had a chance to try reproducing my problem with Cygwin1.dll and
Hyperthreaded machines?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: ht
Corinna Vinschen <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/07/2004 04:07 AM
Please respond to cygwin
To: Cygwin List <[EMAIL PROTECTED]>
cc:
Subject: Re: Cygwin1.dll problem with Hyperthreaded
machines.
On Apr 6 18:29, Chuck McDevit
On Apr 6 18:29, Chuck McDevitt wrote:
> I upgraded, and it didn't help.
What about the latest developers snapshot from
http://http://www.cygwin.com/snapshots/ ?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developerm
D]>
04/06/2004 05:40 PM
Please respond to Cygwin List
To: Chuck McDevitt <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
cc:
Subject: Re: Cygwin1.dll problem with Hyperthreaded
machines.
At 05:17 PM 4/6/2004, you wrote:
>I've been running into a
At 05:17 PM 4/6/2004, you wrote:
>I've been running into a lot of problems with Cygwin on hyperthreaded
>machines, when those machines are heavily loaded.
>
>For example, if I run this script:
>
>#! /bin/ksh
>mypath=$(pwd)
>while [[ ! -z $mypath ]]
>do
> mypath=$(pwd)
> if [[ -z $mypath ]]
> then
I've been running into a lot of problems with Cygwin on hyperthreaded
machines, when those machines are heavily loaded.
For example, if I run this script:
#! /bin/ksh
mypath=$(pwd)
while [[ ! -z $mypath ]]
do
mypath=$(pwd)
if [[ -z $mypath ]]
then
echo "Test Failed..Path is empty"
fi
44 matches
Mail list logo
