Bug 109835 - [865G] [drm] GPU HANG: ecode 2:0:0x75f4003e, in europa.exe [1323], reason: hang on rcs0, action: reset
Summary: [865G] [drm] GPU HANG: ecode 2:0:0x75f4003e, in europa.exe [1323], reason: ha...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i915 (show other bugs)
Version: 19.1
Hardware: Other Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-05 17:36 UTC by rtentser
Modified: 2019-09-18 19:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
glxinfo (12.05 KB, text/plain)
2019-03-05 17:36 UTC, rtentser 		Details
dmesg (171.49 KB, text/plain)
2019-03-05 17:36 UTC, rtentser 		Details
error (8.79 KB, text/plain)
2019-03-05 17:54 UTC, rtentser 		Details
View All

Description rtentser 2019-03-05 17:36:26 UTC 
Created attachment 143538 [details]
glxinfo

I get this bug when i try to run Windows applications with wine. I can reproduce it with linux 4.9.144 (debian build) and mesa 13.0.6, linux 4.19.16 (debian build) and mesa 18.3.4, linux 5.0 (custom build based on debian configuration) and mesa 18.3.4. I'll attach dmesg and /sys/class/drm/card0/error for 5.0 with "drm.debug=0x1e" and "log_buf_len=4M" boot parameters.
Comment 1 rtentser 2019-03-05 17:36:52 UTC 
Created attachment 143539 [details]
dmesg
Comment 2 rtentser 2019-03-05 17:54:41 UTC 
Created attachment 143540 [details]
error
Comment 3 rtentser 2019-05-03 15:24:57 UTC 
I've lied, i have 865GV. With this motherboard: https://www.asrock.com/mb/Intel/P4i65GV/index.asp

Also, LIBGL_ALWAYS_SOFTWARE is a workaround for the problem. But it works very slow.
Comment 4 rtentser 2019-06-03 14:21:28 UTC 
Still here in 19.0.5 and 19.1.0-rc4.
Comment 5 GitLab Migration User 2019-09-18 19:41:30 UTC 
-- 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/791.

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.