On Thu, Nov 18, 2010 at 03:55:50PM +0530, paritosh chandragupta wrote:
>Hi folks ,
>
>I am hitting the following problem while using gmake :-
>
>617 [exiting thread] gmake 9576 cygthread::stub: erroneous thread
>activation , name is NULL .
>
>Now I am indeed using an old cygwin version and can not
On 11/18/2010 2:25 AM, paritosh chandragupta wrote:
Hi folks ,
I am hitting the following problem while using gmake :-
617 [exiting thread] gmake 9576 cygthread::stub: erroneous thread
activation , name is NULL .
Now I am indeed using an old cygwin version and can not update it due to
dependen
Hi folks ,
I am hitting the following problem while using gmake :-
617 [exiting thread] gmake 9576 cygthread::stub: erroneous thread
activation , name is NULL .
Now I am indeed using an old cygwin version and can not update it due to
dependency issues . Do you have a workaround for this problem
Hi folks ,
I am hitting the following problem while using gmake :-
617 [exiting thread] gmake 9576 cygthread::stub: erroneous thread
activation , name is NULL .
The problem detail is as follows :-
cygwin(dot)com/ml/cygwin/2005-02/msg00303(dot)html
www(dot)cygwin(dot)com/ml/cygwin/2004-04/msg002
Tom Rodman wrote:
On Thu 10/11/07 10:05 CDT Matthew Woehlke wrote:
Tom Rodman wrote:
Is there a way to prove that a given process with more than 1 thread,
is still restricted to just one CPU?
Unless you have manually set affinity, why would this be true? More
likely, only one thread is actuall
On Thu 10/11/07 10:05 CDT Matthew Woehlke wrote:
> Tom Rodman wrote:
> > Is there a way to prove that a given process with more than 1 thread,
> > is still restricted to just one CPU?
>
> Unless you have manually set affinity, why would this be true? More
> likely, only one thread is actually doi
Tom Rodman wrote:
I would guess gzip must run on exactly 1 cpu, at any given time.
If so, then at most, gzip could use 1/8 of the total
CPU resources or 12.5%, as reported by windows task manager,
right? So procps is reporting the percent of the current virtual CPU,
that gzip is using, right?
N
Pls look at the example below (PS1 prompt def shown, and shell
alias/funct defs shown). Notice that gzip is listed as having 3
threads ( 'OurServer109' is a 4 CPU box with hyperthreading on, so
it has 8 virtual CPUs ).
I would guess gzip must run on exactly 1 cpu, at any given time.
I
On Sun, Feb 13, 2005 at 12:09:21PM -0500, Christopher Faylor wrote:
> On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote:
> >Nick Coghlan wrote:
> >Command lines looked like (with thread and file counts filled in): $
> >python /lib/python2.4/test/test_threadedtempfile.py -t -f
> >
> >
>
Christopher Faylor wrote:
On Mon, Feb 14, 2005 at 01:12:53PM +1000, Nick Coghlan wrote:
I can't say for sure if it's a regression, since I never got 1.5.12 to work
properly at all (and hence didn't back up the bin directory before dropping
the snapshot binaries into it). At the moment, I'm curiou
On Mon, Feb 14, 2005 at 01:12:53PM +1000, Nick Coghlan wrote:
>Christopher Faylor wrote:
>>On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote:
>>>Command lines looked like (with thread and file counts filled in):
>>>$ python /lib/python2.4/test/test_threadedtempfile.py -t -f
>>>
>>>
>>I
Christopher Faylor wrote:
On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote:
Command lines looked like (with thread and file counts filled in):
$ python /lib/python2.4/test/test_threadedtempfile.py -t -f
Is this a regression? Was this also problem with 1.5.12?
Unless there are pipes
On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote:
>Nick Coghlan wrote:
>>Christopher Faylor wrote:
>>Of course, I don't actually know if this is a related problem or not.
>>I'm hoping Chris can check it easily, since it happens with the standard
>>Cygwin Python, not just with the vers
Nick Coghlan wrote:
Christopher Faylor wrote:
Of course, I don't actually know if this is a related problem or not.
I'm hoping Chris can check it easily, since it happens with the standard
Cygwin Python, not just with the version I built from Python's current CVS.
I took the obvious step of runni
Christopher Faylor wrote:
To help preserve my tenuous grasp on sanity, please reply to *this
thread* when reporting problems. Please don't start a new thread. Just
reply here so that mailing list threading is preserved and I can easily
check for all success or error reports. As before, any kind
The latest snapshot has my latest try at fixing the dreaded
hyperthreading problem. My previous fix was flawed in that once Corinna
corrected a typo in my change, the problem showed up again.
So, I've reworked the synchronization logic again and even ran cygwin
through that "test su
Christopher Faylor wrote:
I'm not claiming that it is right now. I haven't tried a "make -j" test
yet. I just thought it was time to release another try on the world
again:
http://cygwin.com/snapshots/
To help preserve my tenuous grasp on sanity, please reply to *this
thread* when reporting probl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On my machine my own test case, and the make -j2 test case, have been
running now for more than an hour, no problem so far.
You seem to be on the right track :)
Thanks for your efforts
On Wed, Feb 09, 2005 at 08:47:12PM +, CV wrote:
>Summary:
>
>I reported before that the 20050206 snapshot appeared to fix
>the hyperthreading bug for me.
>
>Now it seems that the next snapshot 20050208 broke it again.
Yes, you're right. It's back. I see
CV wrote:
Rolf Campbell gmail.com> writes:
CV wrote:
after 700 to 1000 files bash hangs with the following error message:
2 [exiting thread] bash 3328 cygthread::stub: erroneous thread
activation, name is NULL
And it appears I spoke too early before. I too, still see a problem:
1424 [exit
Rolf Campbell gmail.com> writes:
> CV wrote:
> > after 700 to 1000 files bash hangs with the following error message:
> > 2 [exiting thread] bash 3328 cygthread::stub: erroneous thread
> > activation, name is NULL
>
> And it appears I spoke too early before. I too, still see a problem:
>
CV wrote:
Summary:
I reported before that the 20050206 snapshot appeared to fix
the hyperthreading bug for me.
Now it seems that the next snapshot 20050208 broke it again.
Result:
---
after 700 to 1000 files bash hangs with the following error message:
2 [exiting thread] bash 3328
Summary:
I reported before that the 20050206 snapshot appeared to fix
the hyperthreading bug for me.
Now it seems that the next snapshot 20050208 broke it again.
Test Case:
--
Command:
find z | while read f; do chown username "$f"; done;
and a longer version of the
On Wed, Feb 09, 2005 at 12:27:34PM -0500, Rolf Campbell wrote:
>Rolf Campbell wrote:
>>This test does fail (in the same way) on non-hyperthreaded machines
>>(Win2000Pro on a PIII). But, this is a regression from 1.5.12 (that
>>test runs fine on the non-HT machine with 1.5.12. There was (maybe
Rolf Campbell wrote:
This test does fail (in the same way) on non-hyperthreaded machines
(Win2000Pro on a PIII). But, this is a regression from 1.5.12 (that
test runs fine on the non-HT machine with 1.5.12. There was (maybe
still is) a problem with running "make -j" without the max task counte
> Fixing that seems to have fixed my hyperthreading
> problems. I have
> > >> run three invocations of the scripts for four days
> without a hiccup.
> > >> Previously, I had problems within minutes.
> > >
> > > Go, you! Someone should give you a gold st
Christopher Faylor wrote:
On Mon, Feb 07, 2005 at 08:17:52AM +0100, Volker Bandke wrote:
Which system configuration did you use to recreate the problem?
I got enough donations to purchase the following:
Motherboard: ASUS P4P800SE
Memory: 1G
CPU: CPU P4/3.0EGHz 800M 478P/1MB HT RT
HD: Samsung 1
On Feb 8 09:31, J?rg Schaible wrote:
> Brian Gallew wrote on Monday, February 07, 2005 2:18 PM:
> > Christopher Faylor wrote:
> >> Fixing that seems to have fixed my hyperthreading problems. I have
> >> run three invocations of the scripts for four days without a hic
Brian Gallew wrote on Monday, February 07, 2005 2:18 PM:
> Christopher Faylor wrote:
>> Fixing that seems to have fixed my hyperthreading problems. I have
>> run three invocations of the scripts for four days without a hiccup.
>> Previously, I had problems within minutes.
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher,
thanks for the explanation (I read, and even understood it) Good
job (Explanation and partial fix).
With kind Regards|\
e-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Faylor
> Sent: Monday, February 07, 2005 2:44 PM
> To: cygwin@cygwin.com
> Subject: Re: hyperthreading fix, try #1
>
> On Mon, Feb 07, 2005 at 08:17:52AM +0100, Volker Bandke wrote:
> >W
Dave Korn wrote:
I thought you meant CGF should be promoted to Sherriff!
Oh no! He's much to mean for being promoted to Sherriff.
Think of the children!
But those gold stars are more then well deserved. Thanks cgf!
Regards
mks
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
P
On Mon, Feb 07, 2005 at 08:17:52AM +0100, Volker Bandke wrote:
>Which system configuration did you use to recreate the problem?
I got enough donations to purchase the following:
Motherboard:ASUS P4P800SE
Memory: 1G
CPU:CPU P4/3.0EGHz 800M 478P/1MB HT RT
HD: Sa
On Mon, 7 Feb 2005, Christopher Faylor wrote:
> On Mon, Feb 07, 2005 at 09:32:09AM -0500, Igor Pechtchanski wrote:
> >On Mon, 7 Feb 2005, Corinna Vinschen wrote:
> >>On Feb 7 08:17, Brian Gallew wrote:
> >>>Christopher Faylor wrote:
> >>>>Fixing that s
> -Original Message-
> From: cygwin-owner On Behalf Of CV
> Sent: 07 February 2005 18:54
> CV hotmail.com> writes:
> > Another vote for the silver star !
>
> Oops, I meant the gold star of course !
>
> Cheers CV
>
I thought you meant CGF should be promoted to Sherriff!
cheers
CV hotmail.com> writes:
> Another vote for the silver star !
Oops, I meant the gold star of course !
Cheers CV
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Christopher Faylor cygwin.com> writes:
> I'm not naive enough to think that I've solved all of the hyperthreading
> problems but I would like people to try today's snapshot (or any
> snapshot newer than today's) and report on whether it solves the problem
> or
Volker Bandke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rolf,
a) Your test case fails on my machine as well, right at the
beginning
b) I seem to remember that there was/is a separate problem with "make
- -j", even on non-hyperthreasd machines. Unfortunately I cannot
search
On Mon, Feb 07, 2005 at 09:32:09AM -0500, Igor Pechtchanski wrote:
>On Mon, 7 Feb 2005, Corinna Vinschen wrote:
>>On Feb 7 08:17, Brian Gallew wrote:
>>>Christopher Faylor wrote:
>>>>Fixing that seems to have fixed my hyperthreading problems. I have run
>>&g
On Mon, 7 Feb 2005, Corinna Vinschen wrote:
> On Feb 7 08:17, Brian Gallew wrote:
> > Christopher Faylor wrote:
> > >Fixing that seems to have fixed my hyperthreading problems. I have run
> > >three invocations of the scripts for four days without a hiccup.
>
On Feb 7 08:17, Brian Gallew wrote:
> Christopher Faylor wrote:
> >Fixing that seems to have fixed my hyperthreading problems. I have run
> >three invocations of the scripts for four days without a hiccup.
> >Previously, I had problems within minutes.
>
> Go, you!
Christopher Faylor wrote:
Fixing that seems to have fixed my hyperthreading problems. I have run
three invocations of the scripts for four days without a hiccup.
Previously, I had problems within minutes.
Go, you! Someone should give you a gold star for this.
--
Unsubscribe info: http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rolf,
a) Your test case fails on my machine as well, right at the
beginning
b) I seem to remember that there was/is a separate problem with "make
- -j", even on non-hyperthreasd machines. Unfortunately I cannot
search the mailing list ri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FWIW, the test case I have been using is now running for 12 ours,
and has done several million iterations. From that point of view the
problem seems to be fixed. Now to run the "real" test case -
building Hercules
Which system configuration did
Christopher Faylor wrote:
[...]
Anyway, I took a look at the pipe handling code for the 457th time and
this time I saw a couple of obvious flaws in my logic. The
synchronization was all off.
Fixing that seems to have fixed my hyperthreading problems. I have run
three invocations of the scripts
On Sun, Feb 06, 2005 at 07:22:48PM +0100, Volker Bandke wrote:
>I have started my test script about half an hour ago, and it is still
>running. It never managed to do that before. This could be a good
>sign. Now, the snapshot DLL is far larger than the standard dll (I
>would ASSume because of de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have started my test script about half an hour ago, and it is still
running. It never managed to do that before. This could be a good
sign. Now, the snapshot DLL is far larger than the standard dll (I
would ASSume because of debug info). Can t
t be the latter since that is
very hard to debug.
Anyway, I took a look at the pipe handling code for the 457th time and
this time I saw a couple of obvious flaws in my logic. The
synchronization was all off.
Fixing that seems to have fixed my hyperthreading problems. I have run
three inv
Christopher Faylor wrote:
However, here is one of the times I repeated that I
don't want to do this over the internet:
[...]
Fixing this problem will be difficult. Dealing with
race conditions like this always is difficult.
Indeed, as an embedded software designer I know this
first hand.
I don't
On Tue, Feb 01, 2005 at 11:01:11PM +0100, Joris van der Sande wrote:
>Larry Hall wrote:
>>Chris has already answered that question earlier in the discussion. He
>>needs physical access to the machine to resolve this problem. Remote
>>access isn't enough.
>
>Forgive my ignorance, but I read the ar
On Tue, 1 Feb 2005, Joris van der Sande wrote:
> Larry Hall wrote:
> > Chris has already answered that question earlier in
> > the discussion. He needs physical access to the
> > machine to resolve this problem. Remote access isn't
> > enough.
>
> Forgive my ignorance, but I read the archives ba
Larry Hall wrote:
Chris has already answered that question earlier in
the discussion. He needs physical access to the
machine to resolve this problem. Remote access isn't
enough.
Forgive my ignorance, but I read the archives back to
1 jan 2004 but found no explanation why remote access
doesn't h
At 07:45 PM 1/30/2005, you wrote:
>The hyperthreading problem reproduces perfectly on my Hush ATX 2.8 GHz P4
>(www.hush-pc.com): building my application fails consistent (within 1 minute)
>with hyperthreading enabled.
>
>Since my machine is on-line 24/7, would it help if I gave
The hyperthreading problem reproduces perfectly on my
Hush ATX 2.8 GHz P4 (www.hush-pc.com): building my
application fails consistent (within 1 minute) with
hyperthreading enabled.
Since my machine is on-line 24/7, would it help if I
gave Christopher (or another motivated developer) remote
On Mon, Jan 24, 2005 at 12:22:19AM -0800, Brian Dessent wrote:
>> - People who've built systems themselves said or implied Yes, by
>> (A) using spare parts along with new CPU, Mobo and Memory, or
>> (B) replacing/upgrading an existing machine, or
>> (C) making
On Mon, Jan 24, 2005 at 12:05:45AM -0800, Mark Geisert wrote:
I don't think you've been paying attention.
>>>
>>>No, I haven't been following this entire thread.
>>
>>Fair enough. Bye, bye.
>
>How old are you?
I'm old enough to have become very tired of messages from ill-informed
(i.e., peopl
Mark Geisert wrote:
> And can one even recover this entire thread from the archive?
When threading is broken it is due to brain-dead email clients. The
archive software requires the presence of either a "References" or
"In-Reply-To" header in order to reconstruct threads. All decent email
progr
I don't think you've been paying attention.
No, I haven't been following this entire thread.
Fair enough. Bye, bye.
How old are you? And can one even recover this entire thread from the
archive?
I don't know why this thread needs to have such emotional content. There
is a
technical problem
On Sun, Jan 23, 2005 at 10:39:07AM -0800, David Christensen wrote:
>Christopher Faylor wrote:
>>I don't think you've been paying attention.
>
>No, I haven't been following this entire thread.
Fair enough. Bye, bye.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem r
Christopher Faylor wrote:
> I don't think you've been paying attention.
No, I haven't been following this entire thread. I've told you what I use and
recommend, and shown that my system demonstrates the Cygwin HT bug. When I
build computers, my goals are reliability first, price/performance sec
lem?
>
>This motherboard, case, and power supply are the core of my desktop
>machine and the machines I build for clients. The 2.4C processor and
>256 MB of RAM represent skimping to get the price down to near $400.00.
>Honestly, if you're going to build a new hyperthreading
e machines I build for clients. The 2.4C processor and 256 MB of RAM
represent skimping to get the price down to near $400.00. Honestly, if you're
going to build a new hyperthreading box for yourself, spend the money to do it
right. You're a developer and power user; time is money. $600
loppy drive, keyboard,
mouse,
and operating system.
Well, yeah. I sort of need a hard disk, though and is that system
*guaranteed* to exhibit this problem?
cgf
I have been able to reproduce this on a variety of machines, the only
common attribute that I noticed has been Hyperthreading itself
(
On Wed, Jan 19, 2005 at 09:16:51PM -0800, David Christensen wrote:
>Christopher Faylor wrote:
>> Hasn't anyone put together a nice $400 system?
>
>How about $417.50?
>
> http://secure.newegg.com/app/WishR.asp?ID=1251752
>
>
>You need to provide the hard drive, CD-ROM drive, floppy drive, key
David Christensen wrote:
Christopher Faylor wrote:
Hasn't anyone put together a nice $400 system?
How about $417.50?
http://secure.newegg.com/app/WishR.asp?ID=1251752
You need to provide the hard drive, CD-ROM drive, floppy drive, keyboard,
mouse,
and operating system.
David
--
Unsubscr
Christopher Faylor wrote:
> Hasn't anyone put together a nice $400 system?
How about $417.50?
http://secure.newegg.com/app/WishR.asp?ID=1251752
You need to provide the hard drive, CD-ROM drive, floppy drive, keyboard, mouse,
and operating system.
David
--
Unsubscribe info: htt
On Thu, Jan 20, 2005 at 12:09:54AM +1000, Nick Coghlan wrote:
>Adrian Cox wrote:
>>On Thu, 2005-01-13 at 19:58 -0500, Christopher Faylor wrote:
>>
>>>This is still pretty far off from the goal but I would still appreciate
>>>it if anyone could recommend a cheap system which demonstrates the
>>>prob
On Thu, Jan 20, 2005 at 12:09:54AM +1000, Nick Coghlan wrote:
>Adrian Cox wrote:
>>On Thu, 2005-01-13 at 19:58 -0500, Christopher Faylor wrote:
>>
>>
>>>This is still pretty far off from the goal but I would still appreciate
>>>it if anyone could recommend a cheap system which demonstrates the
>>>p
Adrian Cox wrote:
On Thu, 2005-01-13 at 19:58 -0500, Christopher Faylor wrote:
This is still pretty far off from the goal but I would still appreciate
it if anyone could recommend a cheap system which demonstrates the
problem. So far, I don't recall anyone giving specific details about a
name bra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Should be more money in the pot now.
The system I am using that demonstrates the problem:
CPU: Intel Pentium 4HT, 3200 MHz (4x800), Northwood Hyperthreading
MoBo: ASUS P4P800-E DeLuxe
Chipset: Intel Springdale i865PE
Speicher: 4x512 MB
On Mon, Jan 17, 2005 at 04:06:52PM -0500, Christopher Faylor wrote:
> On Mon, Jan 17, 2005 at 12:17:52PM -0800, Mark Geisert wrote:
> >If you have by now identified the hardware/OSversion you need to
> >reproduce the problem yourself, please let us know so we can stop
> >annoying you.
>
> I did as
On Mon, Jan 17, 2005 at 12:17:52PM -0800, Mark Geisert wrote:
>If you have by now identified the hardware/OSversion you need to
>reproduce the problem yourself, please let us know so we can stop
>annoying you.
I did ask for people to respond with hardware which shows the problem.
A simple respons
Hi Christopher,
If you have by now identified the hardware/OSversion you need to reproduce
the problem yourself, please let us know so we can stop annoying you. If
that info is not important, please let us know. If you haven't identified
the hw/OS, how will you figure this out without more (ideal
On Mon, Jan 17, 2005 at 12:47:56AM -0800, Mark Geisert wrote:
>Hi, I don't know how additional narrowing-down info about this can be
>posted without sounding like a redundant annoying "me too" but here goes.
>
>I can easily reproduce it on a Dell Workstation PWS360 running WinXP SP1.
>The CPU is a
Hi, I don't know how additional narrowing-down info about this can be
posted without sounding like a redundant annoying "me too" but here goes.
I can easily reproduce it on a Dell Workstation PWS360 running WinXP SP1.
The CPU is a 2.8Ghz Pentium 4, 800MHz FSB. 1GB RAM installed but no more
than 3
On Thu, 2005-01-13 at 19:58 -0500, Christopher Faylor wrote:
> This is still pretty far off from the goal but I would still appreciate
> it if anyone could recommend a cheap system which demonstrates the
> problem. So far, I don't recall anyone giving specific details about a
> name brand compute
On Thu, Jan 13, 2005 at 07:58:32PM -0500, Christopher Faylor wrote:
>So far, the tally for contributions toward purchasing a hyperthreaded
>system is around $175 minus the paypal processing fees.
I somehow forgot a very important part of my message:
THANK YOU to everyone who contributed.
cgf
--
On Mon, Jan 10, 2005 at 05:19:22PM -0500, Christopher Faylor wrote:
>I have, with some misgivings, set up a donations page:
>
>http://cygwin.com/donations.html
>
>This is something that I've wanted to do for a while and, IIRC, I've
>even previously gotten buy-in from other developers and package ma
On Mon, Jan 10, 2005 at 12:20:23PM -0500, Christopher Faylor wrote:
>On Mon, Jan 10, 2005 at 09:53:55AM +0100, Volker Bandke wrote:
>>I really want that "hyperthreading problem" with Cygwin resolved. Does
>>the following suggestion make any sense:
>>
>>(I assu
;tried other variations as well. The system is an SMP system so there
>>should have been a good chance of duplicating the bug. I'm not going
>>to try every variation of this problem when it shows up on the list.
>
>Just a quick observation and a question. Hyperthreading expos
> should have been a good chance of duplicating the bug. I'm not going to
> try every variation of this problem when it shows up on the list.
Just a quick observation and a question. Hyperthreading exposed a race
condition in an NT driver of mine that had run for a long time on an
On Mon, Jan 10, 2005 at 09:53:55AM +0100, Volker Bandke wrote:
>I really want that "hyperthreading problem" with Cygwin resolved. Does
>the following suggestion make any sense:
>
>(I assume cfg is in the US, if not, make the necessary changes)
>
>a: Someone (close by t
I've been on XP for a while but IIRC I was seeing it with hyperthread on 2000.
> -Original Message-
> From: Stéphane Donzé [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 10, 2005 8:41 AM
> To: Mike Marchywka; Volker Bandke; Cygwin
> Subject: RE: Hyperthreading
x27; error.
Regards,
Stephane Donze
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Mike Marchywka
> Sent: lundi 10 janvier 2005 12:42
> To: Volker Bandke; Cygwin
> Subject: RE: Hyperthreading Problem - suggestion
>
>
> This
s likely to delete it and
I've been ignoring most of the cygwin list posts.
Thanks.
> -Original Message-
> From: Volker Bandke [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 10, 2005 3:54 AM
> To: Cygwin
> Subject: Hyperthreading Problem - suggestion
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I really want that "hyperthreading problem" with Cygwin resolved. Does the
following suggestion make any sense:
(I assume cfg is in the US, if not, make the necessary changes)
a: Someone (close by to cfg) demonstrates that the bug/pro
At 04:08 PM 1/1/2005, you wrote:
>Brian Bruns wrote:
>>
>>
>>I think you really really really need to reevaluate what you say
>>before you hit send.
>>
>>The open source/free software developers that I communicate with/work
>>with wrote the stuff they did because they needed an
>>application/librar
Brian Bruns wrote:
If you guys want cygwin to be used by real people, in real life
production or development environments, you should go a bit further
than "I don't have the problem on my computer, so fix it yourself".
If you don't want to or are not able to pay attention to "real
world" bugs, cygw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sitting in Germany makes it difficult for me to physically send you a machine.
What I can do, though, is to virtually hand over the machine to you via the
net. I have an ADSL connection with 3 megabits/sec download and 512
kilobit/sec download
On Tue, Dec 28, 2004 at 05:29:10PM -0800, Brian Dessent wrote:
>Stephane Donze wrote:
>>If you guys want cygwin to be used by real people, in real life
>>production or development environments, you should go a bit further
>>than "I don't have the problem on my computer, so fix it yourself". If
>>y
Stephane Donze wrote:
> If you guys want cygwin to be used by real people, in real life
> production or development environments, you should go a bit further than
> "I don't have the problem on my computer, so fix it yourself". If you
> don't want to or are not able to pay attention to "real world
On Tuesday, December 28, 2004 5:31 PM [EST], Stephane Donze wrote:
> Hi,
>
> Thank you for your reply. You are right, I did not look at the
> code, and I certainly do not pretend to be able to fix this problem.
>
> I am sorry to have to say that, but your message is a very good
> example of the fu
On Tue, Dec 28, 2004 at 11:31:00PM +0100, Stephane Donze wrote:
>I am sorry to have to say that, but your message is a very good example
>of the fundamental difference between a project that is useable and
>reliable, and a project that "almost works" and will never do more that
>that.
>
>[snip]
> If you guys want cygwin to be used by real people, in real life
> production or development environments, you should go a bit
> further than
> "I don't have the problem on my computer, so fix it yourself".
OK. So, if he's unable to reproduce the problem, you want him
to... do what? Make ran
> multiprocessor machines and nobody seems to care about it. You cannot
> just expect people to "wait until you someday have a system
> that shows
> the problem" everytime they encounter a bug.
Actually since Cygwin is a free project this is a reasonable
expectation. If you want this fixed send
(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
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" re
Hi,
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 hype
Hi,
It would have saved me some irritation over the last few days if the Cygwin FAQ
mentioned that there are some unresolved issues with running on hyperthreaded
processors.
The first thing I did when I encountered problems was check the FAQ - since
hyperthreading wasn't mentioned, I init
04 05:11 PM
Please respond to
[EMAIL PROTECTED]
To
Pablo Ruiz Garcia <[EMAIL PROTECTED]>
cc
[EMAIL PROTECTED]
Subject
Re: HyperThreading
On Wed, 27 Oct 2004, Pablo Ruiz Garcia wrote:
> - Original Message -
> From: "Brian Ford"
> To: "Pablo Ruiz Garc
1 - 100 of 107 matches
Mail list logo
