Created attachment 61726 [details] Screenshot of the corruption Screen corruptions occur every now and then. I thought that could be some kind of program crashing, but even a live ubuntu session was having that problem. I have tested it on different distros and desktop managers, and got the same result. Most of the time, after having such kind of corruptions, the OS halts (not even MagicSysRq works) Also, it's not an easy-to-reproduce bug. Sometimes it keeps happening, and sometimes it doesn't happen for a long time.
Please reproduce with upstream components and include an Xorg.0.log and dmesg. More than likely the bug has been fixed if you do not state having used anything less than a couple of years old.
Created attachment 61841 [details] dmesg
Created attachment 61842 [details] Xorg log
Created attachment 61843 [details] Another screenshot of glyph corruption
Created attachment 61844 [details] Yet-Another screenshot of the corruption
I've added some screenshots and logs. I have tested with upstream as well (the log file I have attached is not with the upstream one) Since I saw "MTRR allocation failed" message in dmesg, I tried using "enable_mtrr_cleanup mtrr_spare_reg_nr=1" option, which didn't work.
I suspect it's somehow related to framebuffer. Any way to force a redraw to see if I'm right?
Still interested to know if this is actually reproducible with kernel-3.4 and xf86-video-intel.
Have tested with upstream components, about 2 months ago. Will give it a try with the latest updates as well. (When I have enough free time to fix a broken system, though :D)
Seems like everything works fine with mainline kernel (3.4.0) and upstream Intel drivers. Thanks
Created attachment 64495 [details] Updated Xorg log After updating and switching to SNA the bug is back!
You have to be a little bit more specific... Can you please open a new bug report with a screenshot demonstrating your corruption and reattach the Xorg log so that I know what exactly you are reporting?
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.