Bug 112235

Summary: [AMD tahiti xt] random crashes of GL/vulkan games
Product: DRI Reporter: Sylvain BERTRAND <sylvain.bertrand>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: critical    
Priority: not set    
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
kernel log
none
xorg log none

Description Sylvain BERTRAND 2019-11-08 17:34:37 UTC 
games started to randomly crash, vulkan or GL (dota2, dota2 underlord, CS:GO).

The only info I get from the crashes, are from dota2 vulkan (see kernel log) and dota underlords.
This is a mesa vulkan debug build and the offset 0x1e08000 does not map to any source code (glibc addr2line).

I cannot bisect correctly since some sessions have no crash at all for hours.

Any ideas? (for the moment, I can update linux/drm/llvm/mesa/xserver every week)
Comment 1 Sylvain BERTRAND 2019-11-08 17:35:07 UTC 
Created attachment 145914 [details]
kernel log
Comment 2 Alex Deucher 2019-11-08 17:35:53 UTC 
Probably a mesa bug rather than a kernel bug.
Comment 3 Sylvain BERTRAND 2019-11-08 17:36:03 UTC 
Created attachment 145915 [details]
xorg log
Comment 4 Sylvain BERTRAND 2019-11-08 17:39:16 UTC 
could you log the bug for me? I am waiting for my mesa gitlab bugzilla account registration. I am blocked by google javascript capcha *bip* as I use no javascript/ basic (x)html browers, I did contact the mesa dev mailing list owner though (since it seems to be the same thing).
Comment 5 Sylvain BERTRAND 2019-11-12 17:12:34 UTC 
ok, seems I got it: was weird I got no debug infos with a constant crash location in a debug build... because the crash was... in c++ cr*p, namely llvm, which had no debug infos since I did a release build. llvm src was not updating because I used the old git repo location. Have the "fixed" c++ brainf*cked llvm now.

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.