Sometimes no display output on resume from suspend

[Mark O'Donovan]

I updated to the hwe (4.8) from 4.4 because I was suffering from the bug where sometimes lots of text is missing after suspend.

That no longer happens but now I sometimes get a blank screen when resuming.
I can ssh into the system and have tried further suspends and resumes but this does not fix the issue.
A reboot always fixes the issue

My machine is a Dell Precision T1700.
I recently updated the BIOS to try and fix this issue but it has not made any difference.

Dmesg output:
[29905.272499] PM: Syncing filesystems ... done.
[29905.959041] PM: Preparing system for sleep (mem)
[29905.959190] Freezing user space processes ... (elapsed 0.001 seconds) done.
[29905.960837] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds)
[29905.960894] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[29905.962044] PM: Suspending system (mem)
[29905.962068] Suspending console(s) (use no_console_suspend to debug)
[29905.962260] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[29905.975259] sd 0:0:0:0: [sda] Stopping disk
[29905.997555] serial 00:06: disabled
[29905.997558] serial 00:06: System wakeup disabled by ACPI
[29905.997613] e1000e: EEE TX LPI TIMER: 00000011
[29906.669731] PM: suspend of devices complete after 707.633 msecs
[29906.670179] [drm:hsw_write_dcomp [i915]] *ERROR* Failed to write to D_COMP
[29906.689013] PM: late suspend of devices complete after 19.280 msecs
[29906.689670] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[29906.689675] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[29906.689781] e1000e 0000:00:19.0: System wakeup enabled by ACPI
[29906.689910] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[29906.708980] PM: noirq suspend of devices complete after 19.967 msecs
[29906.709307] ACPI: Preparing to enter system sleep state S3
[29906.709518] ACPI Error: Field [PMS1] access width (1 bytes) too large for region [SWCR] (length 0) (20160422/exfldio-190)
[29906.709519] ACPI Error: Field [PMS1] Base+Offset+Width 2+0+1 is beyond end of region [SWCR] (length 0) (20160422/exfldio-205)
[29906.709524] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.SIOS] (Node ffffa077920b8d98), AE_AML_REGION_LIMIT (20160422/psparse-542)
[29906.709526] ACPI Error: Method parse/execution failed [\PTS] (Node ffffa077920c90c8), AE_AML_REGION_LIMIT (20160422/psparse-542)
[29906.709528] ACPI Error: Method parse/execution failed [\_PTS] (Node ffffa077920c6ca8), AE_AML_REGION_LIMIT (20160422/psparse-542)
[29906.709550] PM: Saving platform NVS memory
[29906.709561] Disabling non-boot CPUs ...
[29906.710845] smpboot: CPU 1 is now offline
[29906.726567] smpboot: CPU 2 is now offline
[29906.754513] smpboot: CPU 3 is now offline
[29906.778738] smpboot: CPU 4 is now offline
[29906.801409] Broke affinity for irq 16
[29906.801413] Broke affinity for irq 26
[29906.802419] smpboot: CPU 5 is now offline
[29906.825372] Broke affinity for irq 16
[29906.825376] Broke affinity for irq 26
[29906.825379] Broke affinity for irq 29
[29906.826383] smpboot: CPU 6 is now offline
[29906.849364] Broke affinity for irq 1
[29906.849367] Broke affinity for irq 8
[29906.849369] Broke affinity for irq 9
[29906.849372] Broke affinity for irq 12
[29906.849375] Broke affinity for irq 16
[29906.849378] Broke affinity for irq 23
[29906.849381] Broke affinity for irq 26
[29906.849384] Broke affinity for irq 27
[29906.849386] Broke affinity for irq 29
[29906.850400] smpboot: CPU 7 is now offline
[29906.870598] ACPI: Low-level resume complete
[29906.870648] PM: Restoring platform NVS memory
[29906.871003] Enabling non-boot CPUs ...
[29906.894733] x86: Booting SMP configuration:
[29906.894733] smpboot: Booting Node 0 Processor 1 APIC 0x2
[29906.897258] cache: parent cpu1 should not be sleeping
[29906.897425] CPU1 is up
[29906.922740] smpboot: Booting Node 0 Processor 2 APIC 0x4
[29906.925264] cache: parent cpu2 should not be sleeping
[29906.925449] CPU2 is up
[29906.974764] smpboot: Booting Node 0 Processor 3 APIC 0x6
[29906.977288] cache: parent cpu3 should not be sleeping
[29906.977484] CPU3 is up
[29906.998790] smpboot: Booting Node 0 Processor 4 APIC 0x1
[29907.001318] cache: parent cpu4 should not be sleeping
[29907.001488] CPU4 is up
[29907.022735] smpboot: Booting Node 0 Processor 5 APIC 0x3
[29907.025179] cache: parent cpu5 should not be sleeping
[29907.025363] CPU5 is up
[29907.046748] smpboot: Booting Node 0 Processor 6 APIC 0x5
[29907.049190] cache: parent cpu6 should not be sleeping
[29907.049388] CPU6 is up
[29907.070765] smpboot: Booting Node 0 Processor 7 APIC 0x7
[29907.073203] cache: parent cpu7 should not be sleeping
[29907.073520] CPU7 is up
[29907.084606] ACPI: Waking up from system sleep state S3
[29907.084884] ACPI Error: Field [PMS1] access width (1 bytes) too large for region [SWCR] (length 0) (20160422/exfldio-190)
[29907.084885] ACPI Error: Field [PMS1] Base+Offset+Width 2+0+1 is beyond end of region [SWCR] (length 0) (20160422/exfldio-205)
[29907.084888] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.SIOW] (Node ffffa077920b87a8), AE_AML_REGION_LIMIT (20160422/psparse-542)
[29907.084890] ACPI Error: Method parse/execution failed [\WAK] (Node ffffa077920c9de8), AE_AML_REGION_LIMIT (20160422/psparse-542)
[29907.084892] ACPI Error: Method parse/execution failed [\_WAK] (Node ffffa077920c6ac8), AE_AML_REGION_LIMIT (20160422/psparse-542)
[29907.084894] ACPI Exception: AE_AML_REGION_LIMIT, While executing method \_WAK (20160422/hwesleep-83)
[29907.090735] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[29907.090739] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
[29907.090759] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[29907.102676] PM: noirq resume of devices complete after 17.772 msecs
[29907.103027] PM: early resume of devices complete after 0.298 msecs
[29907.103093] e1000e 0000:00:19.0: System wakeup disabled by ACPI
[29907.103200] rtc_cmos 00:02: System wakeup disabled by ACPI
[29907.103430] sd 0:0:0:0: [sda] Starting disk
[29907.103914] ACPI Error: Field [DRQL] at 144 exceeds Buffer [NULL] size 128 (bits) (20160422/dsopcode-236)
[29907.103916] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.SIO1.DSRS] (Node ffffa077920b6b40), AE_AML_BUFFER_LIMIT (20160422/psparse-542)
[29907.103919] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.UAR1._SRS] (Node ffffa077920b8d20), AE_AML_BUFFER_LIMIT (20160422/psparse-542)
[29907.103921] serial 00:06: activation failed
[29907.103924] dpm_run_callback(): pnp_bus_resume+0x0/0x90 returns -5
[29907.103925] PM: Device 00:06 failed to resume: error -5
[29907.429402] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[29907.433462] ata2.00: configured for UDMA/100
[29907.453368] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[29907.454479] ata1.00: configured for UDMA/133
[29908.838144] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[29908.838147] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[29910.072064] PM: resume of devices complete after 2969.383 msecs
[29910.072336] PM: Finishing wakeup.
[29910.072337] Restarting tasks ...
[29910.072646] usb 1-1.5: USB disconnect, device number 3
[29910.091426] done.
[29910.091664] video LNXVIDEO:00: Restoring backlight state
[29915.935589] e1000e: eth0 NIC Link is Down
[29915.989389] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[29916.193032] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[29917.743997] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[29917.744001] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[29917.744038] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 21 08:25:11 2017
InstallationDate: Installed on 2015-06-04 (747 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcEnviron:
 LANGUAGE=en_IE:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: Upgraded to xenial on 2016-08-17 (307 days ago)

[Mark O'Donovan (shiftee)]

After rebooting with this issue yesterday morning and suspending yesterday evening it happened again this morning.

Dmesg had a more striking error however:
[31636.033162] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc ffff8cc088276000 when fb was deleted
[31636.033176] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable plane with busy fb

[Mark O'Donovan (shiftee)]

Happened again today.
This time I did not get the dmesg error from previous comment.

I am maintaining these logfiles if anyone's interested

[Mark O'Donovan (shiftee)]

Happened again today.
I am using this machine on a Mon-Fri 9-5 basis so will report each day it fails for now.

I am however considering switching to the hwe-edge kernel

[Mark O'Donovan (shiftee)]

Happened again today.

As I do not see a pattern I will stop reporting it

[Mark O'Donovan (shiftee)]

I have worked around this issue by using instructions online to enable hibernate and replace suspend on the menu with hibernate.

This issue occurred a total of 23 times up to kernel 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02

[Martin Dünkelmann (nc-duenkekl3-deactivatedaccount)]

Hibernate is not Suspend and may damage SSD storages because of the heavy using of flash cells.

[jamina1 (jamina1)]

I have this same issue, but the solution of switching to hibernate does not work on my machine

sudo pm-hibernate results in a full shutdown and sudo pm-suspend-hybrid crashes bluetooth until a subsequent restart.

I am on kernel 4.4.0-109-generic

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1699436

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.

[Mark O'Donovan (shiftee)]

I've actually been using suspend again recently with no issues.
Are other people still having these issues?

[Launchpad Janitor (janitor)]

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