dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 101769] 2X performance regression on Mesa 17.1 vs 17.0
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101769 Bug ID: 101769 Summary: 2X performance regression on Mesa 17.1 vs 17.0 Product: Mesa Version: 17.1 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: david(a)lunarg.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 132646 --> https://bugs.freedesktop.org/attachment.cgi?id=132646&action=edit hack to apitrace for duplicating problem We have an internal OpenGL benchmarking tool that measures the performance of certain frames in apitrace files. We have been using this tool to measure the performance of various releases of Mesa. We recently found a large regression in Mesa performance of Half Life Episode 2, as measured by our benchmarking tool. We measured the following frame rates when running the benchmark with Mesa built from the listed source tags: tag mesa-17.0.0 358.6 fps tag mesa-17.1.3 151.1 fps This is a reduction in performance of more than 2X. Since the tool we use to measure performance is an internal tool and we cannot distribute it, I hacked apitrace to behave similar to our tool so that apitrace can be used to measure the performance of the problem frame. The frame rates I measured with this hacked apitrace benchmark are: tag mesa-17.0.0 417.7 fps commit 071d80b 393.9 fps commit f81ede4 324.6 fps tag mesa-17.1.3 196.0 fps The hacked apitrace shows about the same performance drop between mesa-17.0.0 and mesa-17.1.3 as our original benchmark. I also include the results for commits 071d80b and f81ede4 because commit f81ede4 seemed to show the single largest performance drop of all commits between mesa-17.0.0 and mesa-17.1.3. The configuration of the system I have been using to measure Mesa performance is: CPU: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz RAM: 16Gb GPU: AMD RX480 Attached is the patch I applied to apitrace to create my hacked apitrace that attempts to duplicate the original benchmark. After building apitrace with the above patch, I used the following command to measure performance: vblank_mode=0 glretrace -b hl2_linux.trace I can make the hl2_linux.trace trace file available on request. We cannot widely distribute it because it contains Valve IP (i.e. game images). Please send a request directly to david(a)lunarg.com. Note that we have observed similar performance drops for other games, but I have concentrated on isolating and reporting on one frame in one game for now. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 101584] clover: ethminer -G --benchmark: ring buffer overflow, GPU faults
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101584 Bug ID: 101584 Summary: clover: ethminer -G --benchmark: ring buffer overflow, GPU faults Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: haagch(a)frickel.club QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 132229 --> https://bugs.freedesktop.org/attachment.cgi?id=132229&action=edit dmesg Tested with my RX 480 on mesa git and Linux 4.11 and 4.12-rc. To reproduce, get https://github.com/ethereum-mining/ethminer in libethash-cl/ethash_cl_miner_kernel.cl add #pragma OPENCL EXTENSION cl_clang_storage_class_specifiers : enable then cmake . and make and in ethminer/ run ./ethminer -G --benchmark it outputs some progress and at 97% something goes wrong and I get GPU faults and/or GPU hangs. Interestingly with the closed source OpenCL runtime from amdgpu-pro it fails at 97% too. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 101325] UE4Editor crash after pressing "play" with radeon southern island card (7850 HD)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101325 Bug ID: 101325 Summary: UE4Editor crash after pressing "play" with radeon southern island card (7850 HD) 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: dodgyville+freedesktop(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131758 --> https://bugs.freedesktop.org/attachment.cgi?id=131758&action=edit ~/ddebug_dumps/ file with environment variables R600_DEBUG=check_vm GALLIUM_DDEBUG="pipelined 10000" Hi, thanks for your great work on bringing hardware accelerated graphics to linux. I have a recurring problem with one 3D program (UE4editor) crashing my computer during a particular operation (pressing "play" on any project including blank). I believe the problem is at the mesa layer. Brief details: Radeon 7850HD It crashes using radeon and amdgpu (on ubuntu 17.04, linux 4.11, padoka ppa). It does not crash using the fglrx driver (on ubuntu 14.04). The entire machine hangs and requires a reset. Following a suggestion from Michael I set the following environment variables for running ue4editor: R600_DEBUG=check_vm GALLIUM_DDEBUG="pipelined 10000" Now the program dumps without taking out the whole system. It created a file in ~/ddebug_dumps/ with more information about the GPU hang (attached). I have also attached the two dmesg logs for two separate trials involving the radeon and amdgpu modules. I blacklisted them both in grub2 and rebooted. I first manually loaded amdgpu and then after triggering the crash in ue4editor, rebooted and tried again with the manually loaded radeon module. The radeon one seems to give more information and the screen flashed a few times before freezing. When running amdgpu the x session just hangs and does nothing. I made sure I was running the latest (git 17-06-05) padoka builds. I was able to ssh into the machine for a while after the x session had completely frozen (including frozen mouse) until it also disconnected after a few minutes. This is the part of dmesg running radeon where it appears to go off the rails: radeon 0000:07:00.0: ring 4 stalled for more than 10024msec [ +0.000004] radeon 0000:07:00.0: GPU lockup (current fence id 0x0000000000000fd0 last fence id 0x0000000000000fd2 on ring 4) [ +0.485614] radeon 0000:07:00.0: Saved 724 dwords of commands on ring 0. [ +0.000126] radeon 0000:07:00.0: GPU softreset: 0x0000004D [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS = 0xA0403028 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE0 = 0x08000006 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE1 = 0x08000006 [ +0.000001] radeon 0000:07:00.0: SRBM_STATUS = 0x200000C0 [ +0.000118] radeon 0000:07:00.0: SRBM_STATUS2 = 0x00000000 [ +0.000002] radeon 0000:07:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008678_CP_STALLED_STAT2 = 0x00018000 [ +0.000001] radeon 0000:07:00.0: R_00867C_CP_BUSY_STAT = 0x00400006 [ +0.000001] radeon 0000:07:00.0: R_008680_CP_STAT = 0x84038647 [ +0.000001] radeon 0000:07:00.0: R_00D034_DMA_STATUS_REG = 0x44C83106 [ +0.000001] radeon 0000:07:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ +0.000002] radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ +0.000001] radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [ +0.465637] radeon 0000:07:00.0: GRBM_SOFT_RESET=0x0000DDFF [ +0.000052] radeon 0000:07:00.0: SRBM_SOFT_RESET=0x00100100 [ +0.001146] radeon 0000:07:00.0: GRBM_STATUS = 0x00003028 [ +0.000002] radeon 0000:07:00.0: GRBM_STATUS_SE0 = 0x00000006 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE1 = 0x00000006 [ +0.000000] radeon 0000:07:00.0: SRBM_STATUS = 0x200000C0 [ +0.000111] radeon 0000:07:00.0: SRBM_STATUS2 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008680_CP_STAT = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ +0.000001] radeon 0000:07:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ +0.000247] radeon 0000:07:00.0: GPU reset succeeded, trying to resume [ +0.025448] [drm] probing gen 2 caps for device 8086:151 = 261a103/e [ +0.000003] [drm] PCIE gen 3 link speeds already enabled [ +0.002586] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000). [ +0.000120] radeon 0000:07:00.0: WB enabled [ +0.000002] radeon 0000:07:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff94260bdd8c00 [ +0.000001] radeon 0000:07:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff94260bdd8c04 [ +0.000000] radeon 0000:07:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff94260bdd8c08 [ +0.000001] radeon 0000:07:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff94260bdd8c0c [ +0.000001] radeon 0000:07:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff94260bdd8c10 [ +0.000314] radeon 0000:07:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffaa3d89635a18 [ +0.010136] radeon 0000:07:00.0: failed VCE resume (-22). [ +0.159454] [drm] ring test on 0 succeeded in 4 usecs [ +0.000004] [drm] ring test on 1 succeeded in 1 usecs [ +0.000003] [drm] ring test on 2 succeeded in 1 usecs [ +0.000009] [drm] ring test on 3 succeeded in 6 usecs [ +0.000007] [drm] ring test on 4 succeeded in 5 usecs [ +0.175707] [drm] ring test on 5 succeeded in 2 usecs [ +0.000004] [drm] UVD initialized successfully. [ +1.041140] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed out. [ +0.000018] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110). [ +0.474934] radeon 0000:07:00.0: GPU softreset: 0x00000048 [ +0.000002] radeon 0000:07:00.0: GRBM_STATUS = 0xA0003028 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE0 = 0x00000006 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE1 = 0x00000006 [ +0.000001] radeon 0000:07:00.0: SRBM_STATUS = 0x200000C0 [ +0.000118] radeon 0000:07:00.0: SRBM_STATUS2 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 [ +0.000001] radeon 0000:07:00.0: R_00867C_CP_BUSY_STAT = 0x00400002 [ +0.000002] radeon 0000:07:00.0: R_008680_CP_STAT = 0x84010243 [ +0.000001] radeon 0000:07:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ +0.000001] radeon 0000:07:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ +0.000002] radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ +0.000001] radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [ +0.465304] radeon 0000:07:00.0: GRBM_SOFT_RESET=0x0000DDFF [ +0.000056] radeon 0000:07:00.0: SRBM_SOFT_RESET=0x00000100 [ +0.001147] radeon 0000:07:00.0: GRBM_STATUS = 0x00003028 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE0 = 0x00000006 [ +0.000001] radeon 0000:07:00.0: GRBM_STATUS_SE1 = 0x00000006 [ +0.000001] radeon 0000:07:00.0: SRBM_STATUS = 0x200000C0 [ +0.000110] radeon 0000:07:00.0: SRBM_STATUS2 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_008680_CP_STAT = 0x00000000 [ +0.000001] radeon 0000:07:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ +0.000001] radeon 0000:07:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ +0.000238] radeon 0000:07:00.0: GPU reset succeeded, trying to resume Eventually it starts to do this: [ +1.153721] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out. [ +0.000018] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110). [ +0.000008] radeon 0000:07:00.0: scheduling IB failed (-12). [ +0.000011] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12). [ +0.000018] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12). [ +0.000010] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 6 (-12). [ +0.000002] radeon 0000:07:00.0: scheduling IB failed (-12). [ +0.000010] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12). [ +0.000009] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12). [ +0.000009] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 7 (-12). [ +0.001058] radeon 0000:07:00.0: GPU fault detected: 147 0x00044802 [ +0.000003] radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000FF000 [ +0.000001] radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04048002 [ +0.000001] VM fault (0x02, vmid 2) at page 1044480, read from TC (72) [ +10.114896] radeon 0000:07:00.0: ring 0 stalled for more than 10116msec [ +0.000004] radeon 0000:07:00.0: GPU lockup (current fence id 0x0000000000001506 last fence id 0x000000000000151a on ring 0) [ +0.000022] radeon 0000:07:00.0: ring 4 stalled for more than 10112msec [ +0.000003] radeon 0000:07:00.0: GPU lockup (current fence id 0x0000000000000fd3 last fence id 0x0000000000000fd7 on ring 4) [ +0.000029] radeon 0000:07:00.0: ring 3 stalled for more than 10116msec [ +0.000002] radeon 0000:07:00.0: GPU lockup (current fence id 0x00000000000018b7 last fence id 0x000000000000190c on ring 3) [ +0.507937] radeon 0000:07:00.0: ring 3 stalled for more than 10624msec [ +0.000001] radeon 0000:07:00.0: ring 0 stalled for more than 10624msec Then the log repeats a few hundred times the non-utf-8 character "\00" before it cuts off. This is the part of dmesg running amdgpu where it appears to go off the rails: [Jun 6 11:16] INFO: task RenderThread 3:6190 blocked for more than 120 seconds. [ +0.000006] Tainted: G OE 4.11.0-mytest #2 [ +0.000002] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0.000002] RenderThread 3 D 0 6190 1612 0x00000000 [ +0.000003] Call Trace: [ +0.000007] __schedule+0x3c6/0x8c0 [ +0.000004] schedule+0x36/0x80 [ +0.000043] amd_sched_entity_push_job+0xc4/0x110 [amdgpu] [ +0.000003] ? wake_atomic_t_function+0x60/0x60 [ +0.000031] amdgpu_job_submit+0x72/0x90 [amdgpu] [ +0.000027] amdgpu_vm_bo_split_mapping+0x51f/0x7c0 [amdgpu] [ +0.000024] ? amdgpu_vm_do_copy_ptes+0x90/0x90 [amdgpu] [ +0.000024] amdgpu_vm_clear_freed+0x70/0xb0 [amdgpu] [ +0.000024] amdgpu_gem_va_ioctl+0x39a/0x3f0 [amdgpu] [ +0.000014] drm_ioctl+0x218/0x4b0 [drm] [ +0.000010] ? drm_ioctl+0x218/0x4b0 [drm] [ +0.000023] ? amdgpu_gem_metadata_ioctl+0x1d0/0x1d0 [amdgpu] [ +0.000003] ? kmem_cache_free+0x1b6/0x1e0 [ +0.000020] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] [ +0.000003] do_vfs_ioctl+0xa3/0x600 [ +0.000002] ? ____fput+0xe/0x10 [ +0.000003] ? task_work_run+0x85/0xa0 [ +0.000002] SyS_ioctl+0x79/0x90 [ +0.000002] entry_SYSCALL_64_fastpath+0x1e/0xad [ +0.000002] RIP: 0033:0x7fb15e3cb987 [ +0.000001] RSP: 002b:00007faefab6a778 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ +0.000002] RAX: ffffffffffffffda RBX: 00007faf340060e0 RCX: 00007fb15e3cb987 [ +0.000001] RDX: 00007faefab6a7c0 RSI: 00000000c0286448 RDI: 0000000000000009 [ +0.000001] RBP: 00007faefab6a810 R08: 000000011c430000 R09: 000000000000000e [ +0.000001] R10: 0000000000000002 R11: 0000000000000246 R12: 0000000040086409 [ +0.000001] R13: 0000000000000009 R14: 00007faf34ef5700 R15: 00007faf34d61780 [Jun 6 11:17] wlp4s0: disconnect from AP 80:2a:a8:11:23:5e for new auth to 80:2a:a8:11:24:29 [ +0.011326] wlp4s0: authenticate with 80:2a:a8:11:24:29 [ +0.020720] wlp4s0: send auth to 80:2a:a8:11:24:29 (try 1/3) [ +0.002594] wlp4s0: authenticated [ +0.002803] wlp4s0: associate with 80:2a:a8:11:24:29 (try 1/3) [ +0.005088] wlp4s0: RX AssocResp from 80:2a:a8:11:24:29 (capab=0x431 status=0 aid=2) [ +0.000223] wlp4s0: associated End of xorg.log.0 (for an earlier run) [ 12.056] (II) systemd-logind: got pause for 13:79 [ 32.415] (II) config/udev: removing GPU device /sys/devices/pci0000:00/0000:00:01.0/0000:07:00.0/drm/card0 /dev/dri/card0 [ 32.415] (II) config/udev: Adding drm device (/dev/dri/card0) [ 32.415] (II) xfree86: Adding drm device (/dev/dri/card0) [ 35.984] (II) systemd-logind: got resume for 13:81 [ 35.984] (EE) FBDEV(0): FBIOPUT_VSCREENINFO: No such device [ 35.984] (EE) Fatal server error: [ 35.984] (EE) EnterVT failed for screen 0 [ 35.984] (EE) [ 35.984] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 35.984] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 35.984] (EE) [ 35.984] (EE) FBDEV(0): FBIOPUT_VSCREENINFO: No such device [ 36.074] (EE) Server terminated with error (1). Closing log file. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 101229] Global screen tearing (scrolling, Hz miss-match?)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101229 Bug ID: 101229 Summary: Global screen tearing (scrolling, Hz miss-match?) Product: Mesa Version: 17.0 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: Paul.Hancock.17041993(a)live.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131571 --> https://bugs.freedesktop.org/attachment.cgi?id=131571&action=edit glxinfo System exhibits uncontrolled screen-tearing that can be seen when moving windows, watching videos or playing games, or any graphical movement in general. The tearing gradually shifts up or down the screen, suggesting its a cycle frequency miss-match (or floating-point error). Has affected mesa 12 and kernel 4.8 onwards. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 101185] System hang during piglit tests
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=101185 Bug ID: 101185 Summary: System hang during piglit tests 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: keppi5(a)gmx.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 131505 --> https://bugs.freedesktop.org/attachment.cgi?id=131505&action=edit crash logs and piglit result json I was running "piglit run tests/quick results/quick" yesterday and system suddenly stopped responding at test 36216/39353. I was forced to do 5 second power switch shut down. Today I ran the test again and it didn't hang the system but stopped progressing at 38239/39353 where I did Ctrl-C. Attached is backtrace of crashes. $ inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Tonga PRO [Radeon R9 285/380] Display Server: X.Org 1.19.3 driver: amdgpu Resolution: 1920x1080(a)60.00hz, 1920x1080(a)60.00hz GLX Renderer: Gallium 0.4 on AMD TONGA (DRM 3.15.0 / 4.12.0-rc1-g2ea659a9ef48, LLVM 5.0.0) GLX Version: 3.0 Mesa 17.2.0-devel (git-1586768e74) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 100784] Fullscreen fade transitions in starsector run at a few frames per second
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100784 Bug ID: 100784 Summary: Fullscreen fade transitions in starsector run at a few frames per second Product: Mesa Version: 17.0 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: jon(a)moozaad.co.uk QA Contact: dri-devel(a)lists.freedesktop.org The game generally runs at the 60fps cap with this exception. Game forum bug link: http://fractalsoftworks.com/forum/index.php?topic=11972.0 http://i.imgur.com/5zbBSCc.png (see the double prongs on the draw calls, the buffer wait is just an alt-tab) I'm running Opensuse Tumbleweed (mesa 17.0.3/kernel 4.10.10) on a Fury X. Reproduction: Launch star sector (any resolution, windowed or fullscreen) Get into the game (skip tutorials etc) Initiated a UI transition (easiest is press tab for map, left click a planet to show planet info) I'm working on getting an API trace. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 100638] Shadow of mordor crash Mesa: User error: GL_INVALID_VALUE in glFlushMappedBufferRange(offset 2097060 + length 480 > mapped length 2097152)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100638 Bug ID: 100638 Summary: Shadow of mordor crash Mesa: User error: GL_INVALID_VALUE in glFlushMappedBufferRange(offset 2097060 + length 480 > mapped length 2097152) Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: edisonalvarez(a)arnet.com.ar QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130770 --> https://bugs.freedesktop.org/attachment.cgi?id=130770&action=edit dmesg It crashes randomly if I reset the graphics settings to default it doesn't happen again for some time, then it crashes again and I have to reset the settings because it won't start. I using DAL/DC kernel staging from git 4.9.20, but it happens with other kernels. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 100400] Game Valhalla Hills crash on startup
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100400 Bug ID: 100400 Summary: Game Valhalla Hills crash on startup Product: Mesa Version: 17.0 Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: beham.christopher(a)gmx.at QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130460 --> https://bugs.freedesktop.org/attachment.cgi?id=130460&action=edit Output of the game execution logged with script The Game Valhalla Hills crashes for me on Mesa 17.0.2 on Archlinux. I tried the mesa packages from the standard archlinux extra repo. To get a little bit more information I added the line '--enable-debug \' to ./configure in the mesa_archlinux_package_source_files and created the packages and installed the packages mesa and mesa-vdpau, except from builded with enabled debug these packages are the same as from the standard archlinux extra repo. The attached file run is the output of executing: ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose ./ValhallaHills-Linux-Shipping The attached file gdb is the output of executing: ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose gdb ./ValhallaHills-Linux-Shipping I also tried to play with MESA_GL_VERSION_OVERRIDE (the game seems to need at least 3.2) and MESA_GLSL_VERSION_OVERRIDE (the game seems to need at least 150) but with no effects on the error outputs. The game works very well when using the amdgpu-pro driver version 16.60.379184 and turning off vsync in the game options. But I want to keep Mesa because of the need to downgrade packages for amdgpu-pro and bad performance on Grid Autosport. The game also works with an old nvidia GeForce GT240 in my old PC in my cellar with both nvidia version 340 and mesa nouveau driver, with colour and blinking light issues but quite playable. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100306 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |MOVED --- Comment #44 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1262. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 100239] Incorrect rendering in CS:GO
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100239 Bug ID: 100239 Summary: Incorrect rendering in CS:GO Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: network723(a)rkmail.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130271 --> https://bugs.freedesktop.org/attachment.cgi?id=130271&action=edit Broken AUG scope In windows, when you're aiming with AUG the screen around the scope is blurred. On Mesa we have strange black pattern. The pattern changes on each cs:go restart. I can reproduce it on Mesa 17.1-git + llvm 5.0 + RX480 and on stock Ubuntu 16.04.2 (Mesa 13.0, I believe) + R7 240 Note: green rectangles are not the bug, it's me hiding my steam name. -- You are receiving this mail because: You are the assignee for the bug.

1 29

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019