Posts by Graham Thomas


log in
1) Message boards : Number crunching : Forced to abandon GPU processing of SETI work (Message 1761380)
Posted 4 days ago by Profile Graham Thomas
Thanks again, everyone. I'd already changed my settings to those given in AllenIN's last message, including -cpu_lock. I've now upped -period_iterations_num to 550. If that doesn't work I'll increase -sbs too. Should I increase -sbs by a number such as 64 or 128, or doesn't it matter?
2) Message boards : Number crunching : Forced to abandon GPU processing of SETI work (Message 1761005)
Posted 5 days ago by Profile Graham Thomas
OK - so not 100% fantastic. I've had two SETI@Home v8 GPU units stall in the last four days. I'm not sure what they have in common, but I suspect they're the ones that are scheduled to take the longest times to run.

However, I can live with that.

Would increasing the number of iterations in AllenIN's tweak (above) be likely to help - and if so, why?
3) Message boards : Number crunching : Forced to abandon GPU processing of SETI work (Message 1759630)
Posted 9 days ago by Profile Graham Thomas
Fantastic!

The tweaks to the config file appear to have done the trick. All SETI@home v8 units that ran on my GPU yesterday completed without problems.

Thanks once again, everyone, for your help.
4) Message boards : Number crunching : Forced to abandon GPU processing of SETI work (Message 1759423)
Posted 10 days ago by Profile Graham Thomas
Thanks for all your help.

Bob Smith: I'm pretty sure I'm using the ATI drivers, as I update them using the AMD Catalyst Control Center. Your suggestion for choosing only Astropulse would mean that I couldn't run SETI@home v8 tasks on my CPUs, and I'd still like to be able to do that: on balance I'd prefer to turn off GPU processing if necessary.

AllenIN: I've now implemented your suggested change and I'll see how that goes. I had something similar (though with a lower number of iterations) in the file for a previous version and it didn't work, but I now see I had implemented the earlier change in the wrong file (for v7.03 rather than v7.07). Anyway, I've now made the change in the file for v8.00. I'll post again to let you know if it works.
5) Message boards : Number crunching : Forced to abandon GPU processing of SETI work (Message 1759022)
Posted 12 days ago by Profile Graham Thomas
When SETI@home v8 units were first released I hoped that the problems I'd had with v7 units and my ATI GPU might go away.

With longer work units (those estimated to take around 2 hours on my GPU, as opposed to the shorter 45-minute units which were fine, the unit would complete a certain percentage of its work, often around 20%, then cause the display driver to stop working. The display driver would recover, but processing on the unit would then stop (i.e. the percentage of work done would remain the same while both the elapsed time and the remaining time would increase).

When I discussed this on the SETI message board a while back, several people made helpful suggestions, typically involving tweaking my config file. Thanks to everyone who made these suggestions, but alas nothing worked.

So, I hoped things would change with v8, but they haven't. Longer units still stop at around 20% completed. I haven't received any shorter units to compare yet. I suspect they'd be OK, and Astropulse units - on the rare occasions when I get any - are also fine.

However, in the absence of an option to have only Astropulse and/or shorter SETI@home v8 units processed on the GPU, I've decided to allow no SETI units to run on the GPU rather than having to check which ones to abort several times a day. It means I'll run a lot fewer SETI units than before, but there are plenty of other machines out there so it's OK.

I don't expect anyone to try to fix the problem, because I doubt whether enough people have the same GPU to make it worthwhile.

Here are the details of my setup, in case anyone else has the same problem:

23/01/2016 18:56:21 | | CAL: ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (CAL version 1.4.1848, 512MB, 479MB available, 960 GFLOPS peak)
23/01/2016 18:56:21 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (driver version 1800.11 (VM), device version OpenCL 1.2 AMD-APP (1800.11), 512MB, 479MB available, 960 GFLOPS peak)
23/01/2016 18:56:21 | | OpenCL CPU: AMD A8-3850 APU with Radeon(tm) HD Graphics (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1800.11 (sse2), device version OpenCL 1.2 AMD-APP (1800.11))
6) Message boards : Number crunching : Can I prevent longer 7.03 WUs being downloaded? (GPU problem) (Message 1653136)
Posted 15 Mar 2015 by Profile Graham Thomas
Thanks for all that extra info. Very useful.

I've now detached from and reattached to the project. I noticed that the apps were downloaded again, so I guess that the recompilations have been done.

I tried leaving some of the longer 7.03 units in the list to see if they would complete. The first one that was processed did stall, but it got further along (ca 60%) than was the case previously. Now I'll try leaving just the 'shorter longer' units (if that makes sense - those scheduled to take, say, 2 hrs 15 mins to finish rather than the 3 hrs or more scheduled for the longest ones) and see what happens.

I'll then try adding the line suggested above to the two files.

(Oh, and I also tried letting Device Manager update my display driver, just in case my AMD Catalyst suite wasn't up-to-date. Big mistake. It 'updated' to a 2011 driver and totally knocked out the GPU. Thank goodness for the roll-back feature.)

Admiral Gloval: it looks like your machine is processing the 7.03 units about twice as fast as mine. How good that it depends of course on how capable your processor is supposed to be (there are comparison tables you can search for), but from here it looks OK.
7) Message boards : Number crunching : Can I prevent longer 7.03 WUs being downloaded? (GPU problem) (Message 1652464)
Posted 13 Mar 2015 by Profile Graham Thomas
OK, now I'm a bit confused.

Some of the results reported above (especially the Astropulse 6 result) are from several months ago, before I updated my ATI drivers. They were certainly old then, and I updated after I saw that Astropulse 7 units were exiting (or stalling - can't remember - as soon as they started.

You can see what I'm running now from my post at the top of this thread. I've just checked my AMD Catalyst Control Center and the software update checker tells me I'm up-to-date (I'm running the standard version, not the beta.) The Catalyst software suite version is given as 14.501.1003.etc

I can see a CAL version from my seti@home event log. It's 1.4.1848, which is higher than the minimum given in posts above. My OpenCL version is 1.2 and as far as I know it just comes with the Catalyst suite. I can't see any mention of SDK.

I can certainly try detaching from the project and reattaching. But what would that change?
8) Message boards : Number crunching : Can I prevent longer 7.03 WUs being downloaded? (GPU problem) (Message 1652028)
Posted 12 Mar 2015 by Profile Graham Thomas
Thanks, Mike.

However, I can't see a file called

mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt

in my

C:\ProgramData\BOINC\projects\setiathome.berkeley.edu

folder (which I hope is what you meant by 'projects' folder).

I do, though, have two (empty) files there called:

mb_cmdline_7.03_opencl_ati_sah.txt
mb_cmdline_7.03_opencl_ati5_sah.txt

Would it be useful to add the -period_iterations_num line to either or both of these?
9) Message boards : Number crunching : Can I prevent longer 7.03 WUs being downloaded? (GPU problem) (Message 1651592)
Posted 11 Mar 2015 by Profile Graham Thomas
I haven't seen any Astropulse units for a long time now, but I do get lots of seti@home v7 7.03 WUs downloaded for my GPU. This in itself isn't a problem, but units scheduled to take a longer time to complete end up stalling. They reach a certain percentage of their worktime (usually around 20%), then stick at that percentage and amount of time completed, while incrementing the time to completion. Also, at the point when the WU stalls, my screen display goes blank and then recovers.

These WUs are typically scheduled to take 2-3 hours on my machine, whereas shorter WUs that are scheduled to complete in just over an hour run without problems. I've been told (in response to an earlier post here) that there are some combinations of GPU hardware and drivers that just don't handle the longer units. (Details of my setup are below.)

I've got used to aborting the longer WUs before they run, but it's tedious. Is there a way to make sure they don't download in the first place? From the spec of the cc_config.xml file, it looks like it might be possible to stop *all* v7.03 WUs from downloading (via the exclude_gpu option, though I'm no expert here), but that would leave my GPU idle until Astropulse units start flowing again. Is there any way to distinguish between longer and shorter WUs?

Here's my setup:

11/03/2015 08:51:59 | | CAL: ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (CAL version 1.4.1848, 512MB, 479MB available, 960 GFLOPS peak)
11/03/2015 08:51:59 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (driver version 1642.5 (VM), device version OpenCL 1.2 AMD-APP (1642.5), 512MB, 479MB available, 960 GFLOPS peak)
11/03/2015 08:51:59 | | OpenCL CPU: AMD A8-3850 APU with Radeon(tm) HD Graphics (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1642.5 (sse2), device version OpenCL 1.2 AMD-APP (1642.5))
11/03/2015 08:51:59 | | Processor: 4 AuthenticAMD AMD A8-3850 APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
11/03/2015 08:51:59 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 popcnt syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
11/03/2015 08:51:59 | | OS: Microsoft Windows 7: Home Premium x64 Edition, Service Pack 1, (06.01.7601.00)
10) Message boards : Number crunching : Long Seti@home v7.7.03 units (not Astropulse) on AMD GPU - don't finish? (Message 1611800)
Posted 10 Dec 2014 by Profile Graham Thomas
Thanks for all that helpful advice. I'll take a look at that config file and its help file and see if I can work out what those parameters mean. I'm not sure I want to go for any of the more specialised apps at this point.
11) Message boards : Number crunching : Long Seti@home v7.7.03 units (not Astropulse) on AMD GPU - don't finish? (Message 1611639)
Posted 10 Dec 2014 by Profile Graham Thomas
Recently I've been getting Seti@Home v7.7.03 workunits that run on my AMD GPU (as opposed to the v7.7.00 units that run on the CPU). They seem to come in two flavours. One has an estimated time of just over an hour, and these units complete with no problems. The other has an estimated time of about three and a half hours, and these units seem to get stuck. Generally, after starting OK, when they get stuck they show as being about 20% done, and although the 'elapsed' column keeps counting the 'remaining' column doesn't change.

The first few times this happened I let the computation proceed for 6-8 hours before aborting. Now I abort as soon as I see them in the queue.

Has anyone else seen this behaviour? Is there anything I can do about it? And are there any negative consequences of aborting units frequently?

Astropulse units complete OK.

Here's my setup:

06/12/2014 11:53:00 | | CAL: ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (CAL version 1.4.1848, 512MB, 479MB available, 960 GFLOPS peak)
06/12/2014 11:53:00 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (driver version 1573.4 (VM), device version OpenCL 1.2 AMD-APP (1573.4), 512MB, 479MB available, 960 GFLOPS peak)
06/12/2014 11:53:00 | | OpenCL CPU: AMD A8-3850 APU with Radeon(tm) HD Graphics (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1573.4 (sse2), device version OpenCL 1.2 AMD-APP (1573.4))
06/12/2014 11:53:00 | | Host name: -----
06/12/2014 11:53:00 | | Processor: 4 AuthenticAMD AMD A8-3850 APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
06/12/2014 11:53:00 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 popcnt syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
06/12/2014 11:53:00 | | OS: Microsoft Windows 7: Home Premium x64 Edition, Service Pack 1, (06.01.7601.00)

Graham
12) Message boards : Number crunching : Seti@Home 7.7.03 tasks seem to run on GPU - is this normal? (Message 1598545)
Posted 8 Nov 2014 by Profile Graham Thomas
Thanks to both of you. I'll (probably) let the scheduler sort itself out.

The progress bar and 'time remaining' indicators don't seem to work well with the v7.7.03 Seti@Home units that are running on the GPU. They don't appear to get done any faster than the others so I'm not sure that there's any advantage in running them in this way.

I'll see how things settle down and then decide whether to intervene.
13) Message boards : Number crunching : Seti@Home 7.7.03 tasks seem to run on GPU - is this normal? (Message 1598516)
Posted 8 Nov 2014 by Profile Graham Thomas
It used to be the case that my normal Seti@Home tasks ran on my CPU(s) while Astropulse tasks ran on "0.128 CPUs + 1 ATI GPU". (I've got an AMD A8 3850 quad processor with built-in ATI GPU.)

Recently I've been receiving Seti@Home v7.7.03 tasks that claim to be running on 0.128 CPUs + 1 ATI GPU. These tasks all have either (opend_ati_cat132) or (opend_ati5_nocal) following their version number. v7.7.00 tasks are running on CPUs as normal and have nothing in brackets following their version number.

Is this all OK? And if I get more Astropules tasks will these take priority over the Seti@Home tasks on the GPU?
14) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585717)
Posted 12 Oct 2014 by Profile Graham Thomas
jschoepf - it sounds like your problem is the same as (or very similar to) the one I had. See which graphics drivers you're using and whether you can update them.

In the meantime, from BOINC/Projects tab/SETI@home, you can go to "Your account", then to SETI@home settings and change them so that your computer does not receive Astropulse v7 units. You may have to untick the box that says something like 'Accept other kinds of workunits if none of those selected are available'. That should stop you getting more and more units until you fix your problem.

Graham
15) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585715)
Posted 12 Oct 2014 by Profile Graham Thomas
Claggy - you're right. The SETI@home site is now displaying the new driver information. Thanks again.

Graham
16) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585375)
Posted 11 Oct 2014 by Profile Graham Thomas
OK - AMD display driver(s) updated and Astropulse 7 7.04 unit now happily running.

The SETI@home site still shows the old driver on the 'Your Computers' page (I'm not sure if that info will eventually be updated automatically). That's where I took the information from, so if my driver had ever autoupdated it might not have been quite so old. But it was clearly too old for v7 units. If anyone's interested, this is what my BOINC event log now tells me I'm using:

11/10/2014 19:11:51 | | CAL: ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (CAL version 1.4.1848, 512MB, 479MB available, 960 GFLOPS peak)
11/10/2014 19:11:51 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (driver version 1573.4 (VM), device version OpenCL 1.2 AMD-APP (1573.4), 512MB, 479MB available, 960 GFLOPS peak)
11/10/2014 19:11:51 | | OpenCL CPU: AMD A8-3850 APU with Radeon(tm) HD Graphics (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1573.4 (sse2), device version OpenCL 1.2 AMD-APP (1573.4))


Thanks everyone.

Graham
17) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585355)
Posted 11 Oct 2014 by Profile Graham Thomas
Yes - CPU units are running.

Graham
18) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585353)
Posted 11 Oct 2014 by Profile Graham Thomas
Thanks Claggy. I'll see if I can update the driver.

Graham
19) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585350)
Posted 11 Oct 2014 by Profile Graham Thomas
Ah - I've just seen there's a message when I hover the mouse over a 'Waiting to run' unit. It says, "Scheduler wait: unsupported OpenCL runtime".

Anything I can do about that? Or should I just abort the units and turn off acceptance of AP v7 until this particular version of OpenCL is supported?

Graham
20) Message boards : Number crunching : AP 7 7.04 units download, start, then go to 'waiting to run' (Message 1585347)
Posted 11 Oct 2014 by Profile Graham Thomas
Apologies if I should have added this to the 'AP7' thread, but that thread looks like it's dealing with different issues.

In the last day or so I've had a lot of downloads of AP 7 7.04. They start to run, but then (after about a second) they straightaway go into 'Waiting to run'. The next time the project updates, BOINC sees that I have no AP units running on the GPU and downloads some more.

I can tell SETI@home not to accept v7 units, but I'd prefer to find out how to get them to run. What can I do?

I'm running stock Windows BOINC 7.2.42 (x64) on an AMD CPU with built-in Radeon GPU. Specs are as follows:

AuthenticAMD
AMD A8-3850 APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
(4 processors)

AMD AMD Radeon HD 6520G/6530D/6550D/6620G (SuperSumo) (512MB) driver: 1.4.1417 OpenCL: 1.1

I've checked my preferences and have tried restarting BOINC, and then restarting the PC. Still no joy.

Graham


Next 20

Copyright © 2016 University of California