Bug 54738 - [snb gt1] Dota2 (wine) randomly crashes with intel_do_flush_locked failed
Summary: [snb gt1] Dota2 (wine) randomly crashes with intel_do_flush_locked failed
Status: RESOLVED DUPLICATE of bug 55241
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-10 16:35 UTC by Illya Klymov
Modified: 2013-02-08 18:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
i915_error_state (2.15 MB, application/octet-stream)
2012-09-10 16:35 UTC, Illya Klymov 		Details
dmesg output (47.26 KB, application/octet-stream)
2012-09-10 16:35 UTC, Illya Klymov 		Details
lspci (1.99 KB, application/octet-stream)
2012-09-10 16:36 UTC, Illya Klymov 		Details
xorg log (89.88 KB, text/x-log)
2012-09-10 16:36 UTC, Illya Klymov 		Details
View All

Description Illya Klymov 2012-09-10 16:35:07 UTC 
Created attachment 66932 [details]
i915_error_state

When trying to run Dota2 on linux using latest wine I receive weird screen corruptions and after that a guaranteed crash with intel_do_flush_locked failed.

Other games, like Portal2 are running quite OK with my environment

OS: Archlinux x86_64
Mesa version: latest git e81ee67b51651e99e7e8e52c1ccafc66835d57cd
(also reproducible on 8.0.3)
X.org version: 1.12.4
libdrm version: 2.4.39
Comment 1 Illya Klymov 2012-09-10 16:35:43 UTC 
Created attachment 66933 [details]
dmesg output
Comment 2 Illya Klymov 2012-09-10 16:36:00 UTC 
Created attachment 66934 [details]
lspci
Comment 3 Illya Klymov 2012-09-10 16:36:35 UTC 
Created attachment 66935 [details]
xorg log
Comment 4 Eric Anholt 2013-02-08 18:53:59 UTC 
Since gt1 is often a special case for us, and there's another bug for regular gpu hangs with dota2 under wine, I'm marking this as a dup of that bug.

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

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.