Bug 34868 - [845G] xf86-video-intel-2.14.0 - periodically "hung GPU" on X start.
Summary: [845G] xf86-video-intel-2.14.0 - periodically "hung GPU" on X start.
Status: RESOLVED DUPLICATE of bug 26345
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact: Xorg Project Team
Depends on:
Reported: 2011-03-01 06:54 UTC by Natrio
Modified: 2011-09-09 02:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

backtrace of an X core file (1.21 KB, text/plain)
2011-04-17 21:00 UTC, jirij.jabb
no flags Details
xorg.conf used in the test case (1.87 KB, text/plain)
2011-04-17 21:01 UTC, jirij.jabb
no flags Details

Description Natrio 2011-03-01 06:54:19 UTC
Intel 845G, xf86-video-intel
2.14.0 - on X start periodically (~ every second time) "hung GPU", garbage on screen.
In log:
 (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.
Comment 1 jirij.jabb 2011-04-17 20:58:31 UTC
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.

chipset: GM45
xf86-video-intel: 2.14.0-4 (debian package)
xserver: xserver-xorg (7.6+6), xserver-xorg-core (1.9.5-1)
mesa: 7.10-4
libdrm: 2.4.23-3 (from aptitude, pkg-config didn't work)
kernel: (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.
Comment 2 jirij.jabb 2011-04-17 21:00:20 UTC
Created attachment 45752 [details]
backtrace of an X core file
Comment 3 jirij.jabb 2011-04-17 21:01:24 UTC
Created attachment 45753 [details]
xorg.conf used in the test case
Comment 4 Chris Wilson 2011-04-17 22:21:09 UTC
Jirij, that has nothing to do with the original bug or the ddx.
Comment 5 jirij.jabb 2011-04-18 03:07:17 UTC
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.
Comment 6 Eugeni Dodonov 2011-09-08 15:56:41 UTC
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.
Comment 7 Chris Wilson 2011-09-09 02:11:19 UTC

*** This bug has been marked as a duplicate of bug 26345 ***

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.