After waking up from suspend, my screen has two lines. One on the right and one the left (attached screenshot). Not sure where that is coming from. BTW, I am not using 915resolution. I have updated my i810_drv.so to 1.6.5. I am running an intel dual core (core due) machine with onbaord Intel 950 (945GM) on board chipset. Willing to try things out to get this fixed.
Created attachment 7117 [details] showing the artifacts
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
I can confirm this bug on kubuntu/feisty, xorg 7.2. The problem is present using both 915resolution and the modesetting i810 driver. I am using a Lenovo x60 tablet with the SXGA screen, so I suspect that this bug is only present on machines that have higher resolution screens. This bug has also been reported on launchpad (https://launchpad.net/bugs/91966) and has a little more description there.
This seems like it might be related to bug 8881 (Pixel error with i945). The area in which the corruption/exchanged pixels occurs sounds the same. Fwiw, I'm also seeing this on a T60 with the 945GM. The severity of the corruption is variable. Sometimes just two rows of pixels affected, other times smearing across several lines - usually worse after a suspend/resume cycle or two.
I'm seeing something very similar on a Panasonic CF-Y5 (also with the Intel 950 hardware); xorg version is the one shipped with Ubuntu Feisty Fawn, listed by dpkg as 1:7.2-0ubuntu11
Seeing it in Xorg server 1.3 and intel git 9675ccb30818bf831ac4c634751ab4bfe35f7bfe as well. See attachment.
Created attachment 10486 [details] Screenshot of corruption Corruption across XRandR 1.2 screens, intel. Note this is after a resume.
Additionally, it's more apparent when I bump up the size of the visible screen (by adding an additional external monitor via XRandR 1.2). If I don't plug in anything after a resume, the artifacts rarely occur. This is a bit anecdotal at the moment, but I'll see if I can confirm.
*MUCH* has changed between then and now. Moving to the corect component and closing as fixed. Please open a new bug (in the correct component) if you still have issues.
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.