mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2021-01-14T17:31:05Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1305GPU lock-up when running QT5 based celestia2021-01-14T17:31:05ZBugzilla Migration UserGPU lock-up when running QT5 based celestia## Submitted by Hleb Valoshka
Assigned to **mes..@..op.org**
**[Link to original bug (#105240)](https://bugs.freedesktop.org/show_bug.cgi?id=105240)**
## Description
Created attachment 137587
apitrace trace
GPU: HD7750
Kernel: 4....## Submitted by Hleb Valoshka
Assigned to **mes..@..op.org**
**[Link to original bug (#105240)](https://bugs.freedesktop.org/show_bug.cgi?id=105240)**
## Description
Created attachment 137587
apitrace trace
GPU: HD7750
Kernel: 4.14.17 (Debian package)
Driver: both radeon and amdgpu
Mesa: 17.3.4
LLVM: 5
When I start QT5 fork of celestia, my GPU gets locked. With radeon I have a few seconds to switch to a terminal, with amdgpu I don't, sometimes everything is locked so even REISUB doesn't help.
Even apitrace dump-images locks.
Feb 24 23:07:50 deneb kernel: [ 7701.664110] radeon 0000:01:00.0: ring 0 stalled for more than 10244msec
Feb 24 23:07:50 deneb kernel: [ 7701.664118] radeon 0000:01:00.0: ring 3 stalled for more than 10244msec
Feb 24 23:07:50 deneb kernel: [ 7701.664129] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000168b3f last fence id 0x0000000000168cdb on ring 3)
Feb 24 23:07:50 deneb kernel: [ 7701.664513] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000ae7cc last fence id 0x00000000000ae85f on ring 0)
Feb 24 23:07:50 deneb kernel: [ 7701.718269] do_general_protection: 15 callbacks suppressed
Feb 24 23:07:50 deneb kernel: [ 7701.718272] traps: goldendict[4507] general protection ip:7f3bf7cc3185 sp:7ffedf2ba330 error:0 in libc-2.26.so[7f3bf7c8c000+1ad000]
Feb 24 23:07:50 deneb kernel: [ 7701.936036] radeon_dp_aux_transfer_native: 74 callbacks suppressed
Feb 24 23:07:50 deneb kernel: [ 7702.176091] radeon 0000:01:00.0: ring 3 stalled for more than 10756msec
Feb 24 23:07:50 deneb kernel: [ 7702.176135] radeon 0000:01:00.0: ring 0 stalled for more than 10756msec
Feb 24 23:07:50 deneb kernel: [ 7702.176142] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000ae7cc last fence id 0x00000000000ae85f on ring 0)
Feb 24 23:07:50 deneb kernel: [ 7702.176485] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000168b3f last fence id 0x0000000000168ced on ring 3)
Feb 24 23:07:51 deneb kernel: [ 7702.688091] radeon 0000:01:00.0: ring 0 stalled for more than 11268msec
Feb 24 23:07:51 deneb kernel: [ 7702.688096] radeon 0000:01:00.0: ring 3 stalled for more than 11268msec
**Attachment 137587**, "apitrace trace":
[Celestia_QT.trace](/uploads/073165c6cfc503aef46a835658fe4bc8/Celestia_QT.trace)
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1303clearing related crash in Dying Light2020-09-24T12:52:43ZBugzilla Migration Userclearing related crash in Dying Light## Submitted by Grazvydas Ignotas `@notaz`
Assigned to **Default DRI bug account**
**[Link to original bug (#105140)](https://bugs.freedesktop.org/show_bug.cgi?id=105140)**
## Description
util_format_write_4f() gets called with a ...## Submitted by Grazvydas Ignotas `@notaz`
Assigned to **Default DRI bug account**
**[Link to original bug (#105140)](https://bugs.freedesktop.org/show_bug.cgi?id=105140)**
## Description
util_format_write_4f() gets called with a pipe_format PIPE_FORMAT_Z24_UNORM_S8_UINT that has no pack_rgba_float()
Thread 9 "gallium_drv:0" received signal SIGSEGV, Segmentation fault.
```
[Switching to Thread 0x7f78b1397700 (LWP 30748)]
#0 0x0000000000000000 in ?? ()
#1 0x00007f78baf0e547 in util_format_write_4f (format=PIPE_FORMAT_Z24_UNORM_S8_UINT, src=0x1eb422c, src_stride=0, dst=0x7f78b13963a0,
dst_stride=0, x=0, y=0, w=1, h=1) at util/u_format.c:337
#2 0x00007f78bafd5853 in util_pack_color (rgba=0x1eb422c, format=PIPE_FORMAT_Z24_UNORM_S8_UINT, uc=0x7f78b13963a0)
at ../../../../src/gallium/auxiliary/util/u_pack_color.h:433
#3 0x00007f78bafd5ad0 in si_set_clear_color (rtex=0x141f56e0, surface_format=PIPE_FORMAT_Z24_UNORM_S8_UINT, color=0x1eb422c)
at si_clear.c:89
#4 0x00007f78bafd69f3 in si_do_fast_color_clear (sctx=0x1d60690, buffers=0x7f78b1396474, color=0x1eb422c) at si_clear.c:508
#5 0x00007f78bafd6b29 in si_clear (ctx=0x1d60690, buffers=4, color=0x1eb422c, depth=0, stencil=0) at si_clear.c:527
#6 0x00007f78baf344e7 in tc_batch_execute (job=job@entry=0x1eb4180, thread_index=thread_index@entry=0) at util/u_threaded_context.c:96
#7 0x00007f78badbb03f in util_queue_thread_func (input=input@entry=0x1e81550) at u_queue.c:271
#8 0x00007f78badbabc7 in impl_thrd_routine (p=<optimized out>) at ../../include/c11/threads_posix.h:87
#9 0x00007f78ce8e06ba in start_thread (arg=0x7f78b1397700) at pthread_create.c:333
#10 0x00007f78c734241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
```
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1302radeonsi GPU lockup / crash with wine [The Witcher 3]2021-01-14T16:48:24ZBugzilla Migration Userradeonsi GPU lockup / crash with wine [The Witcher 3]## Submitted by Galym Kerimbekov
Assigned to **Default DRI bug account**
**[Link to original bug (#105089)](https://bugs.freedesktop.org/show_bug.cgi?id=105089)**
## Description
Hi
I have GPU lockup after few minutes of playing T...## Submitted by Galym Kerimbekov
Assigned to **Default DRI bug account**
**[Link to original bug (#105089)](https://bugs.freedesktop.org/show_bug.cgi?id=105089)**
## Description
Hi
I have GPU lockup after few minutes of playing The Witcher 3 (the quest is Ciri's story: The King of the wolves)
I use wine vanilla with patch:
https://raw.githubusercontent.com/wine-compholio/wine-staging/master/patches/wined3d-buffer_create/0001-wined3d-Do-not-pin-large-buffers.patch
I also tried various wine vanilla and wine staging from 2.22 to 3.1.
My specs are:
Radeon R7 350 (02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] (rev 87))
Xorg 1.19.3
Linux 4.14.12
mesa-17.3.1 (I had same issue with mesa-git)
llvm-5.0
OpenGL renderer string: AMD CAPE VERDE (DRM 3.19.0 / 4.14.12-gentoo, LLVM 5.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.1
OpenGL core profile shading language version string: 4.50
Maybe I should do some tests here, but I don't know which of these.
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1301line_smooth in the endpoints is not take effect2020-09-24T12:47:48ZBugzilla Migration Userline_smooth in the endpoints is not take effect## Submitted by yha..@..63.com
Assigned to **Default DRI bug account**
**[Link to original bug (#104696)](https://bugs.freedesktop.org/show_bug.cgi?id=104696)**
## Description
When use line_smooth, if it's a oblique line and make ...## Submitted by yha..@..63.com
Assigned to **Default DRI bug account**
**[Link to original bug (#104696)](https://bugs.freedesktop.org/show_bug.cgi?id=104696)**
## Description
When use line_smooth, if it's a oblique line and make the wide bigger you will find the line_smooth is effect in the middle of the line but in the end of line it's like a line not use line_smooth, but if we use the swrast the line is look good.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1300[amdgpu/radeon][regression, CIK] Prefetch the compute shader to TC L2 (4a4ff6...2020-09-24T12:50:00ZBugzilla Migration User[amdgpu/radeon][regression, CIK] Prefetch the compute shader to TC L2 (4a4ff66dbe) causes GPU VM errors when running OpenCL kernels on Hawaii## Submitted by Vedran Miletić
Assigned to **Default DRI bug account**
**[Link to original bug (#104604)](https://bugs.freedesktop.org/show_bug.cgi?id=104604)**
## Description
Commit 4a4ff66dbe radeonsi: also prefetch compute shad...## Submitted by Vedran Miletić
Assigned to **Default DRI bug account**
**[Link to original bug (#104604)](https://bugs.freedesktop.org/show_bug.cgi?id=104604)**
## Description
Commit 4a4ff66dbe radeonsi: also prefetch compute shaders enabled prefetching the compute shader to TC L2 for CIK+. This causes GPU VM errors on Hawaii, Kabini, and likely other CIK GPUs when running certain OpenCL programs (it seems that the key is to call clCreateContext() twice or more, see below) with Clover, both with amdgpu and radeon kernel drivers. I have tested with
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT GL [FirePro W9100] [1002:67a0]
on Fedora rawhide (28) with kernel 4.15.0-0.rc7.git2.1.fc28.x86_64.
I'll minimize the example program that causes this (right now using GROMACS tests, but that's unnecessarily complex), and provide the details (grepped + full dmesg) in the comments for both amdgpu and radeon kernel drivers.
Version: 17.1
### Blocking
* [Bug 99553](https://bugs.freedesktop.org/show_bug.cgi?id=99553)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1299[bisected] Compton weird colors2020-09-17T10:37:08ZBugzilla Migration User[bisected] Compton weird colors## Submitted by Christoph Haag
Assigned to **Default DRI bug account**
**[Link to original bug (#104597)](https://bugs.freedesktop.org/show_bug.cgi?id=104597)**
## Description
Created attachment 136675
Desktop with compton --backe...## Submitted by Christoph Haag
Assigned to **Default DRI bug account**
**[Link to original bug (#104597)](https://bugs.freedesktop.org/show_bug.cgi?id=104597)**
## Description
Created attachment 136675
Desktop with compton --backend glx
RX 480, mesa master.
Running compton --backend glx produces the effect in the attached image. The colors are corrupted, but some applications look correct.
There is one situation where I have seen a similar effect not involving compton and that is kwin's window preview of SteamVR's vrmonitor: https://www.youtube.com/watch?v=IHHQS_Q5uqE. All other window previews work correctly, it's only the vrmonitor that's broken.
But that's enough to say it's not a compton specific problem.
**Attachment 136675**, "Desktop with compton --backend glx":
![Screenshot_20180112_122452](/uploads/6b949883a06f6d138a0eb61a3c6d5c6f/Screenshot_20180112_122452.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1298[apitrace] GPU hang with janusvr (non-VR mode too)2020-09-24T14:38:41ZBugzilla Migration User[apitrace] GPU hang with janusvr (non-VR mode too)## Submitted by Christoph Haag
Assigned to **Default DRI bug account**
**[Link to original bug (#104596)](https://bugs.freedesktop.org/show_bug.cgi?id=104596)**
## Description
RX 480, mesa master, drm-next-4.16-wip d9c47236f500494...## Submitted by Christoph Haag
Assigned to **Default DRI bug account**
**[Link to original bug (#104596)](https://bugs.freedesktop.org/show_bug.cgi?id=104596)**
## Description
RX 480, mesa master, drm-next-4.16-wip d9c47236f500494614a0d3a8e24d70e3c4da9efd (I'll have to try with mainline too)
To reproduce
Download JanusVR: http://downloads.janusvr.com/janusvr_linux.tar.gz
Run ./janusvr -render 2d
Click on the VR Sites Subreddit Tile.
GPU hang
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1297GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms...2019-09-25T23:15:05ZBugzilla Migration UserGPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video## Submitted by Luis Mendes
Assigned to **Default DRI bug account**
**[Link to original bug (#104481)](https://bugs.freedesktop.org/show_bug.cgi?id=104481)**
## Description
Created attachment 136527
dmesg and iomem data from locku...## Submitted by Luis Mendes
Assigned to **Default DRI bug account**
**[Link to original bug (#104481)](https://bugs.freedesktop.org/show_bug.cgi?id=104481)**
## Description
Created attachment 136527
dmesg and iomem data from lockup obtained with glretrace
I am getting GPU lockups while playing video on Kodi, but it also happened with other applications that play video, while OpenGL seems to be stable.
The system seem to be more sensitive to VP9 encoded videos. The freeze happens both on amd64 as well as on armv7l platforms.
I am also able to reproduce GPU hangs on amd64 while replaying a glretrace obtained with kodi on arm platform.
The arm dmesg and traces show a clear GPU lockup, while amd64 dmesg isn't so clear, but the user experience is just the same, complete graphical system freeze, while machine is still working with ssh or remote connections.
Please find amd64 logs in attachments, including iomem, dmesg and gdb traces.
In both platforms I am using Ubuntu 17.10 with Mate desktop, and lightdm session manager, with libdrm-2.4.89, mesa-17.4 at commit "radv: Implement binning on GFX9." - 6a36bfc64d2096aa338958c4605f5fc6372c07b8 and kernel https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.16 at commit "drm/amdgpu: Correct the IB size of bo update mapping." - 104bd2ca1124dfd9aa904d5f5a96253ef2b580f6.
Please note that the system was more stable a few weeks ago with drm-next-4.16 based on kernel 4.15-rc2, and a previous mesa version, I don't remember the actual commits, but despite it was more stable, both on arm as well as on amd64, both systems still crashed similarly, it just got more evident with these new versions.
There are two distinct crash behaviours on amd64: the ones that I obtained while playing a video with kodi on amd64 and those that I obtained on amd64 by replaying an apitrace from the arm platform while playing a VP9 video with kodi.
The first kind of crashes is detailed with logs kodi-processes_and_backtraces.txt and kodi-amdgpu_lockup_dmesg_and_iomem.txt.
The second kind of crashes is detailed with logs glretrace-processes_and_backtraces.txt and glretrace-amdgpu_lockup_dmesg_and_iomem.txt.
For some strange reason the amd64 platform is complaining about polaris11 firmware files, but they are in /lib/firmware and they taken by cloning https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git. I am using the same firmware files on armv7l and the same graphics card and it doesn't complain with the firmware.
I can also provide the apitrace trace file, but it takes around 1GB of data.
**Attachment 136527**, "dmesg and iomem data from lockup obtained with glretrace":
[glretrace-amdgpu_lockup_dmesg_and_iomem.txt](/uploads/c22615b5f621fbfe8981eac7fa35f42a/glretrace-amdgpu_lockup_dmesg_and_iomem.txt)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1295GPU fault detected on wine-nine Path of Exile2020-05-30T11:10:42ZBugzilla Migration UserGPU fault detected on wine-nine Path of Exile## Submitted by Vladimir Usikov
Assigned to **Default DRI bug account**
**[Link to original bug (#104362)](https://bugs.freedesktop.org/show_bug.cgi?id=104362)**
## Description
Created attachment 136347
dmesg log
When i start gam...## Submitted by Vladimir Usikov
Assigned to **Default DRI bug account**
**[Link to original bug (#104362)](https://bugs.freedesktop.org/show_bug.cgi?id=104362)**
## Description
Created attachment 136347
dmesg log
When i start game Path of Exile on wine-nine computer freez.
I can`t switch in kernel console.
When i connect on ssh i can get dmesg output.
Radeon HD 7950 (TAHITI)
kernel 4.13.4 - 4.14.6
kernel module AMDGPU
Mesa 17.2.1 - 17.3.1
wine-nine 2.20 - 2.21
**Attachment 136347**, "dmesg log":
[poe-dmesg.log](/uploads/b01b3ea7d7bc6336f4ebb415a59e7d95/poe-dmesg.log)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1294AMD RX 580: Hide/Show Chromium sometimes corrupts screen (see screenshot)2021-05-27T08:20:46ZBugzilla Migration UserAMD RX 580: Hide/Show Chromium sometimes corrupts screen (see screenshot)## Submitted by Arthur Borsboom
Assigned to **Default DRI bug account**
**[Link to original bug (#104347)](https://bugs.freedesktop.org/show_bug.cgi?id=104347)**
## Description
Created attachment 136316
Screenshot of scrambled win...## Submitted by Arthur Borsboom
Assigned to **Default DRI bug account**
**[Link to original bug (#104347)](https://bugs.freedesktop.org/show_bug.cgi?id=104347)**
## Description
Created attachment 136316
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.
**Attachment 136316**, "Screenshot of scrambled window":
![2017-12-20-102624_3520x1200_scrot](/uploads/262d41c32221b477c265c3f0381add49/2017-12-20-102624_3520x1200_scrot.png)
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1293X-Server hangs with showing scrambled picture, sound still playing.2021-11-26T14:43:32ZBugzilla Migration UserX-Server hangs with showing scrambled picture, sound still playing.## Submitted by bernhardu
Assigned to **Default DRI bug account**
**[Link to original bug (#104345)](https://bugs.freedesktop.org/show_bug.cgi?id=104345)**
## Description
Created attachment 136312
kernel output captured from the s...## Submitted by bernhardu
Assigned to **Default DRI bug account**
**[Link to original bug (#104345)](https://bugs.freedesktop.org/show_bug.cgi?id=104345)**
## Description
Created attachment 136312
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@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?
**Attachment 136312**, "kernel output captured from the serial line.":
[log_2017-12-19_11-56-02.log.bz2](/uploads/2b9b23648a1be6c7183e0da451c44361/log_2017-12-19_11-56-02.log.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1292radeon ring 0 stalled for more than ... radeon ... GPU lockup ...2021-05-27T08:20:15ZBugzilla Migration Userradeon ring 0 stalled for more than ... radeon ... GPU lockup ...## Submitted by nar..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#104307)](https://bugs.freedesktop.org/show_bug.cgi?id=104307)**
## Description
Created attachment 136241
apitrace trace --api gl ./a....## Submitted by nar..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#104307)](https://bugs.freedesktop.org/show_bug.cgi?id=104307)**
## Description
Created attachment 136241
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)
**Attachment 136241**, "apitrace trace --api gl ./a.out ; mv a.out.trace a.out.mesa-17.2.7.trace":
[a.out.mesa-17.2.7.trace](/uploads/6f21e589955060264f38172134ae9d7d/a.out.mesa-17.2.7.trace)
Version: 17.2
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=102909
* https://bugs.freedesktop.org/show_bug.cgi?id=107545
* https://bugs.freedesktop.org/show_bug.cgi?id=101712https://gitlab.freedesktop.org/mesa/mesa/-/issues/1291[polaris10][arm] blurred screen on AMD Radeon Pro WX 71002021-05-27T08:21:14ZBugzilla Migration User[polaris10][arm] blurred screen on AMD Radeon Pro WX 7100## Submitted by Vedran Miletić
Assigned to **Default DRI bug account**
**[Link to original bug (#104266)](https://bugs.freedesktop.org/show_bug.cgi?id=104266)**
## Description
Created attachment 136175
Photo
From ML Mesa-dev:
htt...## Submitted by Vedran Miletić
Assigned to **Default DRI bug account**
**[Link to original bug (#104266)](https://bugs.freedesktop.org/show_bug.cgi?id=104266)**
## Description
Created attachment 136175
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.)
**Attachment 136175**, "Photo":
![blurred-screen](/uploads/256c7e0a283df8e1818b3d33741edf58/blurred-screen.jpg)
Version: 17.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1290[radeonsi] The Witcher 3 freezes the system (POLARIS10)2019-10-03T07:29:40ZBugzilla Migration User[radeonsi] The Witcher 3 freezes the system (POLARIS10)## Submitted by Shmerl
Assigned to **Default DRI bug account**
**[Link to original bug (#104193)](https://bugs.freedesktop.org/show_bug.cgi?id=104193)**
## Description
Created attachment 136068
The Witcher 3: rotfiends radeonsi fr...## Submitted by Shmerl
Assigned to **Default DRI bug account**
**[Link to original bug (#104193)](https://bugs.freedesktop.org/show_bug.cgi?id=104193)**
## Description
Created attachment 136068
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&collapsed=&headers=1&format=raw
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/patches/wined3d-buffer_create/0001-wined3d-Do-not-pin-large-buffers.patch
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)
**Attachment 136068**, "The Witcher 3: rotfiends radeonsi freeze":
[tw3_rotfiends_mesa_freeze.tar.xz](/uploads/e183d285f1be8232eb1f6417082307ab/tw3_rotfiends_mesa_freeze.tar.xz)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1288Undertale crashes on startup (compiling shaders?)2020-03-24T08:53:22ZBugzilla Migration UserUndertale crashes on startup (compiling shaders?)## Submitted by John Steele Scott
Assigned to **Default DRI bug account**
**[Link to original bug (#103915)](https://bugs.freedesktop.org/show_bug.cgi?id=103915)**
## Description
Created attachment 135727
thread apply all bt full
...## Submitted by John Steele Scott
Assigned to **Default DRI bug account**
**[Link to original bug (#103915)](https://bugs.freedesktop.org/show_bug.cgi?id=103915)**
## Description
Created attachment 135727
thread apply all bt full
Mesa 17.2.6 self-compiled, running on Debian Stretch
OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (AMD POLARIS10 / DRM 3.10.0 / 4.11.0-0.bpo.1-amd64, LLVM 5.0.0)
I picked up Undertale <http://store.steampowered.com/app/391540/Undertale/> today, tried to play it but it crashes on startup with the following backtrace:
Core was generated by `/pool/toojays/steam/SteamApps/common/Undertale/runner'.
Program terminated with signal SIGSEGV, Segmentation fault.
```
Thread 9 (Thread 0xe817fb40 (LWP 28800)):
#0 0xf775bc89 in __kernel_vsyscall ()
#1 0xf73fcb9b in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2 0xef9a21da in cnd_wait (mtx=0xa74e410, cond=0xa74e428) at ../../include/c11/threads_posix.h:159
#3 util_queue_thread_func (input=0xa5a98a8) at u_queue.c:171
#4 0xf73f727a in start_thread (arg=0xe817fb40) at pthread_create.c:333
#5 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 8 (Thread 0xe91e1b40 (LWP 28798)):
#0 0xf775bc89 in __kernel_vsyscall ()
#1 0xf73fcb9b in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2 0xef9a21da in cnd_wait (mtx=0xa6b2324, cond=0xa6b233c) at ../../include/c11/threads_posix.h:159
#3 util_queue_thread_func (input=0xa5d1580) at u_queue.c:171
#4 0xf73f727a in start_thread (arg=0xe91e1b40) at pthread_create.c:333
#5 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 7 (Thread 0xebb5eb40 (LWP 28793)):
#0 0xf775bc89 in __kernel_vsyscall ()
#1 0xf73fcb9b in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2 0xef9a21da in cnd_wait (mtx=0xa6b1874, cond=0xa6b188c) at ../../include/c11/threads_posix.h:159
#3 util_queue_thread_func (input=0xa5cf958) at u_queue.c:171
#4 0xf73f727a in start_thread (arg=0xebb5eb40) at pthread_create.c:333
#5 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 6 (Thread 0xf6be5700 (LWP 28792)):
#0 0xf775bc89 in __kernel_vsyscall ()
#1 0xf73fcb9b in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2 0xef9a258a in cnd_wait (mtx=0xa7ac650, cond=0xa7ac668) at ../../include/c11/threads_posix.h:159
#3 util_queue_fence_wait (fence=0xa7ac650) at u_queue.c:106
#4 0xefbf991c in si_shader_select_with_key (sscreen=0xa6b1e50, state=state@entry=0xa6cd97c, compiler_state=compiler_state@entry=0xffea3dec, key=0xffea3ca4, thread_index=-1) at si_state_shaders.c:1596
#5 0xefbfa3c9 in si_shader_select (ctx=ctx@entry=0xa6ccec0, state=state@entry=0xa6cd97c, compiler_state=compiler_state@entry=0xffea3dec) at si_state_shaders.c:1753
#6 0xefbfc76f in si_update_shaders (sctx=0xa6ccec0) at si_state_shaders.c:3222
#7 0xefbf45e6 in si_draw_vbo (ctx=<optimized out>, info=<optimized out>) at si_state_draw.c:1266
#8 0xefaa2f91 in util_draw_arrays (start=0, count=3, mode=PIPE_PRIM_MAX, pipe=0xa6ccec0) at ./util/u_draw.h:66
#9 util_draw_vertex_buffer (pipe=0xa6ccec0, cso=0x0, vbuf=0xa7ac4a0, vbuf_slot=0, offset=0, prim_type=15, num_verts=3, num_attribs=2) at util/u_draw_quad.c:68
#10 0xefc32c6d in r600_draw_rectangle (blitter=0xa6976f0, x1=0, y1=0, x2=640, y2=480, depth=1, type=UTIL_BLITTER_ATTRIB_COLOR, attrib=0xa74e56c) at r600_pipe_common.c:239
#11 0xefa9f22b in util_blitter_clear_custom (blitter=0xa6976f0, width=640, height=480, num_layers=1, clear_buffers=7, color=0xa74e56c, depth=1, stencil=0, custom_dsa=0x0, custom_blend=0x0) at util/u_blitter.c:1406
#12 0xefa9f333 in util_blitter_clear (blitter=<optimized out>, width=<optimized out>, height=<optimized out>, num_layers=<optimized out>, clear_buffers=<optimized out>, color=<optimized out>, depth=<optimized out>, stencil=0) at util/u_blitter.c:1422
#13 0xefbc2102 in si_clear (ctx=0xa6ccec0, buffers=<optimized out>, color=0xa74e56c, depth=1, stencil=0) at si_blit.c:893
#14 0xefac48e1 in tc_call_clear (pipe=0xa6ccec0, payload=0xa74e568) at util/u_threaded_context.c:2073
#15 0xefac51bf in tc_batch_execute (thread_index=0, job=0xa74e4c0) at util/u_threaded_context.c:94
#16 _tc_sync (tc=tc@entry=0xa74e220, func=<optimized out>, info=<optimized out>) at util/u_threaded_context.c:185
#17 0xefac7777 in tc_texture_subdata (_pipe=0xa74e220, resource=0xa7a8ad0, level=0, usage=0, box=0xffea4208, data=0xa7a83d0, stride=64, layer_stride=1024) at util/u_threaded_context.c:1631
#18 0xef8ae3ba in st_TexSubImage (ctx=0xa756088, dims=2, texImage=<optimized out>, xoffset=0, yoffset=<optimized out>, zoffset=0, width=16, height=<optimized out>, depth=1, format=6408, type=5121, pixels=0xa7a83d0, unpack=0xa76e830) at state_tracker/st_cb_texture.c:1418
#19 0xef8afe6c in st_TexImage (ctx=0xa756088, dims=2, texImage=0xa6b8ab8, format=6408, type=5121, pixels=0xa7a83d0, unpack=0xa76e830) at state_tracker/st_cb_texture.c:1635
#20 0xef831165 in teximage (no_error=false, pixels=0xa7a83d0, imageSize=0, type=5121, format=6408, border=0, depth=<optimized out>, height=<optimized out>, width=<optimized out>, internalFormat=6408, level=0, target=3553, dims=2, compressed=0 '\000', ctx=0xa756088) at main/teximage.c:3055
#21 teximage_err (ctx=0xa756088, compressed=compressed@entry=0 '\000', dims=dims@entry=2, target=3553, level=0, internalFormat=<optimized out>, width=16, height=16, depth=1, border=<optimized out>, format=6408, type=5121, imageSize=0, pixels=0xa7a83d0) at main/teximage.c:3081
#22 0xef83310a in _mesa_TexImage2D (target=3553, level=0, internalFormat=6408, width=16, height=16, border=0, format=6408, type=5121, pixels=0xa7a83d0) at main/teximage.c:3119
#23 0x08303d5d in ?? ()
#24 0x08302a5e in ?? ()
#25 0x08303c2e in ?? ()
#26 0x083027c4 in ?? ()
#27 0x0830287f in ?? ()
#28 0x082fd629 in ?? ()
#29 0x081001fa in ?? ()
#30 0x081be8c3 in ?? ()
#31 0x082f7eda in ?? ()
#32 0x0831d356 in ?? ()
#33 0xf6e43276 in __libc_start_main (main=0x831d180, argc=1, argv=0xffea5c14, init=0x8351350, fini=0x83513c0, rtld_fini=0xf776d080 <_dl_fini>, stack_end=0xffea5c0c) at ../csu/libc-start.c:291
#34 0x08051525 in ?? ()
Thread 5 (Thread 0xe89e0b40 (LWP 28799)):
#0 0xf775bc89 in __kernel_vsyscall ()
#1 0xf73fcb9b in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2 0xef9a21da in cnd_wait (mtx=0xa6b2324, cond=0xa6b233c) at ../../include/c11/threads_posix.h:159
#3 util_queue_thread_func (input=0xa5ad7f0) at u_queue.c:171
#4 0xf73f727a in start_thread (arg=0xe89e0b40) at pthread_create.c:333
#5 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 4 (Thread 0xe99e2b40 (LWP 28797)):
#0 0xec2e3fc0 in llvm::VectorType::get(llvm::Type*, unsigned int) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#1 0xec21926c in LLVMVectorType () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#2 0xefc4dee5 in ac_llvm_context_init (ctx=0xe99e10f8, context=0xa5720f8, chip_class=VI) at common/ac_llvm_build.c:68
#3 0xefbe995f in si_llvm_context_init (ctx=<optimized out>, sscreen=<optimized out>, tm=<optimized out>) at si_shader_tgsi_setup.c:1196
#4 0xefbd37aa in si_init_shader_ctx (ctx=ctx@entry=0xe99e03b0, sscreen=sscreen@entry=0xa6b1e50, tm=tm@entry=0xa6b92d8) at si_shader.c:5371
#5 0xefbe085d in si_compile_tgsi_shader (sscreen=0xa6b1e50, tm=0xa6b92d8, shader=0xe7400470, is_monolithic=false, debug=0x0) at si_shader.c:6147
#6 0xefbf9b8c in si_init_shader_selector_async (job=0xa7ab748, thread_index=2) at si_state_shaders.c:1840
#7 0xef9a228b in util_queue_thread_func (input=0xa5a98a8) at u_queue.c:187
#8 0xf73f727a in start_thread (arg=0xe99e2b40) at pthread_create.c:333
#9 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 3 (Thread 0xea1e3b40 (LWP 28796)):
#0 __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:152
#1 0xf6e98fb7 in malloc_printerr (action=<optimized out>, str=0xf6f88d80 "free(): invalid pointer", ptr=<optimized out>, ar_ptr=0xf6fdf780 <main_arena>) at malloc.c:5049
#2 0xf6e997f6 in _int_free (av=0xf6fdf780 <main_arena>, p=0xef67e9fd <llvm::AllAnalysesOn<llvm::LazyCallGraph::SCC>::SetKey+5>, have_lock=0) at malloc.c:3905
#3 0x0834ff7f in operator delete(void*) ()
#4 0xec2a039c in void std::vector<std::pair<void const*, llvm::Pass*>, std::allocator<std::pair<void const*, llvm::Pass*> > >::_M_emplace_back_aux<std::pair<void const*, llvm::Pass*> const&>(std::pair<void const*, llvm::Pass*> const&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#5 0xec2a4bbb in llvm::PMDataManager::initializeAnalysisImpl(llvm::Pass*) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#6 0xecf07c45 in ?? () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#7 0xec2a9f2a in llvm::legacy::PassManagerImpl::run(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#8 0xec2aa10f in llvm::legacy::PassManager::run(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#9 0xec22514c in LLVMRunPassManager () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#10 0xefbea0ec in si_llvm_optimize_module (ctx=0xea1e13b0) at si_shader_tgsi_setup.c:1420
#11 0xefbe0964 in si_compile_tgsi_shader (sscreen=0xa6b1e50, tm=0xa6b8cf0, shader=0xe7700470, is_monolithic=false, debug=0x0) at si_shader.c:6341
#12 0xefbf9b8c in si_init_shader_selector_async (job=0xa7a6758, thread_index=1) at si_state_shaders.c:1840
#13 0xef9a228b in util_queue_thread_func (input=0xa5ad7f0) at u_queue.c:187
#14 0xf73f727a in start_thread (arg=0xea1e3b40) at pthread_create.c:333
#15 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 2 (Thread 0xeb21cb40 (LWP 28794)):
#0 0xf775bc89 in __kernel_vsyscall ()
#1 0xf73fcb9b in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2 0xef9a21da in cnd_wait (mtx=0xa6b5bd0, cond=0xa6b5be8) at ../../include/c11/threads_posix.h:159
#3 util_queue_thread_func (input=0xa599ec8) at u_queue.c:171
#4 0xf73f727a in start_thread (arg=0xeb21cb40) at pthread_create.c:333
#5 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
Thread 1 (Thread 0xea9e4b40 (LWP 28795)):
#0 0xecd20da0 in ?? () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#1 0xec2a951b in llvm::FPPassManager::runOnFunction(llvm::Function&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#2 0xec2a95b2 in llvm::FPPassManager::runOnModule(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#3 0xec2a9f2a in llvm::legacy::PassManagerImpl::run(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#4 0xec2aa10f in llvm::legacy::PassManager::run(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#5 0xed37e09f in ?? () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#6 0xed37e260 in LLVMTargetMachineEmitToMemoryBuffer () from /usr/lib/i386-linux-gnu/libLLVM-5.0.so.1
#7 0xefbe8597 in si_llvm_compile (M=0xe76015c8, binary=0xe760052c, tm=0xa6b78e8, debug=0x0) at si_shader_tgsi_setup.c:134
#8 0xefbdf395 in si_compile_llvm (sscreen=sscreen@entry=0xa6b1e50, binary=binary@entry=0xe760052c, conf=conf@entry=0xe7600560, tm=0xa6b78e8, mod=0xe76015c8, debug=0x0, processor=1, name=0xefd11a3c "TGSI shader") at si_shader.c:5070
#9 0xefbe0abf in si_compile_tgsi_shader (sscreen=0xa6b1e50, tm=0xa6b78e8, shader=0xe7600470, is_monolithic=false, debug=0x0) at si_shader.c:6351
#10 0xefbf9b8c in si_init_shader_selector_async (job=0xa7a54e0, thread_index=0) at si_state_shaders.c:1840
#11 0xef9a228b in util_queue_thread_func (input=0xa5a98a8) at u_queue.c:187
#12 0xf73f727a in start_thread (arg=0xea9e4b40) at pthread_create.c:333
#13 0xf6f12b56 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:110
```
Full backtrace attached.
FWIW it launches okay on my laptop running Ubuntu 16.04 / Mesa 17.2.4 / Iris Graphics 540.
~~**Attachment 135727**~~, "thread apply all bt full":
[undertale-full-bt.txt](/uploads/680cff7bd2a9009ec6d5e83d381f595a/undertale-full-bt.txt)
Version: 17.2
### Depends on
* [Bug 105797](https://bugs.freedesktop.org/show_bug.cgi?id=105797)
### Blocking
* [Bug 77449](https://bugs.freedesktop.org/show_bug.cgi?id=77449)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1287Unity based games do not start2020-09-11T07:31:23ZBugzilla Migration UserUnity based games do not start## Submitted by bar..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#103769)](https://bugs.freedesktop.org/show_bug.cgi?id=103769)**
## Description
Created attachment 135499
Crash of Layers of Fear
Hi,...## Submitted by bar..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#103769)](https://bugs.freedesktop.org/show_bug.cgi?id=103769)**
## Description
Created attachment 135499
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.
**Attachment 135499**, "Crash of Layers of Fear":
[lof.txt](/uploads/7d1266a79dc600d2e9dd5f130c31fa7a/lof.txt)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1286[Hawaii, FirePro, radeon] WARNING: CPU: 1 PID: 18632 at drivers/gpu/drm/ttm/t...2021-01-14T16:52:24ZBugzilla Migration User[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]## Submitted by Vedran Miletić
Assigned to **Default DRI bug account**
**[Link to original bug (#103316)](https://bugs.freedesktop.org/show_bug.cgi?id=103316)**
## Description
On kernel 4.13.6-300.fc27.x86_64, with 01:00.0 VGA com...## Submitted by Vedran Miletić
Assigned to **Default DRI bug account**
**[Link to original bug (#103316)](https://bugs.freedesktop.org/show_bug.cgi?id=103316)**
## Description
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.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1285Tear rendering bug in Bioshock Infinite2021-05-27T08:11:43ZBugzilla Migration UserTear rendering bug in Bioshock Infinite## Submitted by Ian Bruene
Assigned to **Default DRI bug account**
**[Link to original bug (#103300)](https://bugs.freedesktop.org/show_bug.cgi?id=103300)**
## Description
Created attachment 134870
What is
Running Ubuntu 17.04, k...## Submitted by Ian Bruene
Assigned to **Default DRI bug account**
**[Link to original bug (#103300)](https://bugs.freedesktop.org/show_bug.cgi?id=103300)**
## Description
Created attachment 134870
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.
**Attachment 134870**, "What is":
![Screenshot_at_2017-10-11_15-30-54](/uploads/acf2028f7488301fc20d287831c71167/Screenshot_at_2017-10-11_15-30-54.png)
Version: 17.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1283HyperZ related rendering issue in ARK: Survival Evolved2020-03-24T07:28:20ZBugzilla Migration UserHyperZ related rendering issue in ARK: Survival Evolved## Submitted by Elliot Thomas
Assigned to **Default DRI bug account**
**[Link to original bug (#102955)](https://bugs.freedesktop.org/show_bug.cgi?id=102955)**
## Description
Created attachment 134449
The back buffer of apitrace f...## Submitted by Elliot Thomas
Assigned to **Default DRI bug account**
**[Link to original bug (#102955)](https://bugs.freedesktop.org/show_bug.cgi?id=102955)**
## Description
Created attachment 134449
The back buffer of apitrace frame 1017, showing red lines along what looks like primitive edges.
Hi,
I've been poking "ARK: Survival Evolved", trying to get it playable.
The game is notoriously buggy, particularly under Linux, however the biggest issue I've had seems to be a Mesa/Radeon bug.
Blocky "pixelated" lines are drawn across what look like edges (see attached). These lines are most frequently red, black or cyan in colour, and seem to disappear when the scene complexity is lower (like when looking at the floor or an area with no foliage or rocks).
Setting R600_DEBUG=nohyperz resolves the issue.
I've tested an apitrace of the game on both Mesa git, and 17.2.1 on a desktop with a POLARIS10 (RX580 8GiB), running the latest amd-staging-drm-next kernel, and on a laptop with both Intel integrated graphics and a HAINAN (Sun XT? 8670M), running a stock Archlinux kernel.
Both AMD cards have this rendering issue with HyperZ enabled. The Intel card renders without this particular problem (if slowly), and llvmpipe (eventually) renders without issue too.
Apitrace (~600MiB!):
https://drive.google.com/open?id=0B6RX1ZACoaJ5UmhDWDM3ZC03eUk
Desktop:
Linux 4.13.0-rc5-43dd6fde5df4 #3 SMP PREEMPT Thu Sep 21 19:15:33 BST 2017 x86_64 GNU/Linux
Mesa 17.3.0-devel (git hash #52ed3bca91ff13217378196d6800ca7113641a63)
libdrm 2.4.83, LLVM 5.0.0
Laptop:
Linux 4.12.13-1-ARCH #1 SMP PREEMPT Fri Sep 15 06:36:43 UTC 2017 x86_64 GNU/Linux
Mesa 1.7.12,
libdrm 2.4.83, LLVM 5.0.0
The corruption does look somewhat like that of this bug, but applied to terrain as well. https://bugs.freedesktop.org/show_bug.cgi?id=74784
**Attachment 134449**, "The back buffer of apitrace frame 1017, showing red lines along what looks like primitive edges.":
![ark-frame-1017-backbuf](/uploads/2e31b15733f12a0ed5475bdf80211745/ark-frame-1017-backbuf.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1282GPU fault detected (Tonga)2021-01-14T16:51:08ZBugzilla Migration UserGPU fault detected (Tonga)## Submitted by fay..@..15.com
Assigned to **Default DRI bug account**
**[Link to original bug (#102934)](https://bugs.freedesktop.org/show_bug.cgi?id=102934)**
## Description
Created attachment 134418
dmesg containing errors (see...## Submitted by fay..@..15.com
Assigned to **Default DRI bug account**
**[Link to original bug (#102934)](https://bugs.freedesktop.org/show_bug.cgi?id=102934)**
## Description
Created attachment 134418
dmesg containing errors (see end of file)
I was playing visual novel Tsukihime with wine. I tried to switch to windowed mode from fullscreen and my monitor went black, and after that I couldn't recover picture using xrandr or arandr, or xfce's monitor utility. Only restart helped. There are errors in log attached.
Linux 4.12.13, AMD Radeon R9 200 Series (AMD TONGA / DRM 3.15.0 / 4.12.13-1-ARCH, LLVM 5.0.0) OpenGL version: 4.5 Mesa 17.2.0
**Attachment 134418**, "dmesg containing errors (see end of file)":
[err.txt](/uploads/932ce4594bb357787e055f09d462054b/err.txt)
Version: 17.2