You are not logged in.

#1 2014-07-27 19:55:10

antx
Member
Registered: 2014-07-27
Posts: 2

"Freeze" after wake from suspend?

Hi folks,

Not sure what's the best way to report this, but anyway, here's my issue.

On my Toshiba L300 (x86_64) , whenever I use a version of xf86-video-intel driver newer than 2.99.911-2 (ex: .912-1, .912-2, even .914 from testing!), my graphical interface (Gnome Shell) will freeze when waking up from suspend (closing the lid or "systemctl suspend").

So, it looks like 911-2 does not have the issue, however... weirdly enough, the same bug can also be reproduced by installing the 3.15 kernel, with any version of the intel video driver starting from 2.99.911 (I didn't have any lower version in my pacman cache to test with).

So, to recap:

linux = 3.14 + intel video <= 2.99.911 = wakes up from suspend correctly.
linux = 3.14 + intel video >= 2.99.912 = freeze on wake up
linux 3.15 + intel video >= 2.99.911 freeze on wake up

Another important point is that I'm still able to change TTY with CTRL+ALT+F*.

Any pointers or clues on how to find the source of the problem?

I'm running xorg-server 1.15.2-1 and gnome-shell 3.12.2-1 if that can help.

Offline

#2 2014-07-27 22:48:07

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: "Freeze" after wake from suspend?

I've been experiencing this occasionally as well. I've found that after switching to a VT and then coming back, the screen unfreezes for a second and then freezes again. I usually send SIGTERM to opened apps in X and then reboot through the command-line. I am sure this is related to some change in Intel drivers, but I haven't tried to trace it to any specific commit.

Edit: BTW, this is on Ivy Bridge.

Last edited by Pse (2014-07-27 22:48:55)

Offline

#3 2014-07-29 13:51:36

jorges
Member
Registered: 2011-04-07
Posts: 29

Re: "Freeze" after wake from suspend?

I am having this issue randomly as well. This is with a first generation core i5 cpu and HD Graphics (arrandale processor and ironlake gpu). I've been looking at the systemd journal every time after a crash to try to find the cause, but I am still pretty much clueless. I will try to downgrade the kernel and/or intel driver. To add to the confussion, I was by chance also testing the linux-ck kernel to solve some resposiveness issues with hard drive activity, and at a moment thought that could also be the cause. Any of you are using a non-stock kernel by chance?

Jorge

Offline

#4 2014-07-29 18:07:58

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: "Freeze" after wake from suspend?

Stock kernel, here. I just updated to 3.15.7, xorg-server 1.16 and the latest Intel drivers. Haven't tried to reproduce the problem since then, I'll report here if it happens again.

Last edited by Pse (2014-07-29 18:09:04)

Offline

#5 2014-08-03 09:36:47

detro
Member
From: Bulgaria
Registered: 2014-08-03
Posts: 1
Website

Re: "Freeze" after wake from suspend?

Same issue here. My settings are: closing the lid suspends and locks my laptop(asus x401a). Nowadays every 3rd time i open my lid and type my password I got freeze.

NB: I wonder if this has something to do with it, but I haven't experienced this issue, since I accidentally forgot my presentation mode on(xfce4-power-manager), so maybe upower is involved?

Offline

#6 2014-08-03 17:25:06

Akseli0x61
Member
Registered: 2014-08-01
Posts: 12

Re: "Freeze" after wake from suspend?

I have the same issue but for me it only happens rarely and when I close the lid and open it again it's not frozen anymore. I don't know if it's coincidence with some driver update or something but I think it got much more rare when I switched from xfce to cinnamon.

Offline

#7 2014-08-04 11:07:34

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 413

Re: "Freeze" after wake from suspend?

I, too, have had some fairly unpredictable problems since the upgrade to Linux 3.15

Current install is Linux 3.15.8.1 x86-video-intel 2.99.914-3

"systemctl suspend" seems to work. Closing the laptop lid is set to sleep in KDE4 battery monitor energy savings. Closing the lid sometimes works and sometimes returns with no keyboard input and/or desktop freeze requiring a reboot. In fact I have experienced most of the problems above hat some time or other.

Laptop is HP dm1, intel chipset, cpu: U2300 2-core, video: intel GM45 express, network: Realtek RTL8101E/8102E, Wifi: Broadcom  BCM4312

Andrew

Offline

#8 2014-08-05 04:25:43

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: "Freeze" after wake from suspend?

Reporting back: 3.15.7-1 still failed ocassionally. Now testing 3.15.8-1.

Offline

#9 2014-08-07 16:31:28

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 413

Re: "Freeze" after wake from suspend?

I have this error in the journal:

kernel: [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 7680bbd0 tail 00000000 start 0040b000
kernel: dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -5
kernel: PM: Device 0000:00:02.0 failed to resume async: error -5
kernel: usb 3-1: reset full-speed USB device number 2 using uhci_hcd
kernel: ERROR @wl_wowl_ind_wake_reason : Unable to get wake reason, err = -95

I have no idea what it means :-(

Andrew

Offline

#10 2014-08-08 16:19:41

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: "Freeze" after wake from suspend?

3.15.8 just failed. I don't have enough time to investigate. Still working around it by sending SIGTERM to important apps from a VT, then rebooting by issuing 'systemctl reboot'.

Last edited by Pse (2014-08-08 16:20:27)

Offline

#11 2014-08-09 20:20:40

flamusdiu
Member
Registered: 2013-05-10
Posts: 36

Re: "Freeze" after wake from suspend?

Same issue as [SOLVED]Laptop freezes some time after suspend However, if you look at Post #8 you can resolve it by doing.

 i915.i915_enable_rc6=0 

However, this workaround will cause your laptop to use more battery power.

Offline

#12 2014-08-09 21:28:07

Pse
Member
Registered: 2008-03-15
Posts: 413

Re: "Freeze" after wake from suspend?

Ah, I see. Then there's been a regression in the kernel. RC6 used to work fine with my setup. Thanks for finding that post.

Offline

#13 2014-08-10 07:48:35

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 413

Re: "Freeze" after wake from suspend?

That does not seem to have made much difference here. This does seem to have started with 3.15

Andrew

Offline

#14 2014-08-10 08:17:48

fdservices
Member
From: France
Registered: 2012-02-06
Posts: 413

Re: "Freeze" after wake from suspend?

My journal:

Aug 10 09:34:21 hp-dm1 systemd[1]: Starting Sleep.
Aug 10 09:34:21 hp-dm1 systemd[1]: Reached target Sleep.
Aug 10 09:34:21 hp-dm1 systemd[1]: Starting Suspend...
Aug 10 09:34:21 hp-dm1 systemd-sleep[3645]: Suspending system...
Aug 10 09:36:36 hp-dm1 kernel: PM: Syncing filesystems ... done.
Aug 10 09:36:36 hp-dm1 kernel: PM: Preparing system for mem sleep
Aug 10 09:36:36 hp-dm1 kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Aug 10 09:36:36 hp-dm1 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Aug 10 09:36:36 hp-dm1 kernel: PM: Entering mem sleep
Aug 10 09:36:36 hp-dm1 kernel: Suspending console(s) (use no_console_suspend to debug)
Aug 10 09:36:36 hp-dm1 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 10 09:36:36 hp-dm1 kernel: cfg80211: Calling CRDA to update world regulatory domain
Aug 10 09:36:36 hp-dm1 kernel: i8042 kbd 00:07: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: sd 0:0:0:0: [sda] Stopping disk
Aug 10 09:36:36 hp-dm1 kernel: PM: suspend of devices complete after 593.555 msecs
Aug 10 09:36:36 hp-dm1 kernel: PM: late suspend of devices complete after 13.342 msecs
Aug 10 09:36:36 hp-dm1 kernel: r8169 0000:03:00.0: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: PM: noirq suspend of devices complete after 13.662 msecs
Aug 10 09:36:36 hp-dm1 kernel: ACPI: Preparing to enter system sleep state S3
Aug 10 09:36:36 hp-dm1 kernel: PM: Saving platform NVS memory
Aug 10 09:36:36 hp-dm1 kernel: Disabling non-boot CPUs ...
Aug 10 09:36:36 hp-dm1 kernel: kvm: disabling virtualization on CPU1
Aug 10 09:36:36 hp-dm1 kernel: smpboot: CPU 1 is now offline
Aug 10 09:36:36 hp-dm1 kernel: ACPI: Low-level resume complete
Aug 10 09:36:36 hp-dm1 kernel: PM: Restoring platform NVS memory
Aug 10 09:36:36 hp-dm1 kernel: Enabling non-boot CPUs ...
Aug 10 09:36:36 hp-dm1 kernel: x86: Booting SMP configuration:
Aug 10 09:36:36 hp-dm1 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Aug 10 09:36:36 hp-dm1 kernel: kvm: enabling virtualization on CPU1                                                                                                                            
Aug 10 09:36:36 hp-dm1 kernel: CPU1 is up                                                                                                                                                      
Aug 10 09:36:36 hp-dm1 kernel: ACPI: Waking up from system sleep state S3                                                                                                                      
Aug 10 09:36:36 hp-dm1 kernel: uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI                                                                                                           
Aug 10 09:36:36 hp-dm1 kernel: uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI                                                                                                           
Aug 10 09:36:36 hp-dm1 kernel: uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: PM: noirq resume of devices complete after 13.183 msecs
Aug 10 09:36:36 hp-dm1 kernel: PM: early resume of devices complete after 0.452 msecs
Aug 10 09:36:36 hp-dm1 kernel: sd 0:0:0:0: [sda] Starting disk
Aug 10 09:36:36 hp-dm1 kernel: usb usb3: root hub lost power or was reset
Aug 10 09:36:36 hp-dm1 kernel: usb usb6: root hub lost power or was reset
Aug 10 09:36:36 hp-dm1 kernel: usb usb4: root hub lost power or was reset
Aug 10 09:36:36 hp-dm1 kernel: usb usb5: root hub lost power or was reset
Aug 10 09:36:36 hp-dm1 kernel: snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
Aug 10 09:36:36 hp-dm1 kernel: r8169 0000:03:00.0: System wakeup disabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: usb usb7: root hub lost power or was reset
Aug 10 09:36:36 hp-dm1 kernel: i8042 kbd 00:07: System wakeup disabled by ACPI
Aug 10 09:36:36 hp-dm1 kernel: [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 0000d438 tail 00000000 start 0040b000
Aug 10 09:36:36 hp-dm1 kernel: usb 3-1: reset full-speed USB device number 2 using uhci_hcd
Aug 10 09:36:36 hp-dm1 kernel: dpm_run_callback(): pci_pm_resume+0x0/0xb0 returns -5
Aug 10 09:36:36 hp-dm1 kernel: PM: Device 0000:00:02.0 failed to resume async: error -5
Aug 10 09:36:36 hp-dm1 kernel: ERROR @wl_wowl_ind_wake_reason : Unable to get wake reason, err = -95
Aug 10 09:36:36 hp-dm1 kernel: usb 6-2: reset full-speed USB device number 2 using uhci_hcd
Aug 10 09:36:36 hp-dm1 kernel: usb 2-4: reset high-speed USB device number 2 using ehci-pci
Aug 10 09:36:36 hp-dm1 kernel: PM: resume of devices complete after 2439.529 msecs
Aug 10 09:36:36 hp-dm1 kernel: PM: Finishing wakeup.
Aug 10 09:36:36 hp-dm1 kernel: Restarting tasks ... 
Aug 10 09:36:36 hp-dm1 kernel: r8169 0000:03:00.0: no hotplug settings from platform
Aug 10 09:36:36 hp-dm1 kernel: r8169 0000:03:00.0: no hotplug settings from platform
Aug 10 09:36:36 hp-dm1 kernel: r8169 0000:03:00.0: no hotplug settings from platform
Aug 10 09:36:36 hp-dm1 kernel: done.
Aug 10 09:36:36 hp-dm1 kernel: video LNXVIDEO:00: Restoring backlight state
Aug 10 09:36:36 hp-dm1 systemd[1]: Time has been changed
Aug 10 09:36:36 hp-dm1 systemd[664]: Time has been changed
Aug 10 09:36:36 hp-dm1 systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Aug 10 09:36:36 hp-dm1 systemd[1]: Stopping Bluetooth.
Aug 10 09:36:36 hp-dm1 systemd[1]: Stopped target Bluetooth.
Aug 10 09:36:36 hp-dm1 systemd[1]: Starting Bluetooth.
Aug 10 09:36:36 hp-dm1 systemd[1]: Reached target Bluetooth.
Aug 10 09:36:36 hp-dm1 systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill4...
Aug 10 09:36:36 hp-dm1 dhcpcd[1255]: wlo1: carrier lost
Aug 10 09:36:36 hp-dm1 dhcpcd[1255]: wlo1: deleting route to 192.168.100.0/24
Aug 10 09:36:36 hp-dm1 dhcpcd[1255]: wlo1: deleting default route via 192.168.100.254
Aug 10 09:36:36 hp-dm1 avahi-daemon[344]: Withdrawing address record for 192.168.100.2 on wlo1.
Aug 10 09:36:36 hp-dm1 avahi-daemon[344]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.100.2.
Aug 10 09:36:36 hp-dm1 avahi-daemon[344]: Interface wlo1.IPv4 no longer relevant for mDNS.
Aug 10 09:36:36 hp-dm1 systemd[1]: Started Load/Save RF Kill Switch Status of rfkill4.
Aug 10 09:36:36 hp-dm1 systemd-sleep[3645]: System resumed.
Aug 10 09:36:37 hp-dm1 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug 10 09:36:37 hp-dm1 kernel: ata1.00: configured for UDMA/100
Aug 10 09:36:37 hp-dm1 dhcpcd[1255]: wlo1: carrier acquired
Aug 10 09:36:37 hp-dm1 dhcpcd[1255]: wlo1: IAID fe:08:9d:c9
Aug 10 09:36:37 hp-dm1 dhcpcd[1255]: wlo1: rebinding lease of 192.168.100.2
Aug 10 09:36:37 hp-dm1 upowerd[732]: (upowerd:732): UPower-Linux-WARNING **: energy_full (71.539200) is greater than energy_full_design (71.280000)
Aug 10 09:36:38 hp-dm1 dhcpcd[1255]: wlo1: soliciting an IPv6 router
Aug 10 09:36:39 hp-dm1 ntpd[353]: Deleting interface #5 wlo1, 192.168.100.2#123, interface stats: received=28, sent=28, dropped=2, active_time=641 secs
Aug 10 09:36:39 hp-dm1 ntpd[353]: 88.191.120.99 local addr 192.168.100.2 -> <null>
Aug 10 09:36:39 hp-dm1 ntpd[353]: 37.59.25.31 local addr 192.168.100.2 -> <null>
Aug 10 09:36:39 hp-dm1 ntpd[353]: 212.83.174.163 local addr 192.168.100.2 -> <null>
Aug 10 09:36:42 hp-dm1 dhcpcd[1255]: wlo1: leased 192.168.100.2 for 3600000 seconds
Aug 10 09:36:42 hp-dm1 dhcpcd[1255]: wlo1: adding route to 192.168.100.0/24
Aug 10 09:36:42 hp-dm1 dhcpcd[1255]: wlo1: adding default route via 192.168.100.254
Aug 10 09:36:42 hp-dm1 avahi-daemon[344]: Joining mDNS multicast group on interface wlo1.IPv4 with address 192.168.100.2.
Aug 10 09:36:42 hp-dm1 avahi-daemon[344]: New relevant interface wlo1.IPv4 for mDNS.
Aug 10 09:36:42 hp-dm1 avahi-daemon[344]: Registering new address record for 192.168.100.2 on wlo1.IPv4.
Aug 10 09:36:42 hp-dm1 systemd[1]: Started Suspend.
Aug 10 09:36:42 hp-dm1 systemd[1]: Service sleep.target is not needed anymore. Stopping.
Aug 10 09:36:42 hp-dm1 systemd[1]: Stopping Sleep.
Aug 10 09:36:42 hp-dm1 systemd[1]: Stopped target Sleep.
Aug 10 09:36:42 hp-dm1 systemd[1]: Starting Suspend.
Aug 10 09:36:42 hp-dm1 systemd[1]: Reached target Suspend.
Aug 10 09:36:42 hp-dm1 sudo[3643]: pam_unix(sudo:session): session closed for user root
Aug 10 09:36:43 hp-dm1 ntpd[353]: Listen normally on 6 wlo1 192.168.100.2:123
Aug 10 09:36:43 hp-dm1 ntpd[353]: new interface(s) found: waking up resolver

The offending line seems to be

[drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 0000d438 tail 00000000 start 0040b000

The discussion about this bug seems to be here, and remains unsolved.

Andrew

Offline

#15 2014-08-12 11:02:10

PayterX
Member
Registered: 2014-08-11
Posts: 9

Re: "Freeze" after wake from suspend?

Upgrading my kernel to 3.16 fixed it for me.

Offline

Board footer

Powered by FluxBB