20050208 snapshot = yay! (Was: Re: hyperthreading fix, try #1)
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 counter, but make -j2 has always worked very well on non-ht machines. I will try out some other snapshots and see if I can narrow down the time when this showed up later today. -Rolf I've tried yesterday's snapshot with my test-case, and with my real build system. So far, things look very good. -Rolf -- 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/
Re: 20050208 snapshot = yay! (Was: Re: hyperthreading fix, try #1)
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 still is) a problem with running make -j without the max task counter, but make -j2 has always worked very well on non-ht machines. I will try out some other snapshots and see if I can narrow down the time when this showed up later today. -Rolf I've tried yesterday's snapshot with my test-case, and with my real build system. So far, things look very good. If that's the case, then you can thank Corinna. She found a bug in my code. In my defense, however, causing the problem required her to go to the tremdous effort of running something that she called a cygwin test suite. Duh. 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/
RE: hyperthreading fix, try #1
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. Go, you! Someone should give you a gold star for this. IMHO Chris needs more something like a life-time award :) - Jörg -- 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/
Re: hyperthreading fix, try #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 hiccup. Previously, I had problems within minutes. Go, you! Someone should give you a gold star for this. IMHO Chris needs more something like a life-time award :) We could ask the Queen to bestow the OM upon Chris. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/
RE: hyperthreading fix, try #1
-Original Message- From: cygwin-owner On Behalf Of Corinna Vinschen Sent: 08 February 2005 08:48 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 hiccup. Previously, I had problems within minutes. Go, you! Someone should give you a gold star for this. IMHO Chris needs more something like a life-time award :) We could ask the Queen to bestow the OM upon Chris. We could ask the Buddha to bestow the AUM upon him too! cheers, DaveK -- Can't think of a witty .sigline today -- 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/
Re: hyperthreading fix, try #1
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://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: hyperthreading fix, try #1
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! Someone should give you a gold star for this. Igor? Ready to polish a gold star for cgf? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/
Re: hyperthreading fix, try #1
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. Previously, I had problems within minutes. Go, you! Someone should give you a gold star for this. Igor? Ready to polish a gold star for cgf? Always. Regular ones I have a-plenty, just don't ask me for the flashing ones. ;-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/
Re: hyperthreading fix, try #1
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 the mailing list right now due to some error (that possibly has to do with cygwin.com's earlier breakdown. I do remember a sentence somewhere like We don't recommend that you use 'make -j' as it seems to be broken c) Running your testcase with '-j1' instead of '-j2' does not fail on my machine Thanks for you info Volker. Here's what I've figured out: 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 counter, but make -j2 has always worked very well on non-ht machines. I will try out some other snapshots and see if I can narrow down the time when this showed up later today. -Rolf -- 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/
Re: hyperthreading fix, try #1
Christopher Faylor cgf-no-personal-reply-please at 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 not. If it doesn't, please provide as simple a test case as possible so that I can duplicate the problem. Working well here: HP Pavilion with P4HT3.2G. I only ran into the hyperthreading bug the other day when trying to chown a large directory tree. It would bomb out after a minute or two (a few hundred to maybe a thousand files). With the new build (whether stripped with --strip-debug or unstripped) the command completes as expected. Another vote for the silver star ! Cheers CV -- 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/
Re: hyperthreading fix, try #1
CV or254498 at 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: http://cygwin.com/faq/
RE: hyperthreading fix, try #1
-Original Message- From: cygwin-owner On Behalf Of CV Sent: 07 February 2005 18:54 CV or254498 at 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, DaveK -- Can't think of a witty .sigline today -- 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/
Re: hyperthreading fix, try #1
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 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. Igor? Ready to polish a gold star for cgf? Always. Regular ones I have a-plenty, just don't ask me for the flashing ones. ;-) Let's wait until a fix has been fully confirmed. That hasn't happened yet. http://cygwin.com/ml/cygwin/2005-02/msg00147.html and http://cygwin.com/ml/cygwin/2005-02/msg00172.html look like confirmations to me. Besides, if you get one gold star per fixed bug they will all be well-deserved. :-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/
Re: hyperthreading fix, try #1
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 120GB Case: ASPIRE XINFINITY BL 350W RTL I purchased this from Newegg. I love that company. I put the system together in one night, turned it on, and it worked. All of the lights came on correctly, the system booted with a CD, and transferring data from my old system proceeded without a hitch, thanks to my knoppix CD -- love that knoppix, too. The one thing that took me forever to fix was getting XP running. Somehow my XP CD got cracked with a big chunk taken out of it, so I had to get a new CD, and I ended up transferring data from my old system multiple times as I attempted to install the new CD without overwriting all of my existing data. The way I usually do this is to copy raw partitions over, since my windows box is multi-boot and represents years of work. Sometimes the OS figures out how to reconfigure itself, sometimes it needs a nudge. In this case, it needed to be whacked with a large branch. I couldn't get W2K working but I've held off further investigations in that for another time. also, can you describe (in _short_ terms) the cause of the error? Cygwin has a problem because normal pipe I/O on windows is not interruptible (generically speaking - you could kludge it on NT). So, to work around this problem, it starts up pipe i/o in a thread and kills the thread when a signal comes in. It's a sledge hammer approach to interrupting pipe I/O. The pipe thread uses a synchronization event to tell the initiating reader when the pipe is all set, has grabbed its arguments and is ready to go. This event was also used to tell the reader that there was a successful read. Previous to my fix, cygwin did not reliably wait for both events to happen so, after the first read on a pipe, it would become out of sync. This would present a problem on any kind of SMP-like system but it wouldn't be as noticeable on a non-SMP system. Once I ran the test case twenty times or so, I went back and looked at the code I'd previously stared at for hours and saw a few synchronization issues. For once the back trace from gdb showed that something was clearly amiss. So, the fix was to try much harder to ensure that we've correctly waited for notification events, even in the scenario when cygwin thinks it has to terminate a thread due to the arrival of a signal. It is possible that the read has completed in that case and cygwin should not throw the data away since the read really *wasn't* terminated by a signal. Unfortunately, there is still a race here. I have an idea about how to fix the race but it would introduce a destabilizing change that I'd rather not chance before 1.5.13 is released. Given that I can't reproduce the problem with the test script anymore, I think I'll release cygwin with this change plus any other potential fixes required to handle the make -j 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/
Re: hyperthreading fix, try #1
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 Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: hyperthreading fix, try #1
Um... I say Gold Star for this explanation alone, which somehow is completely free from any hint of sarcasm, WJMness, and passive aggression. Bad day Chris? ;-) Oh, and double-gold stars to any and all who coughed up the dough. -- Gary R. Van Sickle -Original Message- 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: 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 120GB Case: ASPIRE XINFINITY BL 350W RTL I purchased this from Newegg. I love that company. I put the system together in one night, turned it on, and it worked. All of the lights came on correctly, the system booted with a CD, and transferring data from my old system proceeded without a hitch, thanks to my knoppix CD -- love that knoppix, too. The one thing that took me forever to fix was getting XP running. Somehow my XP CD got cracked with a big chunk taken out of it, so I had to get a new CD, and I ended up transferring data from my old system multiple times as I attempted to install the new CD without overwriting all of my existing data. The way I usually do this is to copy raw partitions over, since my windows box is multi-boot and represents years of work. Sometimes the OS figures out how to reconfigure itself, sometimes it needs a nudge. In this case, it needed to be whacked with a large branch. I couldn't get W2K working but I've held off further investigations in that for another time. also, can you describe (in _short_ terms) the cause of the error? Cygwin has a problem because normal pipe I/O on windows is not interruptible (generically speaking - you could kludge it on NT). So, to work around this problem, it starts up pipe i/o in a thread and kills the thread when a signal comes in. It's a sledge hammer approach to interrupting pipe I/O. The pipe thread uses a synchronization event to tell the initiating reader when the pipe is all set, has grabbed its arguments and is ready to go. This event was also used to tell the reader that there was a successful read. Previous to my fix, cygwin did not reliably wait for both events to happen so, after the first read on a pipe, it would become out of sync. This would present a problem on any kind of SMP-like system but it wouldn't be as noticeable on a non-SMP system. Once I ran the test case twenty times or so, I went back and looked at the code I'd previously stared at for hours and saw a few synchronization issues. For once the back trace from gdb showed that something was clearly amiss. So, the fix was to try much harder to ensure that we've correctly waited for notification events, even in the scenario when cygwin thinks it has to terminate a thread due to the arrival of a signal. It is possible that the read has completed in that case and cygwin should not throw the data away since the read really *wasn't* terminated by a signal. Unfortunately, there is still a race here. I have an idea about how to fix the race but it would introduce a destabilizing change that I'd rather not chance before 1.5.13 is released. Given that I can't reproduce the problem with the test script anymore, I think I'll release cygwin with this change plus any other potential fixes required to handle the make -j 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/ -- 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/
RE: hyperthreading fix, try #1
-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|\ _,,,---,,_ ZZZzz /,`.-'`'-. ;-;;, Volker Bandke |,4- ) )-,_. ,\ ( `'-' (BSP GmbH)'---''(_/--' `-'\_) It is easier for a camel to pass through the eye of a needle if it is lightly greased. -- Kehlog Albran, The Profit (Another Wisdom from my fortune cookie jar) -BEGIN PGP SIGNATURE- Version: PGP 8.0.1 iQA/AwUBQghuWh5trGyhAF0wEQJd0QCeK2FJNuk6z0zogcKLd5rJv75tmWMAn3ZT XV7i3W4/0DjRAss0uJ2BqTf4 =xKB+ -END PGP SIGNATURE- -- 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/
RE: hyperthreading fix, try #1
-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 the debugging info/additional baggage that is being carried around influence the normal runtime behaviour? Should I run strip against the snapshot DLL and rerun my test? With kind Regards|\ _,,,---,,_ ZZZzz /,`.-'`'-. ;-;;, Volker Bandke |,4- ) )-,_. ,\ ( `'-' (BSP GmbH)'---''(_/--' `-'\_) Steinbach's Guideline for Systems Programming: Never test for an error condition you don't know how to handle. (Another Wisdom from my fortune cookie jar) -BEGIN PGP SIGNATURE- Version: PGP 8.0.1 iQA/AwUBQgZgdx5trGyhAF0wEQKc5QCg51wnZdW5KOEQDiqtplfglygArXAAoJeH D4bXQSMUfTHe58WMpuIs1M96 =pPmL -END PGP SIGNATURE- -- 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/
Re: hyperthreading fix, try #1
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 debug info). Can the debugging info/additional baggage that is being carried around influence the normal runtime behaviour? Should I run strip against the snapshot DLL and rerun my test? I've been building snapshots with debugging turned on lately, yes. I don't think it is possible for this to impact this problem. I certainly saw it with a non-stripped DLL. However, in the interests of science, it probably would be a good idea to strip the DLL and try again if you have time. 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/
Re: hyperthreading fix, try #1
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 for four days without a hiccup.
Previously, I had problems within minutes.
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 not. If it doesn't, please provide as simple a test case as possible
so that I can duplicate the problem.
Using the new snapshot (Feb 6th), the problem is still present, and in
fact, occurs much more quickly and reliably on my system. This is a
modified test case from my original report. Just put makefile and t.sh
in the same dir, run ./t.sh. On my 2.8GHz HT P4, it locks up within
the first second very consistantly. My output look like this:
==output===
$ ./t.sh
Loop 1
: Begin 0.pp 1
: Begin 1.pp 1
$ ./t.sh
: Begin 0.pp
: Begin 1.pp
CYGWIN_NT-5.1
SHELL = /bin/sh
testuname: 0.pp 1.pp 2.pp 3.pp 4.pp 5.pp 6.pp 7.pp 8.pp 9.pp 10.pp 11.pp 12.pp
13.pp 14.pp 15.pp 16.pp 17.pp 18.pp 19.pp 20.pp 21.pp 22.pp 23.pp 24.pp 25.pp
26.pp 27.pp 28.pp 29.pp 30.pp 31.pp 32.pp 33.pp 34.pp 35.pp 36.pp 37.pp 38.pp
39.pp 40.pp 41.pp 42.pp 43.pp 44.pp 45.pp 46.pp 47.pp 48.pp 49.pp 50.pp 51.pp
52.pp 53.pp 54.pp 55.pp 56.pp 57.pp 58.pp 59.pp 60.pp 61.pp 62.pp 63.pp 64.pp
65.pp 66.pp 67.pp 68.pp 69.pp 70.pp 71.pp 72.pp 73.pp 74.pp 75.pp 76.pp 77.pp
78.pp 79.pp 80.pp 81.pp 82.pp 83.pp 84.pp 85.pp 86.pp 87.pp 88.pp 89.pp 90.pp
91.pp 92.pp 93.pp 94.pp 95.pp 96.pp 97.pp 98.pp 99.pp 100.pp 101.pp 102.pp
103.pp 104.pp 105.pp 106.pp 107.pp 108.pp 109.pp 110.pp 111.pp 112.pp 113.pp
114.pp 115.pp 116.pp 117.pp 118.pp 119.pp 120.pp 121.pp 122.pp 123.pp 124.pp
125.pp 126.pp 127.pp 128.pp 129.pp 130.pp 131.pp 132.pp 133.pp 134.pp 135.pp
136.pp 137.pp 138.pp 139.pp 140.pp 141.pp 142.pp 143.pp 144.pp 145.pp 146.pp
147.pp 148.pp 149.pp 150.pp 151.pp 152.pp 153.pp 154.pp 155.pp 156.pp 157.pp
158.pp 159.pp 160.pp 161.pp 162.pp 163.pp 164.pp 165.pp 166.pp 167.pp 168.pp
169.pp 170.pp 171.pp 172.pp 173.pp 174.pp 175.pp 176.pp 177.pp 178.pp 179.pp
180.pp 181.pp 182.pp 183.pp 184.pp 185.pp 186.pp 187.pp 188.pp 189.pp 190.pp
191.pp 192.pp 193.pp 194.pp 195.pp 196.pp 197.pp 198.pp 199.pp 200.pp 201.pp
202.pp 203.pp 204.pp 205.pp 206.pp 207.pp 208.pp 209.pp 210.pp 211.pp 212.pp
213.pp 214.pp 215.pp 216.pp 217.pp 218.pp 219.pp 220.pp 221.pp 222.pp 223.pp
224.pp 225.pp 226.pp 227.pp 228.pp 229.pp 230.pp 231.pp 232.pp 233.pp 234.pp
235.pp 236.pp 237.pp 238.pp 239.pp 240.pp 241.pp 242.pp 243.pp 244.pp 245.pp
246.pp 247.pp 248.pp 249.pp 250.pp 251.pp 252.pp 253.pp 254.pp 255.pp 256.pp
257.pp 258.pp 259.pp 260.pp 261.pp 262.pp 263.pp 264.pp 265.pp 266.pp 267.pp
268.pp 269.pp 270.pp 271.pp 272.pp 273.pp 274.pp 275.pp 276.pp 277.pp 278.pp
279.pp 280.pp 281.pp 282.pp 283.pp 284.pp 285.pp 286.pp 287.pp 288.pp 289.pp
290.pp 291.pp 292.pp 293.pp 294.pp 295.pp 296.pp 297.pp 298.pp 299.pp 300.pp
%.pp::
: Begin $@ ${C}
@uname
: End $@ ${C}
#!/bin/bash
while true; do
make -rRj2
C=$(($C+1))
done
Cygwin Configuration Diagnostics
Current System Time: Mon Feb 07 00:59:22 2005
Windows XP Professional Ver 5.1 Build 2600 Service Pack 2
Path: C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\cygwin\usr\X11R6\bin
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\Program
Output from C:\cygwin\bin\id.exe (nontsec)
UID: 11643(rcampbell)GID: 10513(Domain Users)
10513(Domain Users)
Output from C:\cygwin\bin\id.exe (ntsec)
UID: 11643(rcampbell)GID: 10513(Domain Users)
544(Administrators) 545(Users) 10513(Domain Users)
SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS
HOME = `C:\cygwin\home\rcampbell'
MAKE_MODE = `unix'
PWD = `/tmp/make'
USER = `rcampbell'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\rcampbell\Application Data'
COLORFGBG = `0;default;15'
COLORTERM = `rxvt-xpm'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `DESK-RCAMPBELL2'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
COSMIC = `t'
CVS_RSH = `/bin/ssh'
DISPLAY = `:0'
FP_NO_HOST_CHECK = `NO'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\rcampbell'
HOSTNAME = `desk-rcampbell2'
INFOPATH =
`/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:'
LOGONSERVER = `\\EXCHANGE'
MANPATH =
`/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man'
NUMBER_OF_PROCESSORS = `2'
OLDPWD = `/home/rcampbell'
OS = `Windows_NT'
P4CONFIG = `.p4config'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PRINTER = `135MC-4th on SPOOLER (from PCRCAMPBELL3)'
RE: hyperthreading fix, try #1
-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 you use to recreate the problem? And also, can you describe (in _short_ terms) the cause of the error? With kind Regards|\ _,,,---,,_ ZZZzz /,`.-'`'-. ;-;;, Volker Bandke |,4- ) )-,_. ,\ ( `'-' (BSP GmbH)'---''(_/--' `-'\_) An ounce of application is worth a ton of abstraction. (Another Wisdom from my fortune cookie jar) -BEGIN PGP SIGNATURE- Version: PGP 8.0.1 iQA/AwUBQgcWIB5trGyhAF0wEQI+GQCfSnofdphyi5TRlWO8G18zUui5QesAoOMt I/0glQ56wlb3qTTgU4hh5DmM =mLgN -END PGP SIGNATURE- -- 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/
RE: hyperthreading fix, try #1
-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 right now due to some error (that possibly has to do with cygwin.com's earlier breakdown. I do remember a sentence somewhere like We don't recommend that you use 'make -j' as it seems to be broken c) Running your testcase with '-j1' instead of '-j2' does not fail on my machine With kind Regards|\ _,,,---,,_ ZZZzz /,`.-'`'-. ;-;;, Volker Bandke |,4- ) )-,_. ,\ ( `'-' (BSP GmbH)'---''(_/--' `-'\_) Hidden I/O Functions instructions: SCL SET CURSER TO LOUD (Another Wisdom from my fortune cookie jar) -BEGIN PGP SIGNATURE- Version: PGP 8.0.1 iQA/AwUBQgcbZB5trGyhAF0wEQISUwCfQqCl5HAa7QjMMkrtJp8uzek1CCkAn3NJ 43wgJOBeQRchfoSz7h/dNGsn =AJOY -END PGP SIGNATURE- -- 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/
