Ubuntu 14.04 blank screen after wakeup from sleep

[Kenneth Bogert]

Possibly related to bug 1283938 . I have disabled lock screen on suspend to try and get around the bug but it obviously hasn't worked.

I see a completely black screen with a working mouse cursor. Used Ctrl-Alt-F2 to login at a text terminal and tried to kill gnome-settings-daemon and gnome-shell (doing so has randomly made it work in the past). The gnome-shell process would not kill and I got segfault dmesg errors which are attached.

WORKAROUND: echo auto > /sys/class/drm/card0/device/power_profile

WORKAROUND: Turn off the System-monitor extension in Gnome tweak tool.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 9 14:31:20 2015
DisplayManager: gdm
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-24 (319 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64+mac (20140204)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to trusty on 2014-09-21 (200 days ago)
---
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kbogert 2487 F.... pulseaudio
 /dev/snd/controlC1: kbogert 2487 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=41830e03-5386-43ed-88b8-1c77dd33df98
InstallationDate: Installed on 2014-05-24 (320 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64+mac (20140204)
MachineType: Dell Inc. Studio XPS 1640
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic root=UUID=7ba9d8c6-141e-415a-aae4-fb57486d6148 ro quiet splash radeon.audio=1 noautogroup vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-33-generic N/A
 linux-backports-modules-3.16.0-33-generic N/A
 linux-firmware 1.127.11
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.16.0-33-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-09-21 (201 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 04/09/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0U785D
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd04/09/2011:svnDellInc.:pnStudioXPS1640:pvrA153:rvnDellInc.:rn0U785D:rvrA15:cvnDellInc.:ct8:cvrA15:
dmi.product.name: Studio XPS 1640
dmi.product.version: A153
dmi.sys.vendor: Dell Inc.

[penalvch (penalvch)]

Kenneth Bogert, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1442311

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Kenneth Bogert (kbogert-uga)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc7-vivid/

[jose (o1485726)]

Nevermind my previous comment, I doubt it's the same bug...

[Kenneth Bogert (kbogert-uga)]

Just tried 4.0.0 , and on first try I triggered this issue. I was, however, able to kill gnome-setting-daemon and then gnome-shell from a terminal. This then caused the lock screen to appear and I was able to log in. I've had this happen sometimes in the past before, so I consider this no change.

No suspect messages in dmesg or Xorg.0.log

[penalvch (penalvch)]

Kenneth Bogert, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Kenneth Bogert (kbogert-uga)]

Instead of doing that, I decided to do a quick sanity check.

I installed kernel 3.4-precise from the upstream kernel archives, which I know worked fine when I was running 12.04 with gnome shell (even the updated gnome-shell from the webupd8team ppa, I believe the version was 3.8?)

Sure enough, I've reproduced this bug. At this point I'm not sure this is a kernel issue or not.

[Kenneth Bogert (kbogert-uga)]

I finally found some time to work on this, and I think I have it fixed.

Debugging gnome-shell when I hit this bug (note, I could also trigger this bug by allowing the screen to lock, no suspend necessary) I noticed the following backtrace kept happening:

Thread 1 (Thread 0x7f920ec68a40 (LWP 12089)):
#0 0x00007f920b9f912d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007f9202b8ab72 in poll (__timeout=-1, __nfds=1, __fds=0x7fff76528300) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2 _xcb_conn_wait (c=c@entry=0x7f9ed0, cond=cond@entry=0x7fff76528420, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:447
#3 0x00007f9202b8c3ff in wait_for_reply (c=c@entry=0x7f9ed0, request=29601, e=e@entry=0x0) at ../../src/xcb_in.c:490
#4 0x00007f9202b8c512 in xcb_wait_for_reply (c=0x7f9ed0, request=29601, e=0x0) at ../../src/xcb_in.c:520
#5 0x00007f91f8e4b4ce in dri2WaitForMSC (pdraw=0xca4900, target_msc=0, divisor=2, remainder=0, ust=0x7fff76528550, msc=0x7fff76528558, sbc=0x7fff76528560) at ../../../../src/glx/dri2_glx.c:480
#6 0x00007f92090478f6 in _cogl_winsys_wait_for_vblank (onscreen=onscreen@entry=0xca12e0) at ./winsys/cogl-winsys-glx.c:1606
#7 0x00007f9209048016 in _cogl_winsys_onscreen_swap_region (onscreen=0xca12e0, user_rectangles=<optimized out>, n_rectangles=<optimized out>) at ./winsys/cogl-winsys-glx.c:1808
#8 0x00007f920903d341 in cogl_onscreen_swap_region (onscreen=0xca12e0, rectangles=rectangles@entry=0x7fff76528700, n_rectangles=n_rectangles@entry=1) at ./cogl-onscreen.c:337
#9 0x00007f920ce13662 in clutter_stage_cogl_redraw (stage_window=0x855b80) at ./cogl/clutter-stage-cogl.c:641
#10 0x00007f920ce77887 in clutter_stage_do_redraw (stage=0xd11bf0) at ./clutter-stage.c:1184
#11 _clutter_stage_do_update (stage=0xd11bf0) at ./clutter-stage.c:1242
#12 0x00007f920ce5e028 in master_clock_update_stages (master_clock=0xbe7880, stages=0x35dca30) at ./clutter-master-clock.c:457
#13 clutter_clock_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ./clutter-master-clock.c:589
#14 0x00007f920c13ee04 in g_main_dispatch (context=0x7d35f0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3064
#15 g_main_context_dispatch (context=context@entry=0x7d35f0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3663
#16 0x00007f920c13f048 in g_main_context_iterate (context=0x7d35f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3734
#17 0x00007f920c13f30a in g_main_loop_run (loop=0x7d3390) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3928
#18 0x00007f920d883021 in meta_run () at core/main.c:556
#19 0x0000000000401d11 in main (argc=1, argv=0x7fff76528b08) at main.c:439

Specifically frame #6, it appeared to be endlessly waiting for a vblank. So I added the following to /etc/environment:

export CLUTTER_VBLANK=none

I have just done suspend and resume 20 times without issue, whereas previously I could trigger this bug after 3 or 4 on average.

[penalvch (penalvch)]

Kenneth Bogert, to see if this is already fixed in a later release, could you please test for this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Kenneth Bogert (kbogert-uga)]

I cannot install a daily build on this machine, is there a live-usb image with gnome-shell I can test?

[Kenneth Bogert (kbogert-uga)]

Well, after 3 days and I don't know how many suspends / lock screens later this bug hit me again. Let me see if I can get some more information.

[Kenneth Bogert (kbogert-uga)]

I remembered that I had some kernel parameters set, so I turned off the CLUTTER_VBLANK fix and experimented a bit. I used gnome-shell to suspend, then resume and log in repeatedly until gnome-shell locked up.

(default ubuntu kernel parameters) = bug on 7th try
radeon.audio=1 = bug on 1st try
radeon.audio=1 noautogroup = bug on 2nd try

radeon.audio=1 radeon.dpm=1 noautogroup = no bug yet (15 tries)

I'll keep the machine like this and update if it bugs again.

[Kenneth Bogert (kbogert-uga)]

Radeon.dpm managed to crash the whole system (had to do a hard cutoff, caps-lock key wasn't even registering)

I've switched the power management back to "profile", but instead of using the default profile I've switched to "auto". After 15 tries I've not hit this bug. I'll continue with this setup for a while to give it a better test.

[Kenneth Bogert (kbogert-uga)]

Update: I've not hit this bug after 5 days now, and I need to restart to apply security updates.

To recap, the fix was to add the following to /etc/rc.local :

echo auto > /sys/class/drm/card0/device/power_profile

[Kenneth Bogert (kbogert-uga)]

Just to update this bug, I still had this bug occur occasionally even afterwards, though at a greatly reduced rate. After doing some more testing recently, I've been able to avoid this problem completely by turning off the System-monitor extension in Gnome tweak tool.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017

https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

[Daniel van Vugt (vanvugt)]

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm