<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - xf86-video-intel:2.21.x causes black screen after resuming from hibernation" href="https://bugs.freedesktop.org/show_bug.cgi?id=61699#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED INVALID - xf86-video-intel:2.21.x causes black screen after resuming from hibernation" href="https://bugs.freedesktop.org/show_bug.cgi?id=61699">bug 61699</a> from <a class="email" href="mailto:ketetefid@gmail.com" title="Kete Tefid <ketetefid@gmail.com>"> Kete Tefid</a> <pre>(In reply to <a href="show_bug.cgi?id=61699#c3">comment #3</a>) > 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 <a class="bz_bug_link bz_status_NEW " title="NEW --- - [ilk] *ERROR* failed to enable ironlake power power savings" href="show_bug.cgi?id=58238">https://bugs.freedesktop.org/show_bug.cgi?id=58238</a>? 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>