[SOLVED] No display after waking up from sleep

ansh_kumar · 2014-04-15 17:56:41

After my laptop resumes from sleep , I'm left without any display. I tried pm-utils and s2ram also, all failed. But the laptop is working fine behind the screen as I can use ctrl+alt+f1 to switch to the console(but without any display). I'm sure of this because I then use ctrl+alt+del to restart my laptop. After the restart I'm able to get the display back. I'm using kde with linux 3.13.6-1.

Last edited by ansh_kumar (2014-09-06 07:33:30)

Pse · 2014-04-17 14:12:00

What happens if you press the brightness keys? (Assuming they work before entering sleep).

Last edited by Pse (2014-04-17 14:12:19)

ansh_kumar · 2014-04-18 07:48:23

Nothing...
It's like the LED lid is out of power and comes to life only after a reboot.

ansh_kumar · 2014-04-22 03:00:55

I've updated my system but still facing the same problem. Also my wifi/bluetooth gets started after waking from sleep, which were off before sleep. Don't no why.

ansh_kumar · 2014-04-22 08:05:36

After my laptop resumes from sleep , I'm left without any display. I tried pm-utils and s2ram also, all failed. But the laptop is working fine behind the screen as I can use ctrl+alt+f1 to switch to the console(but without any display). I'm sure of this because I then use ctrl+alt+del to restart my laptop. After the restart I'm able to get the display back. I'm using kde with linux 3.13.6-1. Here is the systemctl log:

-- Logs begin at Sat 2014-03-22 04:06:01 IST, end at Tue 2014-04-22 13:21:08 IST. --
Apr 22 13:19:51 ansh systemd[1]: Starting Sleep.
Apr 22 13:19:51 ansh systemd[1]: Reached target Sleep.
Apr 22 13:19:51 ansh systemd[1]: Starting Suspend...
Apr 22 13:19:51 ansh systemd-sleep[316]: Suspending system...
Apr 22 13:19:51 ansh kernel: PM: Syncing filesystems ... done.
Apr 22 13:19:51 ansh kernel: PM: Preparing system for mem sleep
Apr 22 13:19:57 ansh kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Apr 22 13:19:57 ansh kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Apr 22 13:19:57 ansh kernel: PM: Entering mem sleep
Apr 22 13:19:57 ansh kernel: Suspending console(s) (use no_console_suspend to debug)
Apr 22 13:19:57 ansh kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: WB enabled
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800a9f06c00
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800a9f06c0c
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90006cb2118
Apr 22 13:19:57 ansh kernel: [drm] ring test on 0 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 5 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] UVD initialized successfully.
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 5 succeeded
Apr 22 13:19:57 ansh kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 22 13:19:57 ansh kernel: sd 0:0:0:0: [sda] Stopping disk
Apr 22 13:19:57 ansh kernel: i8042 aux 00:07: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: i8042 kbd 00:06: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: PM: suspend of devices complete after 488.398 msecs
Apr 22 13:19:57 ansh kernel: PM: late suspend of devices complete after 0.271 msecs
Apr 22 13:19:57 ansh kernel: pcieport 0000:00:15.1: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:14.5: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:13.2: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:13.0: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:12.2: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:12.0: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.1: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.0: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: PM: noirq suspend of devices complete after 81.005 msecs
Apr 22 13:19:57 ansh kernel: ACPI: Preparing to enter system sleep state S3
Apr 22 13:19:57 ansh kernel: PM: Saving platform NVS memory
Apr 22 13:19:57 ansh kernel: Disabling non-boot CPUs ...
Apr 22 13:19:57 ansh kernel: kvm: disabling virtualization on CPU1
Apr 22 13:19:57 ansh kernel: smpboot: CPU 1 is now offline
Apr 22 13:19:57 ansh kernel: kvm: disabling virtualization on CPU2
Apr 22 13:19:57 ansh kernel: smpboot: CPU 2 is now offline
Apr 22 13:19:57 ansh kernel: kvm: disabling virtualization on CPU3
Apr 22 13:19:57 ansh kernel: smpboot: CPU 3 is now offline
Apr 22 13:19:57 ansh kernel: ACPI: Low-level resume complete
Apr 22 13:19:57 ansh kernel: PM: Restoring platform NVS memory
Apr 22 13:19:57 ansh kernel: LVT offset 0 assigned for vector 0x400
Apr 22 13:19:57 ansh kernel: [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu
Apr 22 13:19:57 ansh kernel: [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc000000001000000)
Apr 22 13:19:57 ansh kernel: microcode: CPU0: new patch_level=0x06001119
Apr 22 13:19:57 ansh kernel: Enabling non-boot CPUs ...
Apr 22 13:19:57 ansh kernel: x86: Booting SMP configuration:
Apr 22 13:19:57 ansh kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Apr 22 13:19:57 ansh kernel: kvm: enabling virtualization on CPU1
Apr 22 13:19:57 ansh kernel: CPU1 is up
Apr 22 13:19:57 ansh kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Apr 22 13:19:57 ansh kernel: kvm: enabling virtualization on CPU2
Apr 22 13:19:57 ansh kernel: microcode: CPU2: new patch_level=0x06001119
Apr 22 13:19:57 ansh kernel: CPU2 is up
Apr 22 13:19:57 ansh kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Apr 22 13:19:57 ansh kernel: kvm: enabling virtualization on CPU3
Apr 22 13:19:57 ansh kernel: CPU3 is up
Apr 22 13:19:57 ansh kernel: ACPI: Waking up from system sleep state S3
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.0: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.1: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:12.0: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:12.2: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:13.0: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:13.2: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:14.5: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: PM: noirq resume of devices complete after 118.040 msecs
Apr 22 13:19:57 ansh kernel: PM: early resume of devices complete after 0.193 msecs
Apr 22 13:19:57 ansh kernel: pciehp 0000:00:02.0:pcie04: Card present on Slot(0)
Apr 22 13:19:57 ansh kernel: ath: phy0: ASPM enabled: 0x43
Apr 22 13:19:57 ansh kernel: pcieport 0000:00:15.1: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000000047A000).
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: WB enabled
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800aa1ccc00
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004bb5a18
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04 and cpu addr 0xffff8800aa1ccc04
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08 and cpu addr 0xffff8800aa1ccc08
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800aa1ccc0c
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10 and cpu addr 0xffff8800aa1ccc10
Apr 22 13:19:57 ansh kernel: [drm] ring test on 0 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 3 succeeded in 2 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 4 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: pciehp 0000:00:02.0:pcie04: Device 0000:01:00.0 already exists at 0000:01:00, cannot hot-add
Apr 22 13:19:57 ansh kernel: pciehp 0000:00:02.0:pcie04: Cannot add device at 0000:01:00
Apr 22 13:19:57 ansh kernel: [drm] ring test on 5 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] UVD initialized successfully.
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 5 succeeded
Apr 22 13:19:57 ansh kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: WB enabled
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800a9f06c00
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800a9f06c0c
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90006cb2118
Apr 22 13:19:57 ansh kernel: [drm] ring test on 0 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: usb 1-3: reset high-speed USB device number 2 using ehci-pci
Apr 22 13:19:57 ansh kernel: i8042 kbd 00:06: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: [drm] ring test on 5 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] UVD initialized successfully.
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 5 succeeded
Apr 22 13:19:57 ansh kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 22 13:19:57 ansh kernel: ata1.00: configured for UDMA/100
Apr 22 13:19:57 ansh kernel: sd 0:0:0:0: [sda] Starting disk
Apr 22 13:19:57 ansh kernel: ata2.00: configured for UDMA/100
Apr 22 13:19:57 ansh kernel: PM: resume of devices complete after 1093.473 msecs
Apr 22 13:19:57 ansh kernel: PM: Finishing wakeup.

Rexilion · 2014-04-23 06:42:55

Looks like a backlight issue. Does your kernel log end where the log you posted end as well? No additional errors and such?

mserrano · 2014-04-23 15:44:49

Same problem here. Since last Arch update (yesterday or this morning, I could not tell) my Dell E6230 running Linux 3.14.1 is no longer able to wake up the Display Port output aftre hibernate. The machine is up, as I can access the console when I open the lid and press Ctrl-Fn F4. t least I can then reboot it properply.

WonderWoofy · 2014-04-23 17:16:39

https://bbs.archlinux.org/viewtopic.php?id=57855

mserrano · 2014-04-24 04:40:11

Sure, you are right. Providing a log is definitively needed but since the switch to systemd I'm just unable to find these informations anymore. Journalctl -??? never gives anything useful for me. I just don't know where to look at. This is also probably the reason
why suspend-to-disk has stopped working for me many months ago and I have no clue how to fix the problem. After an hibernation to disk, the machine no longer boots (the led blinks). Where do you find any log. If you tell me where to find them, I will be glad providing
this information.

In that particular case, reporting that at least two people faced the same problem since the last arch update, was, by itself, a valuable information.

ansh_kumar · 2014-04-24 05:21:57

here my Journalctl log after suspend and wake up

-- Logs begin at Sat 2014-03-22 04:06:01 IST, end at Tue 2014-04-22 13:21:08 IST. --
Apr 22 13:19:51 ansh systemd[1]: Starting Sleep.
Apr 22 13:19:51 ansh systemd[1]: Reached target Sleep.
Apr 22 13:19:51 ansh systemd[1]: Starting Suspend...
Apr 22 13:19:51 ansh systemd-sleep[316]: Suspending system...
Apr 22 13:19:51 ansh kernel: PM: Syncing filesystems ... done.
Apr 22 13:19:51 ansh kernel: PM: Preparing system for mem sleep
Apr 22 13:19:57 ansh kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Apr 22 13:19:57 ansh kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Apr 22 13:19:57 ansh kernel: PM: Entering mem sleep
Apr 22 13:19:57 ansh kernel: Suspending console(s) (use no_console_suspend to debug)
Apr 22 13:19:57 ansh kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: WB enabled
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800a9f06c00
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800a9f06c0c
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90006cb2118
Apr 22 13:19:57 ansh kernel: [drm] ring test on 0 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 5 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] UVD initialized successfully.
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 5 succeeded
Apr 22 13:19:57 ansh kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 22 13:19:57 ansh kernel: sd 0:0:0:0: [sda] Stopping disk
Apr 22 13:19:57 ansh kernel: i8042 aux 00:07: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: i8042 kbd 00:06: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: PM: suspend of devices complete after 488.398 msecs
Apr 22 13:19:57 ansh kernel: PM: late suspend of devices complete after 0.271 msecs
Apr 22 13:19:57 ansh kernel: pcieport 0000:00:15.1: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:14.5: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:13.2: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:13.0: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:12.2: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:12.0: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.1: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.0: System wakeup enabled by ACPI
Apr 22 13:19:57 ansh kernel: PM: noirq suspend of devices complete after 81.005 msecs
Apr 22 13:19:57 ansh kernel: ACPI: Preparing to enter system sleep state S3
Apr 22 13:19:57 ansh kernel: PM: Saving platform NVS memory
Apr 22 13:19:57 ansh kernel: Disabling non-boot CPUs ...
Apr 22 13:19:57 ansh kernel: kvm: disabling virtualization on CPU1
Apr 22 13:19:57 ansh kernel: smpboot: CPU 1 is now offline
Apr 22 13:19:57 ansh kernel: kvm: disabling virtualization on CPU2
Apr 22 13:19:57 ansh kernel: smpboot: CPU 2 is now offline
Apr 22 13:19:57 ansh kernel: kvm: disabling virtualization on CPU3
Apr 22 13:19:57 ansh kernel: smpboot: CPU 3 is now offline
Apr 22 13:19:57 ansh kernel: ACPI: Low-level resume complete
Apr 22 13:19:57 ansh kernel: PM: Restoring platform NVS memory
Apr 22 13:19:57 ansh kernel: LVT offset 0 assigned for vector 0x400
Apr 22 13:19:57 ansh kernel: [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for vector 0xf9, but the register is already in use for vector 0x400 on another cpu
Apr 22 13:19:57 ansh kernel: [Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc000000001000000)
Apr 22 13:19:57 ansh kernel: microcode: CPU0: new patch_level=0x06001119
Apr 22 13:19:57 ansh kernel: Enabling non-boot CPUs ...
Apr 22 13:19:57 ansh kernel: x86: Booting SMP configuration:
Apr 22 13:19:57 ansh kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Apr 22 13:19:57 ansh kernel: kvm: enabling virtualization on CPU1
Apr 22 13:19:57 ansh kernel: CPU1 is up
Apr 22 13:19:57 ansh kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Apr 22 13:19:57 ansh kernel: kvm: enabling virtualization on CPU2
Apr 22 13:19:57 ansh kernel: microcode: CPU2: new patch_level=0x06001119
Apr 22 13:19:57 ansh kernel: CPU2 is up
Apr 22 13:19:57 ansh kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Apr 22 13:19:57 ansh kernel: kvm: enabling virtualization on CPU3
Apr 22 13:19:57 ansh kernel: CPU3 is up
Apr 22 13:19:57 ansh kernel: ACPI: Waking up from system sleep state S3
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.0: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: xhci_hcd 0000:00:10.1: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:12.0: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:12.2: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:13.0: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ehci-pci 0000:00:13.2: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: ohci-pci 0000:00:14.5: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: PM: noirq resume of devices complete after 118.040 msecs
Apr 22 13:19:57 ansh kernel: PM: early resume of devices complete after 0.193 msecs
Apr 22 13:19:57 ansh kernel: pciehp 0000:00:02.0:pcie04: Card present on Slot(0)
Apr 22 13:19:57 ansh kernel: ath: phy0: ASPM enabled: 0x43
Apr 22 13:19:57 ansh kernel: pcieport 0000:00:15.1: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000000047A000).
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: WB enabled
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff8800aa1ccc00
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004bb5a18
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04 and cpu addr 0xffff8800aa1ccc04
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08 and cpu addr 0xffff8800aa1ccc08
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff8800aa1ccc0c
Apr 22 13:19:57 ansh kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10 and cpu addr 0xffff8800aa1ccc10
Apr 22 13:19:57 ansh kernel: [drm] ring test on 0 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 3 succeeded in 2 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 4 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: pciehp 0000:00:02.0:pcie04: Device 0000:01:00.0 already exists at 0000:01:00, cannot hot-add
Apr 22 13:19:57 ansh kernel: pciehp 0000:00:02.0:pcie04: Cannot add device at 0000:01:00
Apr 22 13:19:57 ansh kernel: [drm] ring test on 5 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] UVD initialized successfully.
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 5 succeeded
Apr 22 13:19:57 ansh kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: WB enabled
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800a9f06c00
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800a9f06c0c
Apr 22 13:19:57 ansh kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90006cb2118
Apr 22 13:19:57 ansh kernel: [drm] ring test on 0 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] ring test on 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: usb 1-3: reset high-speed USB device number 2 using ehci-pci
Apr 22 13:19:57 ansh kernel: i8042 kbd 00:06: System wakeup disabled by ACPI
Apr 22 13:19:57 ansh kernel: [drm] ring test on 5 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: [drm] UVD initialized successfully.
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 3 succeeded in 1 usecs
Apr 22 13:19:57 ansh kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 22 13:19:57 ansh kernel: [drm] ib test on ring 5 succeeded
Apr 22 13:19:57 ansh kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 22 13:19:57 ansh kernel: ata1.00: configured for UDMA/100
Apr 22 13:19:57 ansh kernel: sd 0:0:0:0: [sda] Starting disk
Apr 22 13:19:57 ansh kernel: ata2.00: configured for UDMA/100
Apr 22 13:19:57 ansh kernel: PM: resume of devices complete after 1093.473 msecs
Apr 22 13:19:57 ansh kernel: PM: Finishing wakeup.

It looks like it's an open source driver issue.
I've not tested it with proprietary drivers yet.
Moreover when I use the following in pm-utils

DISPLAY=:0 xgamma -gamma 1.0

I get the following error in pm-suspend log

Running hook /usr/lib/pm-utils/sleep.d/80_display resume suspend:
xgamma:  unable to open display ':0'

Last edited by ansh_kumar (2014-04-24 05:32:55)

ansh_kumar · 2014-04-24 05:30:37

No the log file was way to big to post here. But after the end of this log restart log gets started. I don't think that's of any use. Moreover I think it's an open-source driver issue (xf86-video-ati) because when I use the following in pm-utils

DISPLAY=:0 xgamma -gamma 1.0

I get the following error in pm-suspend log

Running hook /usr/lib/pm-utils/sleep.d/80_display resume suspend:
xgamma:  unable to open display ':0'

Last edited by ansh_kumar (2014-04-24 05:33:09)

jasonwryan · 2014-04-24 06:09:08

Please don't crosspost: https://wiki.archlinux.org/index.php/Fo … ss-Posting

Merging...

ansh_kumar · 2014-09-06 07:26:12

Finally found a working solution. Installed pm-utils and created the file /etc/pm/config.d/radeon with the following contents:

QUIRK_S3_BIOS="true"
QUIRK_S3_MODE="true"

Added the following using the command visudo

user ALL = NOPASSWD: /usr/sbin/pm-suspend

Replace the user with the username. Then created /etc/systemd/system/systemd-suspend.service with the following contents

[Unit]
Description=Suspend
Documentation=man:systemd-suspend.service(8)
DefaultDependencies=no
Requires=sleep.target
After=sleep.target

[Service]
Type=oneshot
ExecStart=
ExecStart=/usr/bin/pm-suspend

But still don't know what was the problem?

Rexilion · 2014-09-06 10:19:26

Those quirks are probably the solution. You should figure out whether you need them both and then figure out what the quirk actually does. Then we can proceed to a definitive fix.

Nice digging though ...

ansh_kumar · 2014-09-06 12:31:04

I need both the quirks for suspend to work. (tested it)

Rexilion · 2014-09-06 14:58:39

sysctl -w kernel.acpi_video_flags=3

Should provide the same effect and would allow you to s2disk without pm-utils. You just need to stick it in systemd's boot sequence somewhere.

But test it first!

ansh_kumar · 2014-09-06 17:15:46

not working ...

Rexilion · 2014-09-06 21:39:21

Did you confirm the sysctl works as intended? I looked this up in the pm-utils source ...

ansh_kumar · 2014-09-07 04:36:34

Before setting the custom value sysctl -a | grep kernel.acpi_video_flags gives:

kernel.acpi_video_flags = 0

After setting the value with sysctl -w kernel.acpi_video_flags=3 it gives

kernel.acpi_video_flags = 3

So sysctl is working as intended.

Rexilion · 2014-09-07 06:32:50

Could you perform the command and then to hibernate, do the following:

echo disk > /sys/power/state

as root? This is the most simplest form of hibernation initiated directly from the kernel. I'm getting the feeling that systemd is putting his own value's in there as well.

ansh_kumar · 2014-09-07 10:07:51

Actually I want to suspend the session(sleep) not hibernate.

Last edited by ansh_kumar (2014-09-07 10:08:57)

Rexilion · 2014-09-07 13:09:22

Sorry for the confusion. In Windows XP, suspending = hibernating. In Linux it's also called hibernate from the kernel (or suspend to disk).

ansh_kumar · 2014-09-07 13:19:56

So what about quirks? What they do and most importantly how can I fix my problem without using pm-utils ?

Rexilion · 2014-09-07 14:52:57

You mentioned that the above quirks in pm-utils fix your issue. The command I gave you is the command that is executed when these two quirks are enabled. If those 2 quirks in pm-utils really fix it, then so should the command. Did you try my latest recommendation yet?

ansh_kumar · 2014-09-07 15:44:01

Yes you were right doing the following worked:

sysctl -w kernel.acpi_video_flags=3
echo mem > /sys/power/state

Arch Linux

#1 2014-04-15 17:56:41

[SOLVED] No display after waking up from sleep

#2 2014-04-17 14:12:00

Re: [SOLVED] No display after waking up from sleep

#3 2014-04-18 07:48:23

Re: [SOLVED] No display after waking up from sleep

#4 2014-04-22 03:00:55

Re: [SOLVED] No display after waking up from sleep

#5 2014-04-22 08:05:36

Re: [SOLVED] No display after waking up from sleep

#6 2014-04-23 06:42:55

Re: [SOLVED] No display after waking up from sleep

#7 2014-04-23 15:44:49

Re: [SOLVED] No display after waking up from sleep

#8 2014-04-23 17:16:39

Re: [SOLVED] No display after waking up from sleep

#9 2014-04-24 04:40:11

Re: [SOLVED] No display after waking up from sleep

#10 2014-04-24 05:21:57

Re: [SOLVED] No display after waking up from sleep

#11 2014-04-24 05:30:37

Re: [SOLVED] No display after waking up from sleep

#12 2014-04-24 06:09:08

Re: [SOLVED] No display after waking up from sleep

#13 2014-09-06 07:26:12

Re: [SOLVED] No display after waking up from sleep

#14 2014-09-06 10:19:26

Re: [SOLVED] No display after waking up from sleep

#15 2014-09-06 12:31:04

Re: [SOLVED] No display after waking up from sleep

#16 2014-09-06 14:58:39

Re: [SOLVED] No display after waking up from sleep

#17 2014-09-06 17:15:46

Re: [SOLVED] No display after waking up from sleep

#18 2014-09-06 21:39:21

Re: [SOLVED] No display after waking up from sleep

#19 2014-09-07 04:36:34

Re: [SOLVED] No display after waking up from sleep

#20 2014-09-07 06:32:50

Re: [SOLVED] No display after waking up from sleep

#21 2014-09-07 10:07:51

Re: [SOLVED] No display after waking up from sleep

#22 2014-09-07 13:09:22

Re: [SOLVED] No display after waking up from sleep

#23 2014-09-07 13:19:56

Re: [SOLVED] No display after waking up from sleep

#24 2014-09-07 14:52:57

Re: [SOLVED] No display after waking up from sleep

#25 2014-09-07 15:44:01

Re: [SOLVED] No display after waking up from sleep

Board footer