As described on http://bugs.gentoo.org:80/show_bug.cgi?id=261112, there is an X lock up when resuming from suspend to {disk,ram} when using xf86-video-intel-2.6.X series. I will try to attach a log in a bit
Created attachment 23657 [details] dmesg output
Created attachment 23658 [details] Xorg.0.log output
And a some information about my system Kernel: 2.6.28-gentoo-r2 Xorg-server: 1.5.3 Xorg-X11: 7.4 mesa: 7.3 xf86-video-intel: 2.6.3 2.5.1 driver works fine so I guess this is a regression on 2.6.X series Let me know if you need more information
I've been hitting this as well on my thinkpad. After resume on my X3100, I get a locked xorg, with an unmovable cursor: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) After googling a bit, it seems many people are hitting this with the new drivers: http://bugs.archlinux.org/task/13651 I've experienced this on 2.6.27.x and 2.6.28.x
This behavior is not reproducable with the following combination 1) xf86-video-intel-2.6.3 2) 2.6.29 kernel 3) Xorg-1.6
I have the same problem with intel 885GM. kernel 2.6.29 xorg-server 1.6.1 xf86-video-intel 2.3.2 After resume from suspend the LVDS (laptop monitor) is blank but the VGA has no problem.
Sorry, I meant 855GM, not 885GM.
Created attachment 24958 [details] reg_dump before suspend captured after VT switch to text console (before suspend)
Created attachment 24959 [details] reg_dump after suspend captured after resume from suspend, still in text console (cannot see the text because the screen is blank). captured with intel_reg_dumper.
Markos, sounds like this bug is fixed for you. Zaf, can you re-open if you still see failures with a more recent 2D driver? Also, please attach your X log etc. from the failure, see http://intellinuxgraphics.org/how_to_report_bug.html for info.
Thanks. The bug doesn't appear with xf86-video-intel 2.7.0
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.