Bugzilla – Bug 21246
[GM965 KMS] Tiling corrupts screen with 2.7.0
Last modified: 2009-05-14 07:53:15 UTC
Created attachment 24894 [details]
The xorg log when the tiling is enabled.
Using the 2.7.0 release, the display gets messed up, as if the screen is somehow out of sync, making it totally unusable. Note that it seems to run fine, it doesn't crash, but it's hard to see what's drawn on the screen. I don't use a xorg.conf for this setup.
When I disable tiling however, everything seems to run fine, so I'm gussing it's a tiling bug :)
I can also reproduce this bug, and I can help pin down when it was introduced. The source repo for this package in ArchLinux is available here.
Revision 35727 has this bug, while 32224 does not. I haven't checked the intermediate revision, as it's an older version of the driver with a patch to fix the Xv lockup issue. The 32224 revision of the driver is a snapshot of the 2.7 branch.
Just as an amendment to my previous comment, the 32224 revision of the package includes a patch which appears to be a git-diff produced patch to bring commit 1d19b024dba970e4b24daccb898101f77d5529ff (which I assume is the same tree that was released as 2.6.999) up to e2465249a90b9aefe6d7a96eb56a51fde54698a0. This latter commit then, doesn't have the tiling bug.
Using 2.7.0 with KMS needs this kernel fix:
It should go into upstream kernel soon, if it hasn't.
Please reopen if you find this patch not help.
*** Bug 21276 has been marked as a duplicate of this bug. ***
*** Bug 21411 has been marked as a duplicate of this bug. ***
*** Bug 21437 has been marked as a duplicate of this bug. ***
*** Bug 21460 has been marked as a duplicate of this bug. ***
*** Bug 21486 has been marked as a duplicate of this bug. ***
Just upgraded to kernel 188.8.131.52 which contained the tiling bugfix and has fixed the issue for me.
I'm using xf86-video-intel 2.7.1 with kernel 184.108.40.206 from ArchLinux. I have this problem if I don't set this as my xorg.conf:
Option "Tiling" "false"
Was the patch proposed in comment #3 is included in 220.127.116.11?