-
Notifications
You must be signed in to change notification settings - Fork 167
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
miner crash/bus hangs when mining for dev #1351
Comments
Thank you. Sometimes the dev mining uses a miner, that has not been benchmarked yet. Most probably, that's the reason for the problems, because it might dig up a miner, that might overload a rig. |
- don't benchmark during donation run (issue #1351)
This might have nothing to do with the way it uses miners, but i saw that it crashed when mining for you last night, this is what i got from log.sh and a proper debug file. log.sh: attaching debug file. |
also from dmesg: [125563.771412] NVRM: GPU at PCI:0000:02:00: GPU-1a9c6802-87b7-ace4-7094-b42142a79fc1 |
I just uppgraded from 4.6.7.7 to 4.6.7.8 and i noticed that it wants to re-benchmark basicly all miners, is this supposed to happen? Seems like a bit of overkill and also puts the rig at risk of crashing if you happen to leave auto-updates on :) |
So i'm currently evaluating a minebox12 and i've been installing rbm "fresh" quite a few times and i've noticed that sometimes some miners seem to hang the pcie bus and witch then ususally requires a restart of the rig.
Once that evalluation part of miners is done it's not much of an issue since rbm will simply use whatever miners that ACTUALLY work, but when it starts dev mining it seems like it dosen't care about what "good" miners there are and just uses whatever miners there are and that can cause a bus hang.
So i was thinking, would it not be a sane thing to use the information of known good miners that rbm has evaluated so you the dev actually can get payed for this great software ? :)
I live the pushover integration btw, it's saved me a lot of time and revenue :)
The text was updated successfully, but these errors were encountered: