-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes finding incorrect hashes on a Mac #3
Comments
Thanks for reporting the problem and for the detailed information. The good news is that I am able to reproduce the bug on a Sierra 10.12.6 MacBook Air 13 (Late 2010). Using the GPU (GeForce 320M) produces wrong results with any prefix, while using the CPU (Core2 Duo L9600) produces correct results (so far). Unfortunately, at the moment I don't have a lot of free time and I will have to borrow the hardware in order to be able to debug the problem, but I hope to be able to work on it during this weekend and/or the weekend after. :) |
Oh wow, that would be awesome, thank you! |
@lukebatchelor I seem to have fixed it for the Air in 6a0bbdf . I would like to run more tests, but the GeForce 320M does only about 3 MHash/s. I will continue with the tests next weekend. For some reason on the Air's GPU it behaves in a mind boggling way, not that I'm an OpenCL guru (and I have used it almost exclusively on AMD), but some of the behaviour is outright bizarre. It would be great if you could confirm that this works with your setup :) |
Completely understand that this is a pretty old project, so I don't expect a response at all, but just wondering if you might know why I'm getting intermittent (but consistent) errors when using certain prefixes.
This is the output I'm seeing
I've had tons run fine, but certain prefixes consistently fail. '13' and '13131313'. Even after changing the state of the repo (making more commits, changing author name).
More info:
I was actually able to run all this without installing any of openCL.
When running I get these options
and it runs fine with all three devices (except for getting the wrong sha's sometimes).
The text was updated successfully, but these errors were encountered: