mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Hardware > GPU Computing > GpuOwl

Reply
 
Thread Tools
Old 2019-11-14, 21:29   #23
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

164738 Posts
Default

mfakto ran 280000+ self tests without issue.
Prime95 is online now   Reply With Quote
Old 2019-11-14, 21:38   #24
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

7×1,069 Posts
Default

With mfakto TF running in one window generating nice stable core and memory clock speed I tried gpuowl prp on 216091. No joy, ending the power piking theory.
Prime95 is online now   Reply With Quote
Old 2019-11-14, 22:18   #25
tServo
 
tServo's Avatar
 
"Marv"
May 2009
near the Tannhäuser Gate

3×211 Posts
Default

Quote:
Originally Posted by Prime95 View Post
add "-use ORIG_X2" to config.txt in the gpuowl directory
Thanks,George.
That fixed the __asm problem but now I am having the same results as you, even with the Afterburner stuff I modify. I get a black screen and must power cycle.
I have also tried it without -fft +3 to no avail.
Maybe more experimenting tomorrow …..
I might try underclocking it.

One thing I did notice, when starting v5.0, which still works of course, Afterburner shows
a 10 degrees C jump upon startup INSTANTLY.
tServo is offline   Reply With Quote
Old 2019-11-15, 00:43   #26
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

117438 Posts
Default

Quote:
Originally Posted by tServo View Post
One thing I did notice, when starting v5.0, which still works of course, Afterburner shows
a 10 degrees C jump upon startup INSTANTLY.
Gave 5.0-9c13870 a try here, got encouraged by the smaller exponents, then it hung on the start of 6972593.
kriesel is online now   Reply With Quote
Old 2019-11-15, 01:27   #27
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

7×1,069 Posts
Default

I ran a two hour mfakto run without problem.

I tried some suggestions from here, namely eliminating game bar. In Wattman I increased the performance monitoring time to 5, and turned off options like shader cache and surface optimization.

I can now run a prp test of 216091 and 756839. This is progress. However, running a PRP with a 5M FFT fails.

Looking for more Windows "features" I can turn off....
Prime95 is online now   Reply With Quote
Old 2019-11-15, 09:02   #28
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

3·1,697 Posts
Default

Quote:
Originally Posted by Prime95 View Post
I ran a two hour mfakto run without problem.

I tried some suggestions from here, namely eliminating game bar. In Wattman I increased the performance monitoring time to 5, and turned off options like shader cache and surface optimization.

I can now run a prp test of 216091 and 756839. This is progress. However, running a PRP with a 5M FFT fails.

Looking for more Windows "features" I can turn off....
I'll see you a shader caching, a surface optimization, and 5 seconds of performance monitoring time, and raise you another 5 seconds of performance monitoring time, and a chill, a -carry long option, +32GB of ram, and a BIOS change ("balanced performance" to "performance")

With no overclocking attempted:
V6.5-84-g30c0508, which is type 1 residues, but no P-1 on NVIDIA
gpuowl-win -user kriesel -cpu roa/radeonvii -use FMA_X2 -device 1 -carry long
or ORIG_X2, speeds are about the same, and I was able to successfully run brief trials at a subset of known mersenne primes selected for about 2:1 exponent spacing; others not attempted.

For PRP=0,1,2,82589933,-1,76,0,3,1
GECs pass,
and the 1M iteration res64 matched the respective entry at https://www.mersenneforum.org/showpo...83&postcount=5

Trying v6.11-9 after that, it matched the 10,000,000 iteration res64 from a separate start for 82589933.
Radeon VII fan speed is humming along at 61%, one of the few parameters gpu-z will show in remote desktop.

Last fiddled with by kriesel on 2019-11-15 at 09:03
kriesel is online now   Reply With Quote
Old 2019-11-15, 18:35   #29
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

3×1,697 Posts
Default Bad news, good news

Quote:
Originally Posted by kriesel View Post
Trying v6.11-9 after that, it matched the 10,000,000 iteration res64 from a separate start for 82589933.
Radeon VII fan speed is humming along at 61%, one of the few parameters gpu-z will show in remote desktop.
I found it hung this morning, at 34.8% complete, only lost a couple of hours. No GEC errors.
Required a system restart to recover.
The good news is I bumped the memory clock up 2% and turned off the annoying game slideshow in Wattman, and gpuowl v0.5 (the only gpu LL tester with the Jacobi check included) completed all the packaged selftests of v0.5 gpuowl with no detected error. That would make some fast LL DC results, at ~0.86 ms/iteration single instance.

This v0.5 selftest sequence slams the gpu power pretty hard, fluctuating it between 18. W min and 258. W max as reported by GPU-Z between and during brief selftests.
Attached Thumbnails
Click image for larger version

Name:	radeon vii ll selftest.png
Views:	130
Size:	470.7 KB
ID:	21315  

Last fiddled with by kriesel on 2019-11-15 at 18:59
kriesel is online now   Reply With Quote
Old 2019-11-15, 19:18   #30
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

7×1,069 Posts
Default

My linux setups are all configured for best throughput at reasonable power consumption. That translates to about 1550MHz core, 870mV and 1150MHz memory. Power draw ~180 watts. YMMV.

Best throughput comes from running 2 PRP tests at the same time.

Last fiddled with by Prime95 on 2019-11-15 at 19:22
Prime95 is online now   Reply With Quote
Old 2019-11-15, 20:12   #31
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

3×1,697 Posts
Default

Gpuowl v0.5 LL DC on a 50M exponent and gpuowl v6.11-9 on PRP Mp51* sharing the same XFX Radeon VII, at ~1700Mhz auto set gpu clock, 1075Mhz memory clock, stock voltage, ok, and averaging 187W. Changed the V6.11-9 PRP run from -carry long to -carry short, and seemingly instantly got a display hang.

Patient: It hurts when I do this.
Doctor: Don't do that.
kriesel is online now   Reply With Quote
Old 2019-11-15, 20:21   #32
ewmayer
2ω=0
 
ewmayer's Avatar
 
Sep 2002
República de California

101101011010112 Posts
Default

Quote:
Originally Posted by kriesel View Post
Patient: It hurts when I do this.
Doctor: Don't do that.
You left off the ending of the story: "Patient stops breathing, expires a few minutes later."
ewmayer is offline   Reply With Quote
Old 2019-11-15, 20:55   #33
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

10011111000112 Posts
Default

Quote:
Originally Posted by ewmayer View Post
You left off the ending of the story: "Patient stops breathing, expires a few minutes later."
This one stopped breathing, but was easily and quickly revived.
kriesel is online now   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
gpuOwL-specific reference material kriesel kriesel 28 2021-03-27 18:40
gpuowl: runtime error SELROC GpuOwl 59 2020-10-02 03:56
GPUOWL AMD Windows OpenCL issues xx005fs GpuOwl 0 2019-07-26 21:37
gpuowl tuning M344587487 GpuOwl 14 2018-12-29 08:11
How to interface gpuOwl with PrimeNet preda PrimeNet 2 2017-10-07 21:32

All times are UTC. The time now is 23:00.

Thu May 6 23:00:52 UTC 2021 up 28 days, 17:41, 0 users, load averages: 2.40, 2.32, 2.25

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.