Bug 59004 - xf86-video-intel 2.20.12-1 (or higher) causes locks up computer on wake from screen sleep; dim on next boot
Summary: xf86-video-intel 2.20.12-1 (or higher) causes locks up computer on wake from ...
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-03 23:24 UTC by Ted Pavlic
Modified: 2013-02-15 00:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Ted Pavlic 2013-01-03 23:24:12 UTC 
This bug is similar to bug 47367 or bug 28739. It has also been reported at:

https://bugs.archlinux.org/task/32636

Description:

On my Lenovo ThinkPad W500 running Arch Linux, waking the display from display sleep causes the machine to lock up. In particular, either the screen goes black and does not respond to any key combination (although the network light keeps blinking) or the screen shows one frame of the screensaver with the unlock dialog, but the dialog does not respond to input. The only recourse is to do a hardware restart (using cntrl+alt+delete has no effect, and using CTRL+ALT+F# has no effect). On restart, the brightness in X is set to its lowest setting.

This problem started when upgrading from 2.20.9-2 to 2.20.12-1. Downgrading back to 2.20.9-2 fixes the problem. The problem is consistently reproducible on this laptop. It has not been tested whether versions between 2.20.9-2 and 2.20.12-1 also have the problem.

Additional info:
* xorg-video-intel 2.20.12-1 (or higher)


Steps to reproduce:

1. Let screen saver start
2. Let screen go to sleep
3. Attempt to wake the display from display sleep
Comment 1 Chris Wilson 2013-01-03 23:53:50 UTC 
Please attach your Xorg.0.log, and grab a 3.7 kernel.

Are you sure the machine is not accessible from the network?
Comment 2 Ted Pavlic 2013-01-04 00:13:14 UTC 
I can install the buggy driver again and further investigate whether it's accessible via network. That isn't trivial on this machine because it currently has no network services enabled, but I will update when I have a chance to enable sshd and try to access the machine the next time it locks up.
Comment 3 Chris Wilson 2013-02-15 00:21:06 UTC 
Please do reopen if this hang continues to be reproducable and you can assist in debugging this issue. 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.