Black screen after resuming from suspend

[Jeremy Jongsma]

Using Ubuntu 14.10 on a Lenovo Yoga 2, when I resume the laptop from suspend I frequently (around 50% of the time) get a blank black screen with a mouse cursor on it, and am unable to login or interact with the desktop at all. Often (also about 50% of the time) switching over to a text terminal and killing "unity-panel-service --lockscreen-mode" causes it to snap out of it and prompt me with the unlock dialog when I switch back to X.

Using xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.7-0ubuntu8.1
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: Wed Feb 4 20:42:38 2015
DistUpgraded: 2014-11-15 17:52:46,161 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.18, 3.16.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3978]
InstallationDate: Installed on 2014-06-28 (221 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20266
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=d1c3a7eb-265e-441f-9aac-eb15636dfe61 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to utopic on 2014-11-15 (81 days ago)
dmi.bios.date: 06/27/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN38WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias: dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Mon Feb 2 11:10:08 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2
xserver.video_driver: intel

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Will Cooke (willcooke)]

As a first step could you try switching to vt1 and back to vt7 without killing unity-panel-service. This will help to narrow down the problem. Switching vt might be enough to get the video woken up, and unity-panel-service might be a bit of a red herring.

[Chris Wilson (ickle)]

It this possible to reproduce with todays -intel update (that disables DRI3)?

[Pat McGowan (pat-mcgowan)]

I confirmed that the workaround to kill unity-panel-service also works for me.
Samsung 940X3G/930X3G laptop running intel haswell
Simply switching VTs does not.

[Jeremy Jongsma (jeremy-jongsma)]

Switching VTs has no effect, tried several times just now. Killing the unity-panel-service resolved it again. I usually have to kill -9 it, then a new one respawns, then I kill that one normally, and the lock screen generally reappears then.

I'll install today's driver update and recheck next time it occurs.

[Jeremy Jongsma (jeremy-jongsma)]

I was hopeful, it worked great a few times in a row, but as I was about to call it fixed it came back. This time the desktop was visible instead of black, but again I couldn't interact with anything.

Killing unity-panel-service was the solution again. I reported this here because I saw a lot of similar reports on the intel driver from previous Ubuntu releases, but I'm beginning to wonder if it's a Unity issue.

[Chris Wilson (ickle)]

Hmm. Can you attach a new Xorg.0.log? Next time it freezes, gdb --pid `pidof unity-panel-server` and type "bt" -- and please paste the output.

[Chris Wilson (ickle)]

Also worth attaching a dmesg from after the freeze just in case there is anything interesting there as well.

[Marco Trevisan (Treviño) (3v1n0)]

Mh... Did you ever click on an indicator before/after suspend (like to suspend when the losckreen was there)?

[Jeremy Jongsma (jeremy-jongsma)]

I forgot the gdb command until after I unfroze it again. Xorg and dmesg attached.

[Jeremy Jongsma (jeremy-jongsma)]

Got GDB this time. Attached.

[Jeremy Jongsma (jeremy-jongsma)]

Marco: no panel clicking is usually involved. All I need to do to reproduce it is close my laptop lid. Sometimes the first suspend cycle works fine, but in that case repeating it a second time always reproduces this issue.

[Robert Hooker (sarvatt)]

going to need the output of running dmesg, not /var/log/dmesg to see what happens here please. alternatively /var/log/kern.log :)

[Jeremy Jongsma (jeremy-jongsma)]

Dmesg output attached.

[goaspy (goa-spy)]

Hi, I have a similar issue with my Kubuntu 14.10 running on my HTPC (Celeron with Bay Trail graphics)

Ever since upgrading to xserver-xorg-video-intel:amd64 (2.99.914-1~exp1ubuntu4.1, 2.99.914-1~exp1ubuntu4.2) on 07.02.2015, whenever I power off the TV, the screen goes black when I turn it back on. Even if it's just a few seconds later.

I have to log in remotely and restart mdm.

I've updated the driver from 1.3.2 to 1.4.0 (with intel graphics installer) but no luck, same outcome.

Please help. Thanks.

[Alberto Salvia Novella (es20490446e)]

Please.
  1. Report to <https://bugs.freedesktop.org/>.
  2. Paste the new report URL here.
  3. Set this bug status back to "confirmed".

Thank you.

[Hans Korstens (hans.korstens)]

As a follower and affected user by this bug, the workflow is unclear to me. Is Jeremy Jongsma asked to file a report upstream, or Job as assignee?

In the meantime the importance has been reduced from critical to medium, and status from confirmed to incomplete. These changes in status probably means it will go down in priority and become more elusive, despite Jeremy having provided all sorts of logs and info.

I'd be willing to do additional testing/logging if needed.

So: who's got the ball on this issue?

[Hans Korstens (hans.korstens)]

For me killing unity-panel-service as a last resort doesn't work (anymore).
I am sometimes, but not always, lucky by preforming these voodoo steps:
1) switch to a VT (text terminal, e.g. CTRL-ALT-F1), log in and type "startx".
2) It starts another X session, and asks for a password ("authentication is required to change your own userdata"). Just press ESC a few times, and you end up with an empty, unusable desktop. You can't do much here.
3) Now switch back to the VT (again CTRL-ALT-F1) and press CTRL-C, which kills the new X session.
4) press CTRL-ALT-F7 to switch back to the original (black-screen) X session, which hopefully snapped out of blackness by the above steps.

This bug is causing data loss much of the time, as it prevents accessing all your open apps and documents after suspending/resuming.

[Nikke (nmellegard)]

Yes, "voodoo" is a good description of the workarounds I use to get back to a semi-usable desktop (mainly to be able to save any work).

I usually switch to a VT and issue permutations of the following commands (some combination often, but not always, works):
$> killall -9 unity
$> unity --replace
$> killall -9 unity-panel-service
$> xrandr --display :0.0 -q
$> xrandr --display :0.0 --auto

/N

[goaspy (goa-spy)]

I've created a script to switch to VT1 and back, made it executable, made it so it doesn't ask for password, then I've assigned a keyboard shortcut to run 'sudo my_script'.

#! /bin/bash
# fix black screen

gvt=$(fgconsole)

chvt 1;
sleep 2;
chvt $gvt

exit 0

I can run this on my HTPC with the press of a button on the remote.

This works most of the times, and when this is not working I have a second script that restarts mdm.

At least I don't have to worry about unsaved data, this is only an entertainment environment.

Now my wife can use the system :)

[Hans Korstens (hans.korstens)]

It's not a proper solution, but upgrading to Ubuntu 15.04 might help. I've upgraded (in place) more than a week ago, and haven't seen the black-screen-on-resume issue yet on my Lenovo Y2P.

[Hans Korstens (hans.korstens)]

And strike that ^ , just had my first black screen on 15.04 too.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christopher M. Penalver (penalvch)]

Jeremy Jongsma, thank you for reporting this bug to Ubuntu. Utopic reached EOL on July 23, 2015.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this reproducible in a supported release?

[Kai Petzke (petzke)]

I have this same problem sometimes with Kubuntu 15.10 on a Lenovo Yoga 2 13.3 on resume from suspend-to-RAM. In that frozen state, I cannot swap to VT-1 though, with Kubuntu. So I just see a black screen with a frozen mouse pointer. This happens once in every 10 to 20 resumes.

[Kai Petzke (petzke)]

I don't know, if this one helps, or is even a correct additional info: I believe, that this freeze here (blank screen with just mouse pointer) happens, when I touch the touchscreen during the initial parts of the resume process. I've learned to keep my fingers off the screen directly after resume, and it seems, that since then, this problem has been less often.

[Christopher M. Penalver (penalvch)]

Kai Petzke, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Kai Petzke (petzke)]

@Christopher:
I've filed a complete bug report from the command line for another issue, that I have with suspend / resume as Bug #1517950. Do you already have the required information there or do you need more data?

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]