Mint17 64-bit KDE 4G RAM with SSD system drive and 6-core CPU. ZOTAC ZT-60415-20L GeForce GT630 1G 64-bit DDR3 video card with Linux driver for it. 384 CUDA cores. All updates applied from Mint BOINC manager version 7.2.42 (x64).


Perhaps this is related to that other bug I see where BOINC no longer respects the GPU setting. Perhaps it is a bug with how "leave in memory" is implemented.

I boot the 64-bit partition when I'm done for the evening so it can run BOINC all night long. I used to blame this problem on the Einstein project because it occurred while that project was having other "stuck upload" problems. When Einstein was running along with my other projects (SETI, WCG, LHC, rosetta, Cosmology, I think that is all on this machine) I would have to hard boot when I came in.

I took Einstein off this machine. Lately, when I come in the GUI is delayed by seconds. Even when you uncheck "While computer is in use" it doesn't get better. When I can get a terminal open and run a top command I see neither the CPU nor the memory are maxed out. That would seem to indicate something is not being kind to the GPU.

Adding insult to injury, neither a GUI reboot nor a reboot command from terminal window will reboot the machine. It's a reset button reboot.

Given there is usually tasks for 3 or more projects running at any given time, I cannot blame any particular project. I have read on here SETI has some issues where it will not release the GPU during certain computational stages, but, seriously? 384 CUDA cores and 1G of RAM on the card and it cannot share?

One of my other machines running Mint17 with one of the Gicky-Gnasty-Gnome interfaces and a very old video card with 1 CUDA or something, has none of these problems. Around the end of the month I should be pulling my spare quad core back from a client site. It has the same video card with a different Gicky-Gnasty-Gnome desktop. I should at least be able to determine if this is Mint17+Boinc+384 CUDA core specific or if this problem is more closely related to something in KDE.

Hopefully there will be an update to BOINC or the offending project(s) which fixes this issue.

---