[QUOTE=Prime95;538760]Giant mistake.

... The entire process has bricked one of the GPUs. Not happy.
[/QUOTE]What? It damaged a gpu?

[QUOTE=kriesel;538826]What? It damaged a gpu?[/QUOTE]

Yes. The GPU is no longer recognized at boot. Tomorrow, I'll try moving the card to a different machine. If that machine does not recognize the card, I will have to RMA it.

[QUOTE=Prime95;538829]Yes. The GPU is no longer recognized at boot. Tomorrow, I'll try moving the card to a different machine. If that machine does not recognize the card, I will have to RMA it.[/QUOTE]

I'm wondering how that could even happen - you think some kind of GPU firmware corruption may have taken place? (E.g. onboard EPROM gets borked). If so, is a user reflash a possibility?

Or do you think actual hardware damage, excess voltage frying transistors or whatnot, may have occurred?

[QUOTE=ewmayer;538832]I'm wondering how that could even happen - you think some kind of GPU firmware corruption may have taken place? (E.g. onboard EPROM gets borked). If so, is a user reflash a possibility?

Or do you think actual hardware damage, excess voltage frying transistors or whatnot, may have occurred?[/QUOTE]

I agree -- quite mysterious. I'd guess it was either a coincidence (there were several reboots) or some kind of firmware corruption. Since the card isn't recognized by linux, I do not know how one would re-initialize the firmware.

[QUOTE=Prime95;538834]I agree -- quite mysterious. I'd guess it was either a coincidence (there were several reboots) or some kind of firmware corruption. Since the card isn't recognized by linux, I do not know how one would re-initialize the firmware.[/QUOTE]

This might be a fruitful thing to look further into - I would not be surprised if such firmware-restoration were a manufacturer-only thing, but professional refurbisher/resellers of this kind of tech gear probably know more about how one might go about it. Do we have any folks like that on the forum? I recall PhilF [url=https://mersenneforum.org/showthread.php?t=24979&page=2]noted here[/url] that he had snagged a used Radeon VII for $400 on eBay and was not leery about buying used because "I'm very good at refurbishing used computer equipment" - just PMed him to weigh in here.

[QUOTE=ewmayer;538836]This might be a fruitful thing to look further into - I would not be surprised if such firmware-restoration were a manufacturer-only thing, but professional refurbisher/resellers of this kind of tech gear probably know more about how one might go about it. Do we have any folks like that on the forum? I recall PhilF [url=https://mersenneforum.org/showthread.php?t=24979&page=2]noted here[/url] that he had snagged a used Radeon VII for $400 on eBay and was not leery about buying used because "I'm very good at refurbishing used computer equipment" - just PMed him to weigh in here.[/QUOTE]

Here's my reply to Ernst:

Hello Ernst.

What I am better at is fixing physical damage or on-board power supply issues. However, I did find this:

[url]https://www.asus.com/Graphics-Cards/RADEONVII-16G/HelpDesk_Download/[/url]

This downloadable, stand-alone flash tool may be ASUS specific, I don't know. He may need to seek a similar file for his brand of card. But, the bottom line is that with the monitor hooked up to a working card in the same machine as the bricked card, a stand-alone BIOS flashing tool like this might be able to flash it.

However, this applies only if George is living right, and while flashing it he holds his mouth just right on a Tuesday. :)

Worst case, if it is out of warranty, bricked Radeon VII's go for surprisingly high dollars on eBay.
-Phil

Sorry, the download link didn't come through in the last message. Here it is, just scroll down a bit and click on Show All to find the BIOS flash tool.

[url]https://www.asus.com/Graphics-Cards/RADEONVII-16G/HelpDesk_Download/[/url]

Asrock:
[url]https://www.asrock.com/Graphics-Card/AMD/Phantom%20Gaming%20X%20Radeon%20VII%2016G/index.asp#BIOS[/url]
[url]https://www.asrock.com/support/BIOSVGA.asp?cat=VII16G[/url]

Re-flash may void your warranty.

Please check carefully.

Only re-flash if you know what you are doing and you know this will solve the issue. Otherwise, you may sent the card back and get the answer "it doesn't work because you damaged when re-flash it, therefore you are screwed and need to pay for a new one"...
YMMV

[QUOTE=mrh;538817]I've been wanting to do some P-1 runs where the B1/B2 (mostly B2) values are too big for u32. I was thinking of turning them all into u64's, unless this is bad idea or I'm missing something. What do you think?[/QUOTE]

For what exponent range? you should use the P-1 probability calculator
[url]https://www.mersenne.ca/prob.php[/url]
to get an idea of what to expect.

For an intuition, there is a range of the ratio between B1 and B2 that makes sense. I'd say this range is 10 to 100. If B2 is much-much larger that B1, you're wasting power.

Based on that, for a B2=4'000'000'000 (i.e. around 2^32), you'd want a B1 of at least 40'000'000 (but probably B1=100'000'000 would make more sense). Now you see that probably you could do a full PRP for less than that.

So unless you have a very special reason, doing P-1 with B2 > 2^32 seems like a bad idea to me. Maybe you could explain more about what you're trying to achieve.

untested windows build of gpuowl 6.11-163
 

[QUOTE=preda;538800]Thank you! I just merged the changes. Indeed this is a massive speedup on powers-of-2 FFTs probably bringing them in line with the other sizes. (and thanks for the FFT-size display fix)

I added a few asserts() to .cl (enabled with -use DEBUG) that allow to check the angle range.[/QUOTE]
Here it is, without any testing beyond -h.