[QUOTE=KyleAskine;280586]Core clock is now 750 and mem clock is 900.[/QUOTE]

Crashed again in the same way.

[QUOTE=KyleAskine;280606]Crashed again in the same way.[/QUOTE]
Well, send it back to AMD for replacement ... or at least open a case with them, but I guess it's a H/W issue then.

[QUOTE=Bdot;280645]Well, send it back to AMD for replacement ... or at least open a case with them, but I guess it's a H/W issue then.[/QUOTE]

Thanks a bunch for your help!!

Very seriously, I am very grateful not only for your help, but for mfakto in general.

I suspect if everything was correctly optimized, we may be able to pull as much or more GHz/$ out of AMD.

For real this time...
 

I fixed my issue!

I started running two instances of mfakto last night at around 6pm, and as of this morning at 7am they are still running!

The secret as far as I can tell:

<facepalm>

Run each instance in a real separate terminal window.

</facepalm>

What I was doing: running everything in one screen session, which allowed me to control that session through putty.

I also reinstalled the 11.9 drivers, so it is possible that this is not the reason, but I suspect it is.

[QUOTE=KyleAskine;280777]I fixed my issue!

I started running two instances of mfakto last night at around 6pm, and as of this morning at 7am they are still running!

The secret as far as I can tell:

<facepalm>

Run each instance in a real separate terminal window.

</facepalm>

What I was doing: running everything in one screen session, which allowed me to control that session through putty.

I also reinstalled the 11.9 drivers, so it is possible that this is not the reason, but I suspect it is.[/QUOTE]

Interesting ... and quite strange. When I hear that, my guess would rather be the driver re-installation than the session separation ... if you want to lock up your system one more time, you can try the old session-mode with the reinstalled drivers, just to be sure on that.

I also have some good news: I found a rather small code change that makes mfakto work again on 11.10 and 11.11, with almost no performance-impact (pass the data to the kernel wrapped in a cl_uint8). A little testing over the weekend (if time permits), and I can release that next week.

[QUOTE=Bdot;280787]Interesting ... and quite strange. When I hear that, my guess would rather be the driver re-installation than the session separation ... if you want to lock up your system one more time, you can try the old session-mode with the reinstalled drivers, just to be sure on that.

I also have some good news: I found a rather small code change that makes mfakto work again on 11.10 and 11.11, with almost no performance-impact (pass the data to the kernel wrapped in a cl_uint8). A little testing over the weekend (if time permits), and I can release that next week.[/QUOTE]

Awesome! Thanks for your work on this.

[QUOTE=Bdot;280787]Interesting ... and quite strange. When I hear that, my guess would rather be the driver re-installation than the session separation ... if you want to lock up your system one more time, you can try the old session-mode with the reinstalled drivers, just to be sure on that.[/QUOTE]

I will do that, but probably not until next week, because I may not have a couple hours to myself until then to make sure I am on it when it locks up :smile:

Thanks again for all your work!

[QUOTE=KyleAskine;280838]I will do that, but probably not until next week, because I may not have a couple hours to myself until then to make sure I am on it when it locks up :smile:

Thanks again for all your work![/QUOTE]

Well, I have run the usual culprits (2x mfakto, 1x mprime, 1x top) in a screen session for a few hours now with no crashes. So I guess it was the drivers. I will keep it running overnight for observation :smile:

Be sure to tell everyone using linux to use 11.9 :smile:

[QUOTE=KyleAskine;281165]

Be sure to tell everyone using linux to use 11.9 :smile:[/QUOTE]

And I thought I did:

Readme:
[code]
Install Catalyst driver, version >= 11.7

Catalyst driver 11.9 uses up to one CPU core less than its predecessors:
11.9 strongly recommended.
[/code][URL="http://mersennewiki.org/index.php/Mfakto"]Wiki[/URL]:
[code]
AMD Catalyst drivers 11.4 or higher, 11.9 recommended
[/code]Note, the minimum version mismatch is, because I just recently found out that Catalyst versions as low as 11.4 work, and I updated the Wiki ... but if nobody reads it anyway ...

[QUOTE=Bdot;281225]And I thought I did:

Readme:
[code]
Install Catalyst driver, version >= 11.7

Catalyst driver 11.9 uses up to one CPU core less than its predecessors:
11.9 strongly recommended.
[/code][URL="http://mersennewiki.org/index.php/Mfakto"]Wiki[/URL]:
[code]
AMD Catalyst drivers 11.4 or higher, 11.9 recommended
[/code]Note, the minimum version mismatch is, because I just recently found out that Catalyst versions as low as 11.4 work, and I updated the Wiki ... but if nobody reads it anyway ...[/QUOTE]

:redface::redface::redface:

[QUOTE=KyleAskine;281237]:redface::redface::redface:[/QUOTE]
:grin: :grin: :grin:

Anyway, testing the new mfakto version on Windows with 11.9 and 11.11 went well and everything seemed fine. Today I updated my Linux box to 11.11, and guess what I get within minutes ...
[code]
[fglrx] ASIC hang happened
[/code]The same thing as you described, even at lowest frequency settings. And of course I did not manage immediately to go back to 11.9 - right now it seems as if I did not have any OpenCL driver at all ... Development with OpenCL is not exactly fun :rant: