- Gfxbench gl error accessing database android#
- Gfxbench gl error accessing database code#
- Gfxbench gl error accessing database windows#
Modules linked in: fuse snd_hda_codec_realtek snd_hda_codec_generic amdgpu i915 x86_pkg_temp_thermal coretemp snd_hda_codec_hdmi snd_hda_intel snd_hda_codec e1000e crct10dif_pclmul snd_hwdep snd_hda_core crc32_pclmul chash gpu_sched snd_pcm ttm igb mei_me mei pinctrl_sunrisepoint pinctrl_intel ] *ERROR* Process information: process testfw_app pid 26882 thread testfw_app pid 26883 ] *ERROR* ring gfx timeout, signaled seq=11267, emitted seq=11269 amdgpu 0000:01:00.0: GPU fault detected: 146 0x0fb0840c for process testfw_app pid 26882 thread testfw_app pid 26883 amdgpu 0000:01:00.0: GPU fault detected: 146 0x0fa0840c for process testfw_app pid 26882 thread testfw_app pid 26883 amdgpu 0000:01:00.0: GPU fault detected: 146 0x0fa0880c for process testfw_app pid 26882 thread testfw_app pid 26883 Iteration 1/1: testfw_app -gfx vulkan -gl_api vulkan -width 1920 -height 1080 -fullscreen 1 -test_id vulkan_5_normal Ubuntu 18.04 got LLVM 7 so I checked this again with latest Mesa (4f0a3c9f9eda65), and the hangs are still happening: Here's some extra info on the Aztec Ruins benchmark:
Gfxbench gl error accessing database android#
Or if there's some Linux Android container that passes Vulkan calls through, you could try the Android version:
Gfxbench gl error accessing database windows#
If Windows version supports Vulkan and Wine doesn't mangle its API calls for Linux, you could be able to trigger the issue (going through DX -> DXVK probably isn't good enough). If not, you could try using the Windows version with Wine, when the site works again. You can still get the page from Google cache:Īs you can see, there isn't yet a public Linux version of GfxBench v5, only Android, iOS, MacOS and Windows versions.Īnd I naturally can't provide the proprietary version.ĭoesn't Valve have licenses to industry standard 3D benchmarks (of which GfxBench is the main one on mobile, and as result, nowadays important also on desktop)? It still worked when I filed this (and has worked for years before). > The link is dead, if you have the demo can you upload it somewhere? (In reply to Samuel Pitoiset from comment #2) No idea whether this is related to GL bug 108898 on same device. bug 104634, bug 105276), so the problem could be in common code. There are some issues with this particular test also on Intel (see e.g. No idea whether this is a regression as I checked it only now. There are also other things that don't work properly in automated testing at this point, but I'm not sure whether they're related. GPU recovery disabled.Īfter this, no other GPU operations seem to work properly. ] *ERROR* ring gfx timeout, signaled seq=53811, emitted seq=53814 amdgpu 0000:01:00.0: GPU fault detected: 146 0x0fa9080c for process testfw_app pid 2995 thread testfw_app pid 2997 amdgpu 0000:01:00.0: GPU fault detected: 146 0x0fa0840c for process testfw_app pid 2995 thread testfw_app pid 2997
amdgpu 0000:01:00.0: GPU fault detected: 146 0x0fa0880c for process testfw_app pid 2995 thread testfw_app pid 2997 * Right after test starts, following in dmesg: * Works fine like the Aztec Ruins GL version and Sacha Willems' Vulkan tests, no GPU hangs * bin/testfw_app -gfx vulkan -gl_api vulkan -width 1920 -height 1080 -fullscreen 1 -test_id vulkan_5_normal
Gfxbench gl error accessing database code#
v4.20-rc4 kernel + latest drm code from yesterday) HadesCanyon KBL i7-8809G ( Vega (rev c0))
0 kommentar(er)
