Unity/Compiz very slow after resume from suspend

[Chris Cheney]

After suspending and then resuming the system unity/compiz often but not always becomes extremely slow to respond, so much so that you can see the transistion from lockscreen to desktop for many minutes (if it ever finishes). I will attach a picture of what it looks like. I didn't wait around long enough to see if it would ever actually finish showing the desktop.

Is there any way to work around this issue? setsid unity has been mentioned online as a workaround for unity/compiz problems but that does not appear to work when run from the linux command line outside of X.

The system has never been able to run the nouveau driver due to it crashing on resume under any desktop environment, which is the primary reason its running the nvidia driver which has worked fine for the past 5 years I've owned the system.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013
 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Apr 27 15:14:01 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: nvidia-304, 304.117, 3.13.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:3417]
InstallationDate: Installed on 2014-04-25 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. P55-UD5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4cbdddb9-1645-4914-b056-903626ac77cf ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11c
dmi.board.name: P55-UD5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11c:bd11/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD5:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55-UD5
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Apr 27 15:10:24 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.15.1-0ubuntu2

[Chris Cheney (ccheney)]

So I found a temporary workaround that seems to work, whenever it hangs I can send HUP to compiz and that seems to fix the problem.

eg:

kill -HUP $(pidof compiz)

However this appears to expose yet another bug that minimized windows at the time of compiz restart essentially disappear permanently, they do not show up in the sidebar anymore, eg if you have 5 firefox windows any that are minimized disappear from the list until firefox is restarted.

[Chris Cheney (ccheney)]

After watching a few more days most of the time compiz apparently just doesn't come back at all from suspend, all that is seen is a black screen with a mouse cursor. That is what happens probably 95% of the time.

Unfortunately due to Ubuntu dropping the previous 18mo support cycle I will probably end up having to transition the systems off of Ubuntu onto Fedora soon or something else that actually works and doesn't use compiz. Since sticking with 13.10 is no longer an option.

[Wouter van Os (wouter0100)]

I'm also experiencing this exact problem for some months now (using Ubuntu 14.10 and 14.04) with an Intel and Nvidia (Optimus) graphic cards..

Workaround seems to work well here. The only thing is that my windows on other workspaces are going back to the main screen, which is obvious.

[Alex Baggott (alex-baggott)]

Thank you for taking the time to report this bug. We have tried to recreate this on the latest release of Ubuntu and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu, please comment on why that is the case and change the bug status to NEW.

Tested by suspending and resuming four times in a row.

[aleph0 (ethan-tate)]

I came here because I have the exact same issue.
Brand new Dell XPS 13 with Ubuntu 14.04.

Aftrr wake from suspend I see a black screen with cursor; then the desktop shows up and looks fine, but performance is more than sluggish - videos become slideshows.

[Leonard Broman (firepiper)]

This issue just started reappearing since about one week back on my XPS 15 9550 laptop. I've had the laptop for some time and not had this issue. I don't know how to get more input to this bug to get it fixed.

However, this fixes it: http://askubuntu.com/questions/792605/ubuntu-16-04-lts-too-slow-after-suspend-and-resume

[Kai-Heng Feng (kaihengfeng)]

Leonard,

I think it's not related to Unity, what happens here is something like [1],

"A bug was reported that on certain Broadwell platforms, after resuming from S3,
the CPU is running at an anomalously low speed.

It turns out that the BIOS has modified the value of the THERM_CONTROL register
during S3, and changed it from 0 to 0x10, thus enabled clock modulation(bit4),
but with undefined CPU Duty Cycle(bit1:3) - which causes the problem."

So basically the "right fix" should come from BIOS, in generally I think Dell is doing a good job at updating BIOS.

If they don't want to fix this at their side, you should file a bug at [2].

[1] https://patchwork.kernel.org/patch/7692241/
[2] https://bugzilla.kernel.org/

[Leonard Broman (firepiper)]

Yes. I assumed it was unrelated to Unity but couldn't find a better bug report tracking this in launchpad. I have a skylake processor and they mention this in the patchwork thread that the issue is appearing in skylake as well. I'll check to see if there are BIOS updates incoming to my laptop.