Created attachment 648247 [details] Xorg.0.log in case there is any helpful information in it. Description of problem: I am experiencing lock ups of my Sandy Bridge based laptop when the screen has been automatically turned off due to inactivity. On returning to the laptop I occasionally find that the screen will not turn back on and the system is completely unresponsive, it appears to have completely locked up. There is no response to keyboard input such as Ctrl-Alt-F2, Ctrl-Backspace or Ctrl-Delete, all I am able to do is perform a dirty shutdown via the power button. The lock ups do not occur when the laptop is in use, only when it has been left inactive and the screen has turned off. In the majority of cases the system will resume as it should but I am getting several lock ups per week at present. I consider this a serious bug due to the risk of file(system) corruption following the lock ups and the fact that it is not possible to work around the issue by disabling the function that automatically turns of the screen when inactive. The GNOME3 settings only allow you to choose a timeout between 1 minute and 1 hour, you cannot disable it completely. This bug appears to be a regression introduced by graphics driver/kernel updates rolled out in the last few weeks. Unfortunately due to the intermittent nature of the problem I cannot be more precise about which set of updates introduced the problem. The laptop is a Dell E6320 with Intel Core i5-2540M, i.e. Intel HD Graphics 3000. Most of the time the laptop is connected to an external monitor on the VGA port with the two displays configured as an extended desktop. Version-Release number of selected component (if applicable): kernel-3.6.6-1.fc17.x86_64 xorg-x11-server-Xorg-1.12.3-2.fc17.x86_64 xorg-x11-drv-intel-2.20.10-2.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 libdrm-2.4.39-1.fc17.x86_64 How reproducible: Intermittent, unpredictable. Steps to Reproduce: 1. Leave computer inactive for long enough for screen to turn off. 2. Attempt to wake the computer with keyboard/mouse input. Actual results: Sometimes the screen will turn back on and the computer will resume as before, sometimes the screen will remain off and the computer will be completely unresponsive. Expected results: The screen should always turn back on the computer resume as before. Additional info: I've assigned this to xorg-intel-drv-intel at it appears to graphics related but this may be the wrong component. I've searched for reports of similar issues but not found anything that quite matches what I'm seeing. It's possible that this bug is only triggered when using an external monitor in a two display set up. Possibly completely unrelated, but I notice my /var/log/messages is full of drm error messages such as the following: Nov 20 14:22:44 lapajh2 kernel: [ 3364.162095] [drm:__gen6_gt_force_wake_get] *ERROR* Force wake wait timed out Nov 20 14:22:45 lapajh2 kernel: [ 3364.896700] [drm:__gen6_gt_force_wake_get] *ERROR* Force wake wait timed out Nov 20 14:22:47 lapajh2 kernel: [ 3367.156448] [drm:__gen6_gt_force_wake_get] *ERROR* Force wake wait timed out Nov 20 14:22:48 lapajh2 kernel: [ 3367.332107] [drm:__gen6_gt_force_wake_get] *ERROR* Force wake wait timed out Nov 20 14:22:50 lapajh2 kernel: [ 3369.863319] [drm:__gen6_gt_force_wake_get] *ERROR* Force wake wait timed out
For what it's worth this issue is still present with: kernel-3.6.11-1.fc17.x86_64 xorg-x11-server-common-1.12.4-2.fc17.x86_64 xorg-x11-drv-intel-2.20.16-1.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 libdrm-2.4.39-1.fc17.x86_64
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.