[Dell Latitude D420] Black screen after resuming from suspend

Bug #1327110 reported by Anders Sjölander
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

When resuming from suspend I get a black screen, not possible to get back to X without restarting the computer. CTRL-ALT-F1 gets me a terminal window but I can't be bothered to find out how to restart X these days, it's easier just to restart the computer.

WORKAROUND: Disable requirement for password on resume, and suspend via the GUI.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thezood 1845 F.... pulseaudio
Date: Fri Jun 6 10:31:38 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2fa0e036-da9b-4bdd-93e6-e13acc75ccbd
InstallationDate: Installed on 2013-11-07 (210 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: Dell Inc. Latitude D420
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en
 TERM=xterm
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=97bb6bfe-9f2e-40a0-9cd0-cc8b747c8e30 ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-27-generic N/A
 linux-backports-modules-3.13.0-27-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-06-02 (3 days ago)
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.asset.tag: SELULT2355
dmi.board.name: 0TJ984
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: SELULT2355
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.

Revision history for this message
Anders Sjölander (thezood) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Anders Sjölander (thezood) wrote : Re: Black screen after resuming from suspend

Installed 3.15.0-031500rc8-generic #201406012235, problem still exists. Subscribing Christopher M. Penalver (penalvch) since he wanted to be informed... Hope this is not presumtious.

tags: added: kernel-bug-exists-upstream-3.15-rc8
Revision history for this message
penalvch (penalvch) wrote :

thezood, thank you for reporting this and helping make Ubuntu better. While booted into http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc8-utopic/ could you please provide the missing information 3) and 4) following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

tags: added: latest-bios-a06
description: updated
summary: - Black screen after resuming from suspend
+ [Dell Latitude D420] Black screen after resuming from suspend
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Anders Sjölander (thezood) wrote :

Output of /proc/acpi/wakeup

Revision history for this message
Anders Sjölander (thezood) wrote :

I did a suspend according to point 4. But resume worked and I couldn't find anything matching the instructions in dmesg.txt.

Revision history for this message
penalvch (penalvch) wrote :

Anders Sjölander, if you do 30 suspend/resume cycles does the problem manifest itself?

Revision history for this message
Anders Sjölander (thezood) wrote :

On the fifth trace suspend I got the picture back on screen but the computer totally froze, not even REISUB would restart it. This is a bit different from when I close the laptop lid because then the computer keeps working but I get a black screen until I restart lightdm. Attached is the dmesg output after that hang, perhaps it can help.

I do find this which seems to be similar to what I'd expect to find according to the resume t race instructions in your link.
[ 2.072557] Magic number: 0:381:403
[ 2.072562] hash matches /home/apw/COD/linux/drivers/base/power/main.c:803
[ 2.072608] power_supply BAT0: hash matches

Revision history for this message
Anders Sjölander (thezood) wrote :

OK, so I think I haven't been totally clear in the description of this bug. Here is some clarification.
- If I do Suspend from the menu and power back on, it works
- If I lock the screen from the menu and unlocks it, it works
- If I close the lid of the laptop, the computer resumes and the username and password dialog appears. But after I have typed in my password, the screen goes black but the computer keeps working. If I restart lightdm, it works

To me this doesn't look like a suspend/resume bug at all.

Revision history for this message
penalvch (penalvch) wrote :

Anders Sjölander, so just to clarify, if you suspend from the menu in the default kernel, you don't have a black screen?

Revision history for this message
Anders Sjölander (thezood) wrote :

That is true. And it happens after I type my password to unlock the computer. I tried turning off password lock during suspend in the power options and then it works. So the problem only happens when the computer resumes from suspend after the laptop lid has been closed and screen is locked.

penalvch (penalvch)
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Test with newer development kernel (3.13.0-24.46)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.13.0-24.46
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.