search

luke-jr / bfgminer

Modular ASIC/FPGA miner written in C, featuring overclocking, monitoring, fan speed control and remote interface capabilities.
http://luke.dashjr.org/programs/bitcoin/files/bfgminer/
Other
1.84k stars 816 forks source link

cpu miner crashes x86_64 gnu/linux computer with system beep #209

Open leaf-node opened 11 years ago

leaf-node commented 11 years ago

i started up the bfgminer program as follows:

bfgminer -o mine.mtred.com:3333 -O sudoman:password

it ran for a about a half minute, then the screen turned off and there was a beep. the computer then rebooted.

i'd like to log the output, but i don't know which is preferable, using --syslog or piping it with 'cmd 2> stderr.txt' or using --sharelog. last time, the computer died without the chance to sync everything to disk. (when i booted up, fsck found at least one error on my /home partition.)

which logging option should i use? i have yasm installed, so the asm code is being used. here are my system stats:

intel core i3 390M thinkpad edge 13" with debian wheezy gnu/linux.
luke-jr commented 11 years ago

This really sounds like a hardware problem. Software shouldn't be able to do that kind of thing!

The preferred method for logging is using --debuglog with 2>debug.log, but as you say, it probably won't make it to disk based on the info you've reported so far. Even if it did, I doubt there's anything that would be useful. :/

leaf-node commented 11 years ago

yeah, it doess sound like it. :(

i had been running bitcoin-qt v0.8.1 for a while, to download the blockchain, both before and while running bfgminer. when i was running version 0.7.2, other programs would stutter while it was downloading and verifying.

i'm guessing that the blockchain uses hardware hashing capabilities? maybe it's gotten worn out. or it could be a bug in the bios' supervisor mode for that piece of hardware. alternatively, maybe a small section of the cpu overheats, but is too small to heat the entire cpu, causing a hardware error before the kernel or bios can detect an overheat?

my laptop was behaving weird after leaving bitcoin-qt on over night to continue the download, so i had to kill it again... ahh!! :-p

leaf-node commented 11 years ago

i ran the program without any issues for over ten minutes. then i stopped it for a while, and tried another pool. it ran fine again.

but when i stopped it after a bit and then quickly switched back to the other pool, my laptop died a couple seconds after output displayed in the terminal.