| Summary: | [845G] xf86-video-intel-2.14.0 - periodically "hung GPU" on X start. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Natrio <natrio> | ||||||
| Component: | Driver/intel | Assignee: | Default DRI bug account <dri-devel> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | critical | ||||||||
| Priority: | medium | ||||||||
| Version: | 7.6 (2010.12) | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Natrio
2011-03-01 06:54:19 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: 2.6.38.2 (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. |
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.