Created attachment 41377 [details] i915_error_state dump When trying to play myst v using wine the gpu hangs. intel_gpu_top shows the 100% time in texture decompress. This happens very soon in the game and is 100% reproducible. I have a i915_error_state dump as requested by Chris Wilson. I am adding it as an attachment.
Per Chris Wilson I changed #define DRM_I915_HANGCHECK_PERIOD 10000 to 10000 as test against a spurious hang. The screen still locked up but it took about 10 seconds for it turn all garbled. This is on linux 2.6.37rc7 with Dave Airlies latest drm stuff. My hardware is: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GM L Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 1252 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at feb80000 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at ec00 [size=8] Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 3: Memory at feb40000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Subsystem: ASUSTeK Computer Inc. Device 1252 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Region 0: Memory at fea80000 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Which version of mesa?
Dec 18 18:01:50 joker4 yum[5244]: Updated: mesa-libGL-7.10-0.17.fc15.x86_64 Dec 18 18:01:52 joker4 yum[5244]: Updated: mesa-libGL-7.10-0.17.fc15.i686 Dec 18 18:01:54 joker4 yum[5244]: Updated: mesa-libGLU-7.10-0.17.fc15.x86_64 Dec 18 18:02:02 joker4 yum[5244]: Updated: mesa-dri-drivers-7.10-0.17.fc15.x86_6 4 Dec 18 18:02:03 joker4 yum[5244]: Updated: mesa-libGLU-7.10-0.17.fc15.i686 Dec 18 18:02:11 joker4 yum[5244]: Updated: mesa-dri-drivers-7.10-0.17.fc15.i686
Could you please check if this happens with recent mesa as well? Thanks!
Hmmm... I am running f14 and the newest mesa in rawhide is 7.11-2.fc17 is that current enough?
(In reply to comment #5) > Hmmm... I am running f14 and the newest mesa in rawhide is 7.11-2.fc17 is that > current enough? Yep, does it still hangs with this version of mesa?
Still happens. Aug 31 18:34:23 joker4 yum[5429]: Updated: mesa-dri-drivers-7.11-2.fc17.i686 Aug 31 18:39:45 joker4 kernel: [435871.006044] [drm:i915_hangcheck_elapsed] *ERR OR* Hangcheck timer elapsed... GPU hung Aug 31 18:39:45 joker4 kernel: [435871.007541] [drm:i915_reset] *ERROR* Failed t o reset chip.
Should add : wine-core-1.3.24-1.fc14.x86_64 kernel 2.6.37-1.fc15.x86_64
*** Bug 71926 has been marked as a duplicate of this bug. ***
Second error state: https://bugs.freedesktop.org/attachment.cgi?id=89652
I still get a hung gpu using the latest kernel 3.12, Xorg and mesa. It even happens using XP in running in VirtualBox to play Myst 5 or Myst URU. To me this means it is not related to wine, but must be in the kernel driver, Xorg or mesa.
Hello, is this still a valid issue with latest SW? Otherwise closing soon. Thank you.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/688.
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.