Graphical (CUDA) workunit crush when PC is used remotely
29 Jan 2011 14:29:33 UTC
Topic 195611
(moderation:
From time to time I have to use my PC (Win XP)remotely via RDP and than all workunit immediately make computation error, one by one. It happens with BRP3cuda32 and with earlier CUDA workunit, too.
Is it possible pause graphical workunit before RDP session?
Rudzik
Graphical (CUDA) workunit crush when PC is used remotely
)
Yes, it's been noted that (specifically) the Windows RDP tool crashes all CUDA apps - not just Einstein's (NVidia's driver is unloaded on the target machine, and a Microsoft driver - not CUDA capable - is loaded instead).
I haven't seen the suggestion of detecting an RDP session start and suspending GPU processing automatically before: that probably isn't possible now, but it's a worthwhile suggestion for future versions of BOINC.
An alternative approach would be to use a different remote access product - I believe VNC is compatible with CUDA, and there may be others.
RE: I haven't seen the
)
It's still 2011, right? Just asking, as this was included in BOINC in 2009, as far as I know.
Started in 6.10.14, continued in 6.10.15, 6.10.16, and as such included in the clients since that time.
Now, there is still a problem when users use the fast user switching option, while BOINC runs CUDA/CAL or OpenCL tasks. Nothing for that yet.
RE: From time to time I
)
I use VNC for this reason rather than RDC. VNC does not crash CUDA apps.
By the way, the reason that
)
By the way, the reason that Windows RDP will make CUDA/OpenCL/CAL work crash/stop/whatever, is because Windows RDP uses its own video driver. This video driver is a stripped down version and doesn't know anything about CUDA (or the others). It is not updated when you update your own video drivers. 3rd Party programs such as VNC use the external --installed by you-- video drivers.
RE: By the way, the reason
)
Err, I think that's what I said. But if v6.10.14/15/16 are supposed to make BOINC suspend, rather than crash, CUDA tasks - why does v6.10.58 crash them all for the OP? Should we find somebody to test this before v6.12.12 goes live?
RE: Err, I think that's
)
Sorry for explaining it in more detail... before questions came of how to update the Windows RDP driver and such.
I'm not clairvoyant and just noticed that the batteries of my crystal orb are dead. So cannot compute.
I don't have any means to test it. Only have one PC running Windows these days, the rest are non-BOINC and run forms of Linux.