After resuming from hibernation, the screen goes black and nothing will work until ctrl+alt+fx is pressed and then one goes back to X by pressing ctrl+alt+f7. This phenomenon was observed after upgrading intel linux driver from 2.20.x to 2.21.x. uname -a: Linux FefidLaptop 3.7.4-pf #5 SMP PREEMPT Fri Feb 8 23:47:58 IRST 2013 x86_64 Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz GenuineIntel GNU/Linux I am on Gentoo, if this helps: Portage 2.1.11.50 (default/linux/amd64/13.0/desktop/kde, gcc-4.7.2, glibc-2.15-r3, 3.7.4-pf x86_64) ================================================================= System uname: Linux-3.7.4-pf-x86_64-Intel-R-_Core-TM-_i3_CPU_M_380_@_2.53GHz-with-gentoo-2.1 KiB Mem: 3843084 total, 1371800 free KiB Swap: 4194300 total, 4194300 free Timestamp of tree: Wed, 27 Feb 2013 19:45:01 +0000 ld GNU ld (GNU Binutils) 2.22 distcc 3.1 x86_64-pc-linux-gnu [enabled] app-shells/bash: 4.2_p37 dev-lang/python: 2.7.3-r2, 3.2.3 dev-util/cmake: 2.8.9 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.11.8 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.9.6-r3, 1.11.6 sys-devel/binutils: 2.22-r1 sys-devel/gcc: 4.6.3, 4.7.2-r1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.6 (virtual/os-headers) sys-libs/glibc: 2.15-r3 BUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=native -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-O2 -march=native -pipe" FFLAGS="-O2 -pipe" LDFLAGS="-Wl,-z,now,--as-needed,-O1,--hash-style=gnu,--sort-common" MAKEOPTS="-j20 -l8" dmesg after resuming: [13006.406463] TuxOnIce 3.3, with support for usm, compression, block i/o, swap storage, file storage, userui. [13006.430014] Initiating a hibernation cycle. [13006.466962] Console is 42x165. [13006.467019] Using configuration file /etc/splash/tuxonice/1366x768.cfg. [13006.496911] Framebuffer support initialised successfully. [13006.500976] Starting other threads.Freezing user space processes ... (elapsed 0.01 seconds) done. [13006.512215] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [13006.814957] Restarting kernel threads ... done. [13006.906118] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [13007.623899] ...20%...40%...60%...80% [13015.648899] Waited for i/o due to synchronous I/O 4 times. [13015.648908] Waited for i/o due to throughput_throttle 2318 times. [13015.649261] Suspending console(s) (use no_console_suspend to debug) [13015.649464] sd 0:0:0:0: [sda] Synchronizing SCSI cache [13016.216779] PM: freeze of devices complete after 567.823 msecs [13016.216958] PM: late freeze of devices complete after 0.176 msecs [13016.217349] PM: noirq freeze of devices complete after 0.390 msecs [13016.217478] ACPI: Preparing to enter system sleep state S4 [13017.228157] PM: Saving platform NVS memory [13017.229846] Disabling non-boot CPUs ... [13017.231169] smpboot: CPU 1 is now offline [13017.232973] smpboot: CPU 2 is now offline [13017.234511] smpboot: CPU 3 is now offline [13017.234829] Extended CMOS year: 2000 [13017.235461] PM: Restoring platform NVS memory [13017.235975] Extended CMOS year: 2000 [13017.236005] CPU0: Thermal monitoring handled by SMI [13017.236030] Enabling non-boot CPUs ... [13017.237106] smpboot: Booting Node 0 Processor 1 APIC 0x4 [13017.248236] CPU1: Thermal monitoring handled by SMI [13017.250639] CPU1 is up [13017.250681] smpboot: Booting Node 0 Processor 2 APIC 0x1 [13017.261812] CPU2: Thermal monitoring handled by SMI [13017.264235] CPU2 is up [13017.264275] smpboot: Booting Node 0 Processor 3 APIC 0x5 [13017.275403] CPU3: Thermal monitoring handled by SMI [13017.277827] CPU3 is up [13017.279809] ACPI: Waking up from system sleep state S4 [13017.810498] PM: noirq restore of devices complete after 11.224 msecs [13017.810690] PM: early restore of devices complete after 0.125 msecs [13017.810713] i915 0000:00:02.0: setting latency timer to 64 [13017.810724] ehci_hcd 0000:00:1a.0: setting latency timer to 64 [13017.810736] usb usb1: root hub lost power or was reset [13017.810738] ehci_hcd 0000:00:1d.0: setting latency timer to 64 [13017.810739] pci 0000:00:1e.0: setting latency timer to 64 [13017.814681] usb usb2: root hub lost power or was reset [13017.818619] ahci 0000:00:1f.2: setting latency timer to 64 [13017.818626] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported [13017.818627] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported [13017.818642] snd_hda_intel 0000:00:1b.0: irq 41 for MSI/MSI-X [13017.818956] mei 0000:00:16.0: irq 44 for MSI/MSI-X [13017.819686] ath: phy0: ASPM enabled: 0x42 [13017.820710] mei 0000:00:16.0: wd: failed to find the client [13018.122763] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [13018.123631] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (unknown) filtered out [13018.124761] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [13018.126756] ata5: SATA link down (SStatus 0 SControl 300) [13018.128758] ata6: SATA link down (SStatus 0 SControl 300) [13018.131037] ata2.00: configured for UDMA/100 [13018.142839] usb 1-1: reset high-speed USB device number 2 using ehci_hcd [13018.178917] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (unknown) filtered out [13018.179294] ata1.00: configured for UDMA/133 [13018.189759] sd 0:0:0:0: [sda] Starting disk [13018.358708] usb 2-1: reset high-speed USB device number 2 using ehci_hcd [13018.545723] usb 1-1.1: reset high-speed USB device number 3 using ehci_hcd [13018.967524] usb 1-1.2: reset full-speed USB device number 4 using ehci_hcd [13019.104809] btusb 1-1.2:1.0: no reset_resume for driver btusb? [13019.104811] btusb 1-1.2:1.1: no reset_resume for driver btusb? [13019.338301] usb 2-1.2: reset low-speed USB device number 3 using ehci_hcd [13019.356159] ACPI Error: Thread 33331328 cannot release Mutex [MUT0] acquired by thread 33334464 (20120913/exmutex-399) [13019.356167] ACPI Error: Method parse/execution failed [\_SB_.LID0._LID] (Node ffff880132e7a8c0), AE_AML_NOT_OWNER (20120913/psparse-536) [13019.356180] dpm_run_callback(): acpi_button_resume+0x0/0x18 returns -19 [13019.356183] PM: Device PNP0C0D:00 failed to restore: error -19 [13019.456609] Extended CMOS year: 2000 [13019.606468] PM: restore of devices complete after 1796.766 msecs [13020.465411] ...20%...40%...60%...80% [13024.690849] Waited for i/o due to readahead not ready 1384 times. [13024.690852] Waited for i/o due to throughput_throttle 532 times. [13024.698141] Restarting tasks ... done. [13024.747698] wlan0: deauthenticated from 1c:af:f7:03:f9:a8 (Reason: 6) [13024.769375] cfg80211: Calling CRDA to update world regulatory domain [13024.789333] video LNXVIDEO:00: Restoring backlight state [13024.792235] TuxOnIce debugging info: - TuxOnIce core : 3.3 - Kernel Version : 3.7.4-pf - Compiler vers. : 4.6 - Attempt number : 1 - Parameters : 0 667648 0 0 -2 5 - Overall expected compression percentage: 0. - Compressor is 'lzo'. Compressed 2059177984 bytes into 445559395 (78 percent compression). - Block I/O active. Used 110785 pages from swap on /dev/sda3. - Max outstanding reads 1636. Max writes 6950. Memory_needed: 1024 x (4096 + 344 + 104) = 4653056 bytes. Free mem throttle point reached 0. - Swap Allocator enabled. Swap available for image: 1048575 pages. - File Allocator active. Storage available for image: 0 pages. - I/O speed: Write 163 MB/s, Read 286 MB/s. - Extra pages : 82 used/2000. - Result : Succeeded. [13025.857281] wlan0: authenticate with 1c:af:f7:03:f9:a8 [13025.876374] wlan0: send auth to 1c:af:f7:03:f9:a8 (try 1/3) [13025.878393] wlan0: authenticated [13025.878588] wlan0: associate with 1c:af:f7:03:f9:a8 (try 1/3) [13025.881418] wlan0: RX AssocResp from 1c:af:f7:03:f9:a8 (capab=0x411 status=0 aid=1) [13025.881503] wlan0: associated
Your Xorg.0.log from across suspend may have an important clue.
(In reply to comment #1) > Your Xorg.0.log from across suspend may have an important clue. Thank you for your quick response. Actually, it made me have a look on X.0.log and surprisingly it was identical to the one after installing an old intel-2.20.x driver. Even the results were the same, since with an old driver screen did not come up either until I switched back and forth to f7. Even I rebuilt the kernel; I chose an old one and even reinstalld xorg and its drivers in vain. This is going to be challenging. I think another package in the system has caused this bug to appear and it is not related to intel driver. Anyway, please close this bug as invalid. I am sorry for the inconvenience.
Please do reopen when you get some more information. Also be aware that we fixed some similar symptoms of compositors-vs-modeset (including suspend/hibernate & resume) in v3.8.
(In reply to comment #3) > Please do reopen when you get some more information. Also be aware that we > fixed some similar symptoms of compositors-vs-modeset (including > suspend/hibernate & resume) in v3.8. Thank you very much. Indeed, the problem had been provoked by using 3.7 kernel series and I can remember that before that, i.e. 3.6 series, I did not have this problem. I upgraded to 3.8.1 and the problem is gone. It correctly brings the screen up after resuming from hibernation, even with the intel 2.21.3 driver. Thanks for your tip. It did save me from being trapped in an infinite loop. However, another problem has occured which, of course, is not related to the intel driver, and I just would like to inform you of that: [ 0.397604] WARNING: at drivers/gpu/drm/i915/i915_gem.c:1021 __wait_seqno+0x4db/0x500() [ 0.397606] Hardware name: LIFEBOOK AH530 [ 0.397607] Modules linked in: [ 0.397610] Pid: 1, comm: swapper/0 Not tainted 3.8.1-gentoo #1 [ 0.397611] Call Trace: [ 0.397617] [<ffffffff81079da9>] ? warn_slowpath_common+0x79/0xc0 [ 0.397619] [<ffffffff81406b5b>] ? __wait_seqno+0x4db/0x500 [ 0.397622] [<ffffffff81444d39>] ? intel_ring_begin+0x39/0x140 [ 0.397624] [<ffffffff81445ad9>] ? pc_render_add_request+0x309/0x320 [ 0.397628] [<ffffffff8143e76f>] ? intel_enable_gt_powersave+0x45f/0x830 [ 0.397630] [<ffffffff81444a09>] ? intel_init_ring_buffer+0x179/0x340 [ 0.397633] [<ffffffff8142632a>] ? intel_modeset_init_hw+0x3a/0x50 [ 0.397635] [<ffffffff81427be9>] ? intel_modeset_gem_init+0x9/0x20 [ 0.397640] [<ffffffff813f8e9b>] ? i915_driver_load+0xb8b/0xdf0 [ 0.397644] [<ffffffff813e2add>] ? drm_get_pci_dev+0x18d/0x2c0 [ 0.397648] [<ffffffff813504b6>] ? local_pci_probe+0x46/0x80 [ 0.397650] [<ffffffff813507ca>] ? pci_device_probe+0x11a/0x120 [ 0.397653] [<ffffffff81455ad8>] ? driver_probe_device+0x68/0x220 [ 0.397655] [<ffffffff81455d23>] ? __driver_attach+0x93/0xa0 [ 0.397657] [<ffffffff81455c90>] ? driver_probe_device+0x220/0x220 [ 0.397659] [<ffffffff81453f3d>] ? bus_for_each_dev+0x4d/0x80 [ 0.397661] [<ffffffff81455238>] ? bus_add_driver+0x178/0x260 [ 0.397664] [<ffffffff81456324>] ? driver_register+0x84/0x180 [ 0.397668] [<ffffffff81f05e3e>] ? drm_core_init+0x12f/0x12f [ 0.397671] [<ffffffff810002e2>] ? do_one_initcall+0x122/0x170 [ 0.397674] [<ffffffff81edfbd3>] ? kernel_init_freeable+0xfd/0x18d [ 0.397676] [<ffffffff81edf4f7>] ? loglevel+0x34/0x34 [ 0.397679] [<ffffffff81820e70>] ? rest_init+0x80/0x80 [ 0.397681] [<ffffffff81820e79>] ? kernel_init+0x9/0xf0 [ 0.397683] [<ffffffff8183822c>] ? ret_from_fork+0x7c/0xb0 [ 0.397692] [<ffffffff81820e70>] ? rest_init+0x80/0x80 [ 0.397698] ---[ end trace 5faa54f4690f7058 ]--- [ 0.397700] [drm:ironlake_enable_rc6] *ERROR* failed to enable ironlake power power savings What is happening to the intel driver? That was not present in older series. Is it public or am I the only one who is affected by https://bugs.freedesktop.org/show_bug.cgi?id=58238? Albeit I do not see much difference in power saving results by looking at powertop output: The gpu idles at 2-3 ops/second. Thank you again.
We never had rc6 working effectively on ilk, and in fact were never convinced we got it working at all. Hence why it is disabled by default, and given the noises we received from the hardware guys there is no real impetus to get it working.
Note that the ilk rc6 related backtrace is already reported at https://bugzilla.kernel.org/show_bug.cgi?id=54691 Please test the patch attached to that bug report and if it works for you, supply your tested-by. Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.