Intel 845G, xf86-video-intel
2.14.0 - on X start periodically (~ every second time) "hung GPU", garbage on screen.
(EE) intel(0): Detected a hung GPU, disabling acceleration.
(WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
In previous versions:
2.13.0 - Working, but wrong positioning and resizing OpenGL picture.
2.12.0 - Seems to be Ok.
I can confirm this bug, to a certain point.
The X driver segfaults (100% probability) on a second start of "wine Aquaria.exe" (or any other 2D/3D game) and it can be randomly triggered by ie. google-chrome's flash player.
xf86-video-intel: 2.14.0-4 (debian package)
xserver: xserver-xorg (7.6+6), xserver-xorg-core (1.9.5-1)
libdrm: 2.4.23-3 (from aptitude, pkg-config didn't work)
kernel: 18.104.22.168 (happens on 2.6.37 as well)
Linux distribution: Debian GNU/Linux "Wheezy" (testing) x86_64
Machine or mobo model: Lenovo Thinkpad T500
Display connector: laptop monitor, LVDS1
I've managed to actually produce a (hopefully) usable backtrace, it's attached as trace.txt, my xorg.conf is attached as well.
There's no graphic driver related warning/error in Xorg.0.log (no "hung" message) because of the NoTrapSignals option enabled (the machine freezes), there's a less verbose version of the attached trace if the option is disabled.
Created attachment 45752 [details]
backtrace of an X core file
Created attachment 45753 [details]
xorg.conf used in the test case
Jirij, that has nothing to do with the original bug or the ddx.
I'm very sorry, you're right - I've just found out that the issue happens with the "radeon" driver as well, so it's not device-dependent. The regression must have been caused by some more generic package update rather than 2.13.x->2.14.0 update.
I'll file a proper bug in an appropriate section, sorry for the inconvenience.
This issue is affecting a hardware component which is not being actively worked on anymore.
Moving the assignee to the dri-devel list as contact, to give this issue a better coverage.
*** This bug has been marked as a duplicate of bug 26345 ***