dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 104347] AMD RX 580: Hide/Show window sometimes corrupts screen (see screenshot)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104347 Bug ID: 104347 Summary: AMD RX 580: Hide/Show window sometimes corrupts screen (see screenshot) Product: Mesa Version: 17.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: arthurborsboom(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136316 --> https://bugs.freedesktop.org/attachment.cgi?id=136316&action=edit Screenshot of scrambled window When I hide all Windows with a shortcut and then show another one, a window (not the whole desktop) looks a scrambled, see attachments. It restores itself usually after 3-5 seconds and/or hiding/showing of the window after a couple of times. In dmesg there is no message of a GPU warning/error. Kernel: Linux 4.14.5-1-ARCH Driver: amdgpu X11: xf86-video-amdgpu 1.4.0 Mesa: 17.3.0 If this is the wrong place to report this issue, can you please move it to the correct location? If other information is needed, please let me know. -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 104345] Playing video hangs X-Server with showing scrambled picture, sound still playing.
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104345 Bug ID: 104345 Summary: Playing video hangs X-Server with showing scrambled picture, sound still playing. Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: bernhardu(a)mailbox.org Created attachment 136312 --> https://bugs.freedesktop.org/attachment.cgi?id=136312&action=edit kernel output captured from the serial line. Playing video hangs X-Server with showing scrambled picture, sound still playing. System hangs after some time playing mostly when playing a recorded DVB-S-SD stream via VLC. Happened also with other videos and players. This left the system showing a distorted version of the last shown frame from the video. Most of the time it is a chess board like pattern. Sound is still playing regularly. A ssh connection is still possible. Playing the exact same video again later works without problem. Kernel output shows at this time following: [ 4353.316286] amdgpu 0000:08:00.0: GPU fault detected: 146 0x0570480c [ 4353.328836] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001004AE [ 4353.343791] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A04800C [ 4353.358755] amdgpu 0000:08:00.0: VM fault (0x0c, vmid 5) at page 1049774, read from 'TC0' (0x54433000) (72) [ 4353.378234] amdgpu 0000:08:00.0: GPU fault detected: 146 0x0570440c [ 4353.390777] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0010049C [ 4353.405735] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A04400C [ 4353.420692] amdgpu 0000:08:00.0: VM fault (0x0c, vmid 5) at page 1049756, read from 'TC1' (0x54433100) (68) Followed by this: [ 4592.681352] INFO: task amdgpu_cs:0:1007 blocked for more than 120 seconds. [ 4592.695116] Tainted: G O 4.13.0-1-amd64 #1 Debian 4.13.13-1 [ 4592.709587] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4592.725255] amdgpu_cs:0 D 0 1007 1000 0x00400000 [ 4592.736245] Call Trace: [ 4592.741145] ? __schedule+0x3c8/0x860 [ 4592.748486] ? schedule+0x32/0x80 [ 4592.755120] ? schedule_timeout+0x1da/0x350 [ 4592.763537] ? amdgpu_vm_validate_level.isra.9+0x80/0x80 [amdgpu] [ 4592.775725] ? dma_fence_default_wait+0x239/0x260 [ 4592.785138] ? dma_fence_default_wait+0x239/0x260 [ 4592.794548] ? dma_fence_free+0x20/0x20 [ 4592.802220] ? dma_fence_wait_timeout+0x33/0xe0 [ 4592.811317] ? amdgpu_ctx_add_fence+0x61/0xf0 [amdgpu] [ 4592.821632] ? amdgpu_cs_ioctl+0x156b/0x1920 [amdgpu] [ 4592.831784] ? amdgpu_cs_find_mapping+0x90/0x90 [amdgpu] [ 4592.842432] ? drm_ioctl_kernel+0x65/0xb0 [drm] [ 4592.851510] ? drm_ioctl+0x2e3/0x3a0 [drm] [ 4592.859737] ? amdgpu_cs_find_mapping+0x90/0x90 [amdgpu] [ 4592.870373] ? do_futex+0x2df/0xa90 [ 4592.877376] ? amdgpu_drm_ioctl+0x49/0x80 [amdgpu] [ 4592.886971] ? do_vfs_ioctl+0x9f/0x600 [ 4592.894471] ? SyS_futex+0x7a/0x170 [ 4592.901453] ? SyS_ioctl+0x74/0x80 [ 4592.908264] ? system_call_fast_compare_end+0xc/0x97 Attached is a log captured on the serial port from boot to the crash follwed by a Magic-Sys-Req-T. This are the system specs: Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Radeon RX 460] (XFX) Display Server: x11 (X.Org 1.19.5 ) drivers: amdgpu (unloaded: modesetting,fbdev,vesa) Resolution: 1920x1080(a)60.00hz OpenGL: renderer: AMD Radeon RX 460 Graphics (AMD POLARIS11 / DRM 3.18.0 / 4.13.0-1-amd64, LLVM 5.0.0) version: 4.5 Mesa 17.2.5 System: Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.10.5 Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: N/A UEFI: American Megatrends v: 3203 date: 11/09/2017 CPU: Octa core AMD Ryzen 7 1700 Eight-Core (-HT-MCP-) speed/max: 1550/3000 MHz Error happened with Debian Stretch with linux 4.9 and later. Currently it is running a Debian testing. Is this the right product/component for this report? -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 104307] radeon ring 0 stalled for more than ... radeon ... GPU lockup ...
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104307 Bug ID: 104307 Summary: radeon ring 0 stalled for more than ... radeon ... GPU lockup ... Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: narutocanada(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136241 --> https://bugs.freedesktop.org/attachment.cgi?id=136241&action=edit apitrace trace --api gl ./a.out ; mv a.out.trace a.out.mesa-17.2.7.trace # how to reproduce: # cd /build/mesa-13.0.6/; make install rm a.out t.ppm ; gcc gbm5.c -lgbm -lEGL -lGL -lGLU ; apitrace trace --api gl ./a.out ; display t.ppm mv a.out.trace a.out.mesa-13.0.6.trace # cd /build/mesa-17.2.7/; make install echo > /var/log/messages rm a.out t.ppm ; gcc gbm5.c -lgbm -lEGL -lGL -lGLU ; apitrace trace --api gl ./a.out ; display t.ppm mv a.out.trace a.out.mesa-17.2.7.trace # NOTE: nromally this shader runs for about 1 second (depends on GPU), # but would never reach 10 seconds lockup timer defined in drivers/gpu/drm/radeon/radeon_drv.c # something changed in Mesa perhaps ? # single source file at: https://github.com/narutocanada/smallpt-glsl Dec 18 01:42:21 localhost kern.err kernel: [ 4272.087147] radeon 0000:00:01.0: ring 0 stalled for more than 10020msec Dec 18 01:42:21 localhost kern.warn kernel: [ 4272.089575] radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000000019 last fence id 0x000000000000001a on ring 0) Dec 18 01:42:22 localhost kern.err kernel: [ 4272.587921] radeon 0000:00:01.0: ring 0 stalled for more than 10521msec Dec 18 01:42:22 localhost kern.warn kernel: [ 4272.590350] radeon 0000:00:01.0: GPU lockup (current fence id 0x0000000000000019 last fence id 0x000000000000001a on ring 0) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 104266] [polaris10][arm] blurred screen on AMD Radeon Pro WX 7100
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104266 Bug ID: 104266 Summary: [polaris10][arm] blurred screen on AMD Radeon Pro WX 7100 Product: Mesa Version: 17.2 Hardware: ARM OS: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: vedran(a)miletic.net QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136175 --> https://bugs.freedesktop.org/attachment.cgi?id=136175&action=edit Photo >From ML Mesa-dev: https://lists.freedesktop.org/archives/mesa-dev/2017-December/179186.html https://lists.freedesktop.org/archives/mesa-dev/2017-December/179426.html https://lists.freedesktop.org/archives/mesa-dev/2017-December/180001.html Hi, We met a problem on ubuntu17.10 for arm server with amdgpu (AMD RADEON PRO WX 7100), we use open source driver which are integrated in ubuntu17.10 (Mesa 17.2.2). And the architecture is AArch64-linux-gnu. we install: apt-get install xserver-xorg xinit xfce4 and mesa-utils glmark2 we start x server: startx and then the monitor shows the screen and the screen is blurred (something wrong). And I have tried some opengl applications, the output has same problem.(something is missing or in the wrong place.) But in a x86_64 architecture server, with same OS. The screen output is normal. (I check xorg\DDX\mesa\libdrm etc.all the versions are the same with aarch64 server.) What I have done: 1. I upgrade kernel to 4.15-rc2 ,upgrade DRM to 3.23,upgrade DDX to 1.40,upgrade mesa to 17.2.6, but the problem still exist. 2. I enable ‘shadowprimary’ option, the screen output became normal, but the performance drop quickly——glxgears drop from 4800fps to 600fps, glmark drop from 4300 score to 730 score. (We solve the glxgears segmentation fault problem by add the compile flags: -fsigned-char. In arm platform, char variant default to "unsigned-char", that makes problem of glxgears segmentation fault. But after we recompile mesa with -fsigned-char. The screen output still tearing(blurred). the display problem still exist.) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 104193] [radeonsi] The Witcher 3 freezes the system with no attachments calls & transform feedback Wine patch
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104193 Bug ID: 104193 Summary: [radeonsi] The Witcher 3 freezes the system with no attachments calls & transform feedback Wine patch Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: shtetldik(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136068 --> https://bugs.freedesktop.org/attachment.cgi?id=136068&action=edit The Witcher 3: rotfiends radeonsi freeze Wine has an issue with distorted monsters in The Witcher 3. Józef Kucia identified the problem as follows: * wined3d doesn't support draw calls with no attachments, * wined3d tries to map transform feedback buffers while transform feedback is paused. See https://bugs.winehq.org/show_bug.cgi?id=43872#c8 He provided a patch: https://bugs.winehq.org/attachment.cgi?id=59848&action=diff&context=patch&c… However applying it, is causing a system freeze (with radeonsi) after such kind of monsters are encountered in the game and fighting them for some time. See attached savegame for example with rotfiends. Interestingly, Józef Kucia couldn't reproduce this freeze with radeon driver, so it appears to be radeonsi specific. You can apply the above Wine patch to Wine git master to test it (I build Wine using just that patch, and one staging patch for performance: https://raw.githubusercontent.com/wine-compholio/wine-staging/master/patche… My last test environment: OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10 / DRM 3.18.0 / 4.13.0-1-amd64, LLVM 5.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.4.0-devel (git-b926da241a) -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 103972] GL_ARB_gpu_shader_int64. Compute shader. Shared storage.
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103972 Bug ID: 103972 Summary: GL_ARB_gpu_shader_int64. Compute shader. Shared storage. Product: Mesa Version: 17.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: kampeador(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 135802 --> https://bugs.freedesktop.org/attachment.cgi?id=135802&action=edit main.cpp and shader. Hello. I can't assign a variable with the data from shared storage. Before 17.2.5 this bug affected all storage types, when using loops. It was fixed. Now its with shared storage only. Some algorithms are impossible to implement efficiently. I've created a test app to reproduce this bug. Output should be: OUTPUT: 2101479989,1917184202,4191109983,1779160146 Currently it is: 0,0,4191109983,1779160146 It was also tested with AMD proprietary driver(GL_AMD_gpu_shader_int64) on Windows 10 and worked correct. Note 1: If you remove a "shared" qualifier inside shader, you will see a correct output. Note 2: Sometimes an app freezes my OS on Shader Program execution. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 103769] Unity based games do not start
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103769 Bug ID: 103769 Summary: Unity based games do not start Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: bartos.petr(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 135499 --> https://bugs.freedesktop.org/attachment.cgi?id=135499&action=edit Crash of Layers of Fear Hi, It seems there is some problem with mesa git (in combination with llvm git) and Unity based games. They are crashing at start. I've already mentioned it here https://bugs.freedesktop.org/show_bug.cgi?id=103389 , but recently I have found that also Oddworld: New 'n' Tasty is crashing. Out of curiosity I've installed also Rochard (which is older but also Unity based) and it is also crashing. Reverting back to older version of mesa (and llvm 4.0), all three games are working. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 103316] [Hawaii, FirePro, radeon] WARNING: CPU: 1 PID: 18632 at drivers/gpu/drm/ttm/ttm_page_alloc_dma.c:548 ttm_dma_free_pool.part.8+0x128/0x130 [ttm]
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103316 Bug ID: 103316 Summary: [Hawaii, FirePro, radeon] WARNING: CPU: 1 PID: 18632 at drivers/gpu/drm/ttm/ttm_page_alloc_dma.c:548 ttm_dma_free_pool.part.8+0x128/0x130 [ttm] Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: vedran(a)miletic.net QA Contact: dri-devel(a)lists.freedesktop.org On kernel 4.13.6-300.fc27.x86_64, with 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT GL [FirePro W9100] upon modprobe -r radeon I get: [83523.596239] [drm] radeon: finishing device. [83523.615907] [TTM] Finalizing pool allocator [83523.615910] [TTM] Finalizing DMA pool allocator [83523.615942] ------------[ cut here ]------------ [83523.615948] WARNING: CPU: 1 PID: 18632 at drivers/gpu/drm/ttm/ttm_page_alloc_dma.c:548 ttm_dma_free_pool.part.8+0x128/0x130 [ttm] [83523.615949] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_device intel_cstate intel_uncore eeepc_wmi intel_rapl_perf asus_wmi snd_pcm sparse_keymap rfkill iTCO_wdt mxm_wmi iTCO_vendor_support [83523.615968] snd_timer wmi_bmof snd mei_me mei soundcore shpchp i2c_i801 lpc_ich tpm_infineon tpm_tis tpm_tis_core tpm wmi xfs libcrc32c amdgpu amdkfd i915 amd_iommu_v2 radeon(-) i2c_algo_bit drm_kms_helper ttm crc32c_intel drm r8169 mii video [83523.615978] CPU: 1 PID: 18632 Comm: modprobe Not tainted 4.13.6-300.fc27.x86_64 #1 [83523.615978] Hardware name: ASUS All Series/Z87-A, BIOS 1602 10/29/2013 [83523.615979] task: ffff948aebd84c80 task.stack: ffffa04ea4cf8000 [83523.615982] RIP: 0010:ttm_dma_free_pool.part.8+0x128/0x130 [ttm] [83523.615982] RSP: 0018:ffffa04ea4cfbc40 EFLAGS: 00010202 [83523.615983] RAX: 0000000000000202 RBX: ffff948ed5b6d540 RCX: 0000000000000000 [83523.615984] RDX: 0000000100400002 RSI: ffffdab5d0562e40 RDI: ffffa04ea4cfbbf0 [83523.615984] RBP: ffffa04ea4cfbc58 R08: ffff948ed58b9080 R09: 0000000100400001 [83523.615985] R10: ffffa04ea4cfbb40 R11: 0000000000000000 R12: ffff948edce2e2e0 [83523.615985] R13: 0000000000000008 R14: ffffffffc043e1e8 R15: ffff948edd148100 [83523.615986] FS: 00007efc655aa740(0000) GS:ffff948eefa40000(0000) knlGS:0000000000000000 [83523.615987] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [83523.615987] CR2: 000055e3e6293030 CR3: 00000003f194c000 CR4: 00000000001406e0 [83523.615988] Call Trace: [83523.615992] ttm_dma_page_alloc_fini+0x84/0xf0 [ttm] [83523.615994] ttm_mem_global_release+0x19/0x90 [ttm] [83523.616017] radeon_ttm_mem_global_release+0x12/0x20 [radeon] [83523.616026] drm_global_item_unref+0x4c/0x70 [drm] [83523.616035] radeon_ttm_fini+0x133/0x1a0 [radeon] [83523.616044] radeon_bo_fini+0x12/0x40 [radeon] [83523.616057] cik_fini+0xca/0xf0 [radeon] [83523.616065] radeon_device_fini+0x35/0x110 [radeon] [83523.616072] radeon_driver_unload_kms+0x4b/0x80 [radeon] [83523.616077] drm_dev_unregister+0x3c/0xe0 [drm] [83523.616083] drm_put_dev+0x32/0x60 [drm] [83523.616089] radeon_pci_remove+0x15/0x20 [radeon] [83523.616092] pci_device_remove+0x39/0xb0 [83523.616094] device_release_driver_internal+0x158/0x210 [83523.616095] driver_detach+0x38/0x70 [83523.616096] bus_remove_driver+0x59/0xd0 [83523.616097] driver_unregister+0x2c/0x40 [83523.616098] pci_unregister_driver+0x22/0xb0 [83523.616103] drm_pci_exit+0xbb/0xc0 [drm] [83523.616115] radeon_exit+0x1c/0x43 [radeon] [83523.616116] SyS_delete_module+0x1a8/0x2b0 [83523.616118] ? exit_to_usermode_loop+0x91/0xb0 [83523.616120] entry_SYSCALL_64_fastpath+0x1a/0xa5 [83523.616121] RIP: 0033:0x7efc64a93917 [83523.616122] RSP: 002b:00007ffdd5e175f8 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0 [83523.616123] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007efc64a93917 [83523.616123] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 0000564a18d45ea8 [83523.616123] RBP: 0000000000000000 R08: 00007ffdd5e165a1 R09: 0000000000000000 [83523.616124] R10: 00007efc64b0cbc0 R11: 0000000000000206 R12: 0000564a18d45e40 [83523.616124] R13: 00007ffdd5e16610 R14: 0000564a18d45ea8 R15: 00007ffdd5e189e0 [83523.616125] Code: 00 ad de 48 89 df 48 89 03 48 05 00 01 00 00 48 89 43 08 e8 7b 35 f6 da 48 8b 3d 14 63 00 00 e8 af 46 5b db 5b 41 5c 41 5d 5d c3 <0f> ff eb b0 0f 1f 40 00 0f 1f 44 00 00 48 8b 06 48 85 c0 74 13 [83523.616141] ---[ end trace 64292c2a3a933def ]--- [83523.616779] [TTM] Zone kernel: Used memory at exit: 2080 kiB [83523.616781] [TTM] Zone dma32: Used memory at exit: 24 kiB [83523.616782] [drm] radeon: ttm finalized [83523.642072] [drm] Module unloaded This doesn't depend on whether the GPU experienced VM errors prior to modprobe -r. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 103300] Tear rendering bug in Bioshock Infinite
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=103300 Bug ID: 103300 Summary: Tear rendering bug in Bioshock Infinite Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: ianbruene(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 134870 --> https://bugs.freedesktop.org/attachment.cgi?id=134870&action=edit What is Running Ubuntu 17.04, kernel 4.12.11, mesa 17.2.2 padoka-stable (but it appeared in an earlier version), RX 460. In Bioshock Infinite there are "tears" which graphically consist of a swirly glowy cloud thing and a sprite that looks like a tear with static inside. When I encounter them the sprite is missing. This only effects the tears that have the "static" in them (the music, three truths, and Elizabeth screaming ones), but does not effect any of the story or combat tears. What few tests I know how to do eliminate corruption in the installation (steam verifies it), or corrupted shader cache (deleted that). I am *not* certain that this is a driver bug, but it seems to lean in that direction. Attached is a screenshot of how it looks on my system, vs how it should look. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 102962] GPU crash running Overwatch in wine-staging
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102962 Bug ID: 102962 Summary: GPU crash running Overwatch in wine-staging Product: Mesa Version: 17.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: tobi291019(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Running Overwatch in wine-staging 2.17 or 2.16 causes frequent GPU crashes, in particular almost always when selecting Symmetra in the Hero Selection screen. As far as I can tell there is no version of wine-staging (including specific commits) that avoid this issue. Interestingly, a patched version of wine-staging 2.16 and earlier (https://github.com/gamax92/wine-overwatch) does not seem to trigger this at all. (I suspect their removal of some wined3d related patches started to trigger this, whilst the earlier version avoided it.) No errors are shown on both wine's and mesa's end, although I have not successfully tried a build with -DDEBUG CFLAG, which I could try in case this is helpful. I have tried working out which of the patches applied by the repository are avoiding the issue, but haven't work out any good leads. Running on Arch Linux with linux 4.13.3 (Custom compiled with unrelated patches) and mesa 17.2.1. The issue can be reproduced both with the standard wine-staging package on Arch as well as compiling the mentioned patched version. It might be worthwile to contact the wine developers about this, but their bug reporting guidelines specifically say to not report driver issues there, so I decided to report here first. -- You are receiving this mail because: You are the assignee for the bug.

1 17

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019