Skip to content
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

segmentation fault (core dumped) with cuckaroo_cpu_avx2_xx plugin on ubuntu 18.04 #75

Closed
hadv opened this issue Dec 27, 2018 · 8 comments

Comments

@hadv
Copy link

hadv commented Dec 27, 2018

When running with cuckaroo_cpu_avx2_xx miner plugins, grin-miner always be stop with below error

segmentation fault (core dumped)

it's no problem with miner plugins: cuckatoo_mean_cpu_avx2_31 and cuckaroo_cpu_compat_29

@bladedoyle
Copy link
Contributor

It crashes for me on both i7 and i9 CPU. The stack trace shows:

Thread 9 "grin-miner" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffef13c8700 (LWP 17730)]
edgetrimmer::genUVnodes (this=this@entry=0x7ffff540e000, id=id@entry=0)
    at /home/bdoyle/tmp/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroo/mean.hpp:333
333               _mm256_store_si256((__m256i *)(buf + e),     XOR(XOR(v0,v1),XOR(v2,v3)));
(gdb)

@tromp
Copy link
Contributor

tromp commented Dec 29, 2018

Should be fixed by tromp/cuckoo@7454620

To fix this before the next grin-miner update, you can run
git submodule update --remote --recursive
and rebuild grin-miner

@hadv
Copy link
Author

hadv commented Dec 29, 2018

Should be fixed by tromp/cuckoo@7454620

To fix this before the next grin-miner update, you can run
git submodule update --remote --recursive
and rebuild grin-miner

it seems I still have problem with cuckaroo_cpu_avx2_29 miner plugin

@tromp
Copy link
Contributor

tromp commented Dec 29, 2018

Note that I needed a fix in another place too. Are you using tromp/cuckoo@a074dcc or a later commit?

@hadv
Copy link
Author

hadv commented Dec 29, 2018

Note that I needed a fix in another place too. Are you using tromp/cuckoo@a074dcc or a later commit?

I will recheck later. I just run git submodule update --remote --recursive and rebuild

@tromp
Copy link
Contributor

tromp commented Dec 29, 2018

Let me know if you still have crashes...

@hadv
Copy link
Author

hadv commented Dec 29, 2018

thanks, it worked with this commit tromp/cuckoo@4ec7302

@tromp
Copy link
Contributor

tromp commented Dec 29, 2018

Ok, feel free to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants