Forum > GPU crunching
x38g reports
Jason G:
Thanks,
Clearly those runtimes indicate something freaked out. Despite that, there's no visible indication in stderr apart from the excessive runtime on the task report itself, which means I'll need to instrument every kernel launch to find out what's happening. That will take a few days to go through the whole code, then if you;re agreeable I'll drag you into the dev area to pin down the exact point(s) of downclock. I'll do so by using a build instrumented to check for kernel errors and subsquently print the brand new, presumably downclocked, clock speed after the point of failure.
Can you confirm (once again) that these are 'sticky downclocks' requiring a reboot to clear ?
Jason
perryjay:
:o The, the dev area???? Can I bring a gun?
Yes, they needed a reboot. Well, at least the first one did. I just went ahead and rebooted when I saw the one today. Figured it was the easiest way to get going again fast. So far this time everything is running okay again now.
Jason G:
--- Quote from: perryjay on 23 Jun 2011, 01:37:06 pm --- :o The, the dev area???? Can I bring a gun?
Yes, they needed a reboot. Well, at least the first one did. I just went ahead and rebooted when I saw the one today. Figured it was the easiest way to get going again fast. So far this time everything is running okay again now.
--- End quote ---
OK, but we won't wait for it to downclock again to try something.
Please swap in the attached, deliberately slightly dialled back for diagnostic purposes, build, while I spend the next few days instrumenting the code. If this one doesn't initiate downclocks on the card in the meantime, then it'll add some possibilities to the investigation, directing me to optimise a particular piece of code I've been hesitant to touch so far (so that part remained stock until this dialled back build).
(x39c, dialled back build attached for diagnostic purposes)
[Edit:] Old build removed. Please use the updated x39d build at:
http://lunatics.kwsn.net/12-gpu-crunching/x38g-reports.msg39407.html#msg39407
Jason G:
FYI: there is an easy way to swap in builds if you're confused by the app_info.
perryjay:
Okay, just to be sure, where does it go? Do I just replace all instances of <file_name>Lunatics_x38g_win32_cuda32.exe</file_name> in the app info or do I need to put it somewhere else?
Easy way? What's that? I've never seen such a thing. Nothing is easy for a n00b like me! ;D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version