I have a dual Xeon 2687W workstation and it appears TThrottle cannot handle this many cores. During initialization TThrottle just retries and retries to determine number of cores. Is this expected? Do you plan to support 16 physical cores? I am a "paying" member :D
Quote from: ChrisSibbald on July 05, 2012, 11:52:03 PM
I have a dual Xeon 2687W workstation and it appears TThrottle cannot handle this many cores. During initialization TThrottle just retries and retries to determine number of cores. Is this expected? Do you plan to support 16 physical cores? I am a "paying" member :D
TThrottle should be able to handle 12 Temp cores, that's 24 cores, should be enough for now.
Do you use the latest Beta version? If not do so, it fixed these sort of problems.
If the problems remain, I need the LATEST log file from here: C:\Users\username\AppData\Roaming\eFMer\TThrottle\log.
You can email the log, because it's a bit long.
If for some reason the log is empty:
In TThrottle.xml (C:\Program Files\eFMer\TThrottle). If the file isn't there copy it from the example folder.
Make sure:
file is set to 1:
<logging>
<file>1</file>
<email>0</email>
</logging>
Thanks for the Speedy response Fred. I will try the beta version and let you know how I make out.
HI Fred,
No luck with Beta. Same behavior, calibration keeps restarting. Where can I find the email address to send you the log file?
Quote from: ChrisSibbald on July 06, 2012, 11:16:16 AM
HI Fred,
No luck with Beta. Same behavior, calibration keeps restarting. Where can I find the email address to send you the log file?
Got you logs. Need everything from the log tab as well to see what's going on. (after TThrottle startup)
Thanks Fred. Here is the text of the log from the TThrottle UI. Let me know if there is anything else I can do to help.
----------------log-------------------
06 July 2012 - 13:05:58 Driver installed properly. Driver Version: 2.3
06 July 2012 - 13:05:58 Driver regulator: active
Program version: 5.70 64Bit
Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
Language: User: 1033 ENU ,System: 1033 ENU
nvidia: found 2 logical devices
nvidia: found 2 physical devices
nvidia: Temperature 58 °C, max Temperature 127 °C
nvidia: Temperature 60 °C, max Temperature 127 °C
nvidia: GeForce GTX 580, GeForce GTX 580
Vendor ID: GenuineIntel
Vendor: INTEL
HighestIntegerValue: 0000000D - Processor Signature: 000206D7
Misc. info: 02200800
Feature Flags1 1FBEE3FF
Feature Flags2 BFEBFBFF
Processor: Intel(R) Xeon(R) CPU E5-2687W 0 @ 3.10GHz
Processor: Family: 6h, Model: 2D, Stepping: 7
TJunction read from CPU: 92 °C, TJunction using: 92 °C
Core Temperature: 54 °C, Raw Data: 88260000
882b0000,882b0000,882a0000,882a0000,882d0000,882d0000,882d0000,882d0000,
882e0000,882e0000,88290000,88290000,882b0000,882b0000,882c0000,882c0000,
88220000,88220000,88240000,88240000,88270000,88270000,882a0000,882a0000,
This Processor has 16 cores and 8 temperature sensors.
BOINC:
lhcathome2.cern.ch_test4theory
lhcathomeclassic.cern.ch_sixtrack
setiathome.berkeley.edu
www.worldcommunitygrid.org
You can help by reading www.efmer.eu/boinc/faq.html How can I help!
Select the send EMail button,or copy everything in this logging window and mail it to me!
boinc[At]efmer[Dot]eu. We use this information to improve this product.
Quote from: ChrisSibbald on July 06, 2012, 09:46:35 PM
This Processor has 16 cores and 8 temperature sensors.
This indicates that the calibration has succeeded.
As always 1 sensor / 1 core = 2 shared cores.
Does the calibration dialog still pop up?
Hi Fred,
The calibration dialog continuously popped up. I let it run for quite some time (many popups) then killed TThrottle. I will try again and be more patient.
Hi Fred
No luck. The calibration dialog keeps popping up. As soon as the progress bar gets to 100% TThrottle either exits/restarts or simply minimizes to task bar and the calibration restarts. Here is the content of the log from the UI. I noted that CPU 2 is showing up as XXX...perhaps that has something to do with it. I will also email you the log file.
----------------UI log--------------
Number of matching Programs (Processes): 19
CPU:1 (18%) - PID:328344 (4) Slot:17 http://www.worldcommunitygrid.org/ CMD2_2541-1HCI_A.clustersOccur-3BJI_A.clustersOccur_726
CPU:1 (14%) - PID:326968 (4) Slot:18 http://www.worldcommunitygrid.org/ CMD2_2541-1HCI_A.clustersOccur-3BJI_A.clustersOccur_620
CPU:1 (12%) - PID:204664 (4) Slot:27 http://www.worldcommunitygrid.org/ CMD2_2541-1HCI_A.clustersOccur-3BJI_A.clustersOccur_676
CPU:1 (8%) - PID:175288 (3) Slot:28 http://www.worldcommunitygrid.org/ qf530_00071
CPU:1 (2%) - PID:186276 (3) Slot:20 http://www.worldcommunitygrid.org/ qf530_00039
CPU:1 (1%) - PID:205636 (3) Slot:29 http://www.worldcommunitygrid.org/ HFCC_target-9_01354412_target-9_0000
CPU:1 (5%) - PID:223692 (3) Slot:9 http://www.worldcommunitygrid.org/ DSFL_000090-1_0000010_0206
CPU:1, GPU:0, PID:338072 (2) Child: wcgrid_dsfl_vina_prod_x86.exe.6.25
XXX: 0 (0%) - PID:240556 (3) Slot:12 http://www.worldcommunitygrid.org/ faah34564_ZINC24193330_xJ1_xtal_00
XXX: 0 (0%) - PID:249672 (3) Slot:19 http://www.worldcommunitygrid.org/ GFAM_x3bpmB_PfFP3_0029538_0140
CPU:1, GPU:0, PID:329808 (2) Child: wcgrid_gfam_vina_prod_x86.exe.6.12
XXX: 0 (0%) - PID:326408 (3) Slot:24 http://www.worldcommunitygrid.org/ faah34564_ZINC27675489_xJ1_xtal_00
XXX: 0 (0%) - PID:312588 (3) Slot:6 http://www.worldcommunitygrid.org/ SN2S_2X8L_1000195_0945
CPU:1, GPU:0, PID:336648 (2) Child: wcgrid_sn2s_vina_prod_x86.exe.6.20
XXX: 0 (0%) - PID:299780 (3) Slot:3 http://www.worldcommunitygrid.org/ faah34570_ZINC09339383_xJ1_xtal_01
XXX: 0 (0%) - PID:274052 (3) Slot:1 http://www.worldcommunitygrid.org/ c4cw_target06_074537065
XXX: 0 (0%) - PID:324340 (3) Slot:5 http://www.worldcommunitygrid.org/ faah34570_ZINC09090403_xJ1_xtal_04
XXX: 0 (0%) - PID:326532 (3) Slot:10 http://www.worldcommunitygrid.org/ c4cw_target06_074538411
XXX: 0 (0%) - PID:327184 (3) Slot:25 http://www.worldcommunitygrid.org/ DSFL_000090-1_0000023_0227
CPU:1, GPU:0, PID:338860 (2) Child: wcgrid_dsfl_vina_prod_x86.exe.6.25
XXX: 0 (0%) - PID:240532 (3) Slot:16 http://www.worldcommunitygrid.org/ GFAM_x3bpmB_PfFP3_0029595_0225
CPU:1, GPU:0, PID:332852 (2) Child: wcgrid_gfam_vina_prod_x86.exe.6.12
XXX: 0 (0%) - PID:328076 (3) Slot:13 http://www.worldcommunitygrid.org/ DSFL_000090-1_0000024_0235
CPU:1, GPU:0, PID:334896 (2) Child: wcgrid_dsfl_vina_prod_x86.exe.6.25
XXX: 0 (0%) - PID:328196 (4) Slot:21 http://www.worldcommunitygrid.org/ CMD2_2541-2QZU_A.clustersOccur-3BIY_A.clustersOccur_8
XXX: 0 (0%) - PID:326040 (3) Slot:8 http://www.worldcommunitygrid.org/ X0900065551380200603231443
XXX: 0 (0%) - PID:124388 (3) Slot:4 http://www.worldcommunitygrid.org/ SN2S_2X8L_1000195_0829
CPU:1, GPU:0, PID:339228 (1) Child: wcgrid_sn2s_vina_prod_x86.exe.6.20
XXX: 0 (0%) - PID:326228 (3) Slot:30 http://lhcathome2.cern.ch/test4theory/ uc_1340953163_41242
GPU:1 0 PID:335708 (5) Slot:15 http://setiathome.berkeley.edu/ 28jn10ab.6881.16022.12.10.50
GPU:1 0 PID:336248 (5) Slot:2 http://setiathome.berkeley.edu/ 20au10af.5841.124908.14.10.241
GPU:1 0 PID:334448 (5) Slot:7 http://setiathome.berkeley.edu/ 01jl10aa.26205.23986.3.10.97
GPU:1 0 PID:334584 (5) Slot:0 http://setiathome.berkeley.edu/ 01jl10aa.26205.23986.3.10.46
GPU:1 0 PID:338868 (5) Slot:11 http://setiathome.berkeley.edu/ 01jl10aa.26205.23986.3.10.117
GPU:1 0 PID:338912 (5) Slot:14 http://setiathome.berkeley.edu/ 01jl10aa.26205.23986.3.10.115
----------------------------------------------------------------------------------------------------------------------------------------------
One other data point...
I ran this box for a while with only one CPU and TThrottle ran fine with one Xeon E5-2687W. When I added the second CPU I started having these issues.
Quote from: ChrisSibbald on July 07, 2012, 01:22:06 PM
One other data point...
I ran this box for a while with only one CPU and TThrottle ran fine with one Xeon E5-2687W. When I added the second CPU I started having these issues.
OK, this should be enough for some testing or a test build.
Close down TThrottle
Remove the logs from: C:\Users\fred\AppData\Roaming\eFMer\TThrottle\log
Unzip and move the exe to C:\Program Files\eFMer\TThrottle
http://www.efmer.eu/download/boinc/boinc_tasks/unified/TThrottle64_570_test.zip (http://www.efmer.eu/download/boinc/boinc_tasks/unified/TThrottle64_570_test.zip)
Start TThrottle and wait until the calibration finished.
I like to see the logging in: C:\Users\fred\AppData\Roaming\eFMer\TThrottle\log
Fire up regedit.exe and check the keys in HKEY_CURRENT_USER\Software\eFMer\TThrottle64\calibration
Give me core_delta (2) and cores (16).
Thanks Fred. Just sent you an email with the log and screenshot of registry keys.
First Time Processor Check complete, TThrottle restarts and does First time processor check, repeats. I let it try 5 times then used task manager to kill TThrottle.
Quote from: ChrisSibbald on July 05, 2012, 11:52:03 PM
I have a dual Xeon 2687W workstation and it appears TThrottle cannot handle this many cores. During initialization TThrottle just retries and retries to determine number of cores. Is this expected? Do you plan to support 16 physical cores? :D
OK, now I see it, the CPU has 16 Threads *2 = 32 Threads and that's more than this version supports right now (24).
Let's see what I can do, this is a lot more work. Because it involves the graphs as well and BoincTasks. :-X
Thanks Fred. I would really appreciate it if you can support 32 threads.
PS. I will definitely make another donation if you get this working :D
Quote from: ChrisSibbald on July 09, 2012, 05:57:19 PM
PS. I will definitely make another donation if you get this working :D
Aha a bribe. :o
Usually one of the best motivators :D
I'm working on the 32 cores. Got the driver updated, now the rest of the program
You are a gentleman and a scholar. :D Thanks Fred.
Quote from: ChrisSibbald on July 14, 2012, 01:22:55 PM
You are a gentleman and a scholar. :D Thanks Fred.
Running in test....
Quote from: fred on July 14, 2012, 01:39:38 PM
Running in test....
It's working on my I7 X64, but it crashed on a 32 bit Win7 with a blue screen. :o
Every small error in a driver causes instant death.
Now backtracking step for step what is going on. Driver testing at this point is difficult to say the least.
And of course the 64 and 32 bit drivers are not compatible.
Testing, testing.
Here it is.
Before you install this new version, please run the "old" version as administrator and remove the check at "Run TThrottle at login".
Next test this one: http://www.efmer.com//download/boinc/tthrottle/unified/setup_32_64_tthrottle_5_8_0.exe (http://www.efmer.com//download/boinc/tthrottle/unified/setup_32_64_tthrottle_5_8_0.exe)
AMD is untested.
All testers:
Set the "Debug" check in the log tab.
Restart TThrottle and send me the log.
Hi Fred
I am still experiencing the issue whereby the "First time processor check" ends then restarts. I sent you an email with the log file from the UI and the log file from the AppData folder.
Getting closer I think.
Let me know what I can do to help.
Cheers,
Chris
Try this:
Exit TThrottle;
Regedit.exe
Go to:
HKEY_CURRENT_USER\Software\eFMer\TThrottle\calibration
Change the value cores into 20 hex or 32 dec.
Start TThrottle.
A new build 5.8.0, see line in previous post.
Before you install it, go to: C:\Program Files\eFMer\TThrottle and delete TThrottle64.exe or TThrottle.exe.
Run the installer.
Check on the TThrottle64.exe properties->Details the date should be 18-7-2012 13:23 Just to make sure you don't get a version from the browser cache.
Hi Fred, using the build from July 16 (5.8) and updating the registry settings all appears to work fine! Thank you. I am very impressed with how quickly you turned this enhancement request around. A donation is forthcoming :D
Quote from: ChrisSibbald on July 18, 2012, 12:11:24 PM
Hi Fred, using the build from July 16 (5.8) and updating the registry settings all appears to work fine! Thank you. I am very impressed with how quickly you turned this enhancement request around. A donation is forthcoming :D
Yes. 8)
Just to make sure press the Recalibrate button in the expert tab. To see if that works OK.
After that I like to see the log again with the "debug" check enabled.
Because your log was missing a number of cores last time. :o Let's see if they are there.
hmmm...bummer. When I recalibrate it got in that loop of "First time processor check" again. I will email you the UI log and the log file.
I was using an older test version of the Tthrottle.exe v5.8. Once I updated to the latest Fred provided all is good.
Thank you Fred for getting this great piece of software working on my dual Xeon 16 core machine!
Quote from: ChrisSibbald on July 20, 2012, 05:02:02 PM
I was using an older test version of the Tthrottle.exe v5.8. Once I updated to the latest Fred provided all is good.
Thank you Fred for getting this great piece of software working on my dual Xeon 16 core machine!
Thanks Chris.
If anyone put this test version on their machine.
Delete *.dll and *.exe in this folder: C:\Program Files\eFMer\TThrottle and install the V 5.80 official beta release.
But if it works, let it run.
The only changes in the beta release is for the BoincTasks temperature graphs and for some AMD testing.