Screen remains black after resume from hibernation

Bug #1554509 reported by Yann Salmon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hibernation does not work properly. I ran sudo pm-hibernate, then rebooted.
The hibernation part itself seems to work nice.

Resuming presents the following behaviour:
 - the booting sequence starts
 - the console shows the progress of the resuming process (10%, 20%, etc.)
 - my monitor switches to graphical mode like I would expect, but it then remains black instead of showing my desktop. It does not go to "sleep mode" like it does when the computer is off or the DVI cable is disconnected.

The computer remains responsive, and if music was playing when hibernation started, it properly resumes. I can also use the keyboard (to run sudo reboot now, for example). Switching to another virtual console (Ctrl+Alt+1, Ctrl+Alt+7) does not improve the situation.

WORKAROUND: Use kernel parameter:
nomodeset

---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: yann 1556 F.... pulseaudio
 /dev/snd/controlC0: yann 1556 F.... pulseaudio
 /dev/snd/controlC1: yann 1556 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=574e9971-0906-47a9-9936-a1c6749b0d90
InstallationDate: Installed on 2016-03-06 (5 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
IwConfig:
 enp0s25 no wireless extensions.

 lo no wireless extensions.
MachineType: Dell Inc. Precision T1600
Package: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=fr_FR
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic root=UUID=93ce274f-fa99-4a90-9081-7e70aeec5d83 ro
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
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-4.4.0-11-generic N/A
 linux-backports-modules-4.4.0-11-generic N/A
 linux-firmware 1.156
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: xenial xenial
Uname: Linux 4.4.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/24/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 06NWYK
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/24/2013:svnDellInc.:pnPrecisionT1600:pvr01:rvnDellInc.:rn06NWYK:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision T1600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Yann Salmon (yannsalmon)
description: updated
Revision history for this message
Yann Salmon (yannsalmon) wrote :

After upgrading packages (and kernel to 4.4.0-11-generic), the problem persists.

However, there seems to be a workaround : booting with the nomodeset option allows to hibernate and resume properly.

Revision history for this message
Yann Salmon (yannsalmon) wrote :

It appears that booting with nomodeset prevents the radeon video driver to load, so this driver may be the cause of the problem.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

it's a kernel bug then

affects: pm-utils (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1554509

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Yann Salmon (yannsalmon) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Yann Salmon (yannsalmon) wrote : CRDA.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : Dependencies.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : JournalErrors.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : Lspci.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : Lsusb.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : ProcModules.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : UdevDb.txt

apport information

Revision history for this message
Yann Salmon (yannsalmon) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 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'.

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.5-rc7-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Yann Salmon (yannsalmon)
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Yann Salmon (yannsalmon) wrote :

Hibernation and resuming from it works fine with TuxOnIce (kernel 4.4.0-18-generic-tuxonice). This may help you find out what is causing the problem with the default hibernation process.

Revision history for this message
penalvch (penalvch) wrote :

YS1:
1) Did this issue not occur in a Ubuntu release prior to 16.04?
2) To keep this relevant to upstream, could you please test the latest mainline kernel (4.7-rc5) and advise to the results?

no longer affects: xserver-xorg-video-ati (Ubuntu)
description: updated
tags: added: kernel-bug-exists-upstream-4.5-rc7
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Yann Salmon (yannsalmon) wrote :

1) Comparison is difficult because I seldom use non-tuxonice kernels and I was using the proprietary drivers for my graphic card with XUbuntu 14.04 (not now anymore).

2) I tired with 4.7-rc6 : it works ! A violet line appeared for less than a second (which does not happen with 4.4.0-28-generic-tuxonice), but normal operation immediately resumed.

Revision history for this message
penalvch (penalvch) wrote :

YS1, to clarify, with 4.7-rc6, you hibernated, and then without any intervention, it immediately resumed from hibernation?

Revision history for this message
Yann Salmon (yannsalmon) wrote :

No, the hibernation takes place correctly and shuts the computer down.
As I restarted it, resuming worked correctly except for the transient graphical glitch.

On a side note, yesterday evening my graphics card produced more and more glitches and then simply crashed (it is to be replaced ; computer does not boot with it anymore). So the violet line glitch I mentioned earlier may just have been the beginning of that, and be not related to the hibernation cycle at all.

Revision history for this message
penalvch (penalvch) wrote :

YS1, given you have hardware failure, let this report be closed. However, if you have an issue with the new/modified setup, please file a new report.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.