Advanced search

Message boards : Number crunching : Messing with vBox crashed a gpugrid WU

Author Message
Profile JStateson
Avatar
Send message
Joined: 31 Oct 08
Posts: 186
Credit: 3,331,546,800
RAC: 0
Level
Arg
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 48998 - Posted: 19 Feb 2018 | 16:21:55 UTC

Noticed really bad distortion playing music so I brought up the vBox console to see of any of my (16) LHC vbox work units were overloading the system. I noticed that sound was disabled so I assumed it was not caused by vBox taking over the audio. While I was reading the vBox dialog box there was a warning statement to the effect that there was only 9mb of VRAM available for vBox to use and that was not enough. Right about that instant I noticed that boinctask reported that one of my gpugrid long tasks crashed with a computation error. Its display was right behind the vBox dialog box so it was immediately apparent. I suspect this was not a coincidence and it was the first gpugrid error I have ever seen on this system.

I traced the sound distortion down to a problem with Dell drivers and posted the problem at the Dell community. It had nothing to do with gpugrid or lhc.

However, I uninstalled LHC from this system as a precaution as it was obvious that bringing up the vBox console caused immediate problems with the gpugrid app.

I noticed that some projects are implementing a reliability test to determine whether or not to send out work units. I hope this failure does not reduce my gpugrid work load.
____________
try my performance program, the BoincTasks History Reader.
Find and read about it here: https://forum.efmer.com/index.php?topic=1355.0

Post to thread

Message boards : Number crunching : Messing with vBox crashed a gpugrid WU

//