Bug 104416 - [skl] GPU HANG: ecode 9:0:0x85dffffb, in Bastion
Summary: [skl] GPU HANG: ecode 9:0:0x85dffffb, in Bastion
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 17.3
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-30 02:49 UTC by mateusz.macieja8
Modified: 2018-11-20 13:50 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (40.94 KB, text/plain)
2017-12-30 02:49 UTC, mateusz.macieja8
Details

Description mateusz.macieja8 2017-12-30 02:49:58 UTC
Created attachment 136450 [details]
/sys/class/drm/card0/error

mesa 17.3.1-2

Bastion (steam) crashes after selecting the story entry in the game menu (the loading screen freezes).
Does not crash with the antialiasing 2x option set.
Comment 1 Elizabeth 2018-01-05 22:26:28 UTC
Hello Mateusz, 
Do the game or steam returns any trace? What desktop are you using? Do this worked in any previous Mesa version? If you have the chance, could you try this branch https://cgit.freedesktop.org/mesa/mesa/?
Thank you.
Comment 2 Marina Chernish 2018-11-20 09:04:27 UTC
Bastion game hangs with 17.3.1 mesa on Skylake. The newest 19.0.0 mesa works well so I've bisected this. It was fixed by commit:

468a2b6525f3b1e950d8b14138ccf62227aab73a is the first fixed commit
commit 468a2b6525f3b1e950d8b14138ccf62227aab73a
Author: Jason Ekstrand <jason.ekstrand@intel.com>
Date:   Mon Jan 22 23:40:48 2018 -0800

	i965/miptree: Add an aux_disabled parameter to render_aux_usage
    
	Only one of the callers of intel_miptree_render_aux_usage actually took
	brw->draw_aux_buffer_disabled into account.  This was causing us to
	ignore draw_aux_buffer_disabled for the intel_miptree_prepare_render.
	This isn't a problem because the draw_aux_buffer_disabled entry was set
	during texture preparation and we already did the resolve at that time.
	However, this also meant that the aux_usage we were passing to
	brw_cache_flush_for_render and brw_render_cache_add_bo was wrong so our
	automatic cache flushing around aux_usage changes wasn't happening.
	This was causing GPU hangs in Oxenfree.
    
	Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104711
	Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104411
	Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104383
	Fixes: ea0d2e98ecb369ab84e78c84709c0930ea8c293a
	Cc: mesa-stable@lists.freedesktop.org
	Reviewed-by: Iago Toral Quiroga <itoral@igalia.com>
	Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
	(cherry picked from commit d38ec24f531fac0b53c406a09d17427309a3ffca)

My environment: Skylake kernel 4.15.0-34-generic; Ubuntu 18.04; CPU:Intel Core i3-6006U; GPU: Intel® HD Graphics 520.
Comment 3 Denis 2018-11-20 13:50:43 UTC
closing as Marina found commit which fixed an issue.


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.