> DVACT_WAKEUP does finish its job. It's just that it is doing so while > kernel threads and userland processes are running as well. Drivers > need to be aware of this, and I'm not sure they all are.
Well the only thing which could stop that X process from playing with stuff, is the driver it believes it is interfacing with....
