dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 108261] [amdgpu][GL_ARB_bindless_texture][opengl 4] GPU hang on AMD Raven
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=108261 Bug ID: 108261 Summary: [amdgpu][GL_ARB_bindless_texture][opengl 4] GPU hang on AMD Raven 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: RobusGrobus95(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org GPU hang appears when trying to render scene to FBO (framebuffer object) with attached texture with resident handle, but if all the handles of attached texture are not reesident (or if there is no handles), hang disappears. For example this pseudocode causes GPU hang: GLuint renderbufId; glCreateRenderbuffers(1, &renderbufId); glNamedRenderbufferStorage(renderbufId, GL_DEPTH_COMPONENT, width(), height()); GLuint texId; glCreateTextures(GL_TEXTURE_2D, 1, &texId); glTextureStorage2D(texId, 1, GL_RGBA8, width(), height()); GLuint64 handle = glGetTextureHandleARB(texId); glMakeTextureHandleResidentARB(handle); glBindFramebuffer(GL_FRAMEBUFFER, fboID); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0, texId, 0); glFramebufferRenderbuffer(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_RENDERBUFFER, rboId); //render some triangles glBindFramebuffer(GL_FRAMEBUFFER, 0); //render main scene glSwapBuffers(); And this not: GLuint renderbufId; glCreateRenderbuffers(1, &renderbufId); glNamedRenderbufferStorage(renderbufId, GL_DEPTH_COMPONENT, width(), height()); GLuint texId; glCreateTextures(GL_TEXTURE_2D, 1, &texId); glTextureStorage2D(texId, 1, GL_RGBA8, width(), height()); GLuint64 handle = glGetTextureHandleARB(texId); std::cout << handle << std::endl; //prevent optimizing out glBindFramebuffer(GL_FRAMEBUFFER, fboID); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0, texId, 0); glFramebufferRenderbuffer(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_RENDERBUFFER, rboId); //render some triangles glBindFramebuffer(GL_FRAMEBUFFER, 0); //render main scene glSwapBuffers(); I can try to write full cpp sample for exposing the hang, if it's needed. There is already open source graphic engine (my "pet" project) affected by the hang, but code is quite complex (https://gitlab.com/KawaiiGraphics/Kawaii3D https://gitlab.com/KawaiiGraphics/Misaka3D ; workaround added in commit b53d98dacff2b0392c2143c8901289e93ddd8623, so only previous versions are affected). My hardware: APU: AMD Ryzen 5 2400G (with integrated GPU Radeon Vega 11 Graphics) System board: MSI AM4 X470 Gaming Pro RAM: Goodram Iridium 16Gb (8+8 Gb dual-channel 2800MHz) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 108194] Civilization VI - Animated leader characters small black squares artifacts
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=108194 Bug ID: 108194 Summary: Civilization VI - Animated leader characters small black squares artifacts Product: Mesa Version: 18.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: freedesktop(a)psydk.org QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 141871 --> https://bugs.freedesktop.org/attachment.cgi?id=141871&action=edit A leader character covered with multiple small black squares See the attached picture. I'm not sure if the problem is related to bug 108111 so I prefer opening a new one. If both are related to a LLVM regression it's possible we'll be able to close both. Computer info: OpenGL renderer string: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.23.0, 4.15.0-34-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 - padoka PPA -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 108036] VA-API implementation reports support for unsupported endpoints
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=108036 Bug ID: 108036 Summary: VA-API implementation reports support for unsupported endpoints Product: Mesa Version: 18.2 Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: notkurufu(a)cock.li QA Contact: dri-devel(a)lists.freedesktop.org Videos encoded via VA-API on amd hardware using the h264 High profile end up corrupt. This appears to be a known flaw and unsupported by mesa drivers. My reference for this is here: https://bugs.freedesktop.org/show_bug.cgi?id=104920#c8 Notably the mesa team claims that the issue is with applications using an unsupported profile and that applications should query VA-API for supported features. However it can be see with `vainfo` on AMD hardware that h264 High profile support IS advertised by the drivers. So the error is not in the applications which correctly query the information. But in the drivers returning false information. An example of vainfo output on AMD hardware advertising h264 High profile support. I also have a source video and resultant reencoding at high profile which is corrupt which is the same issue in the earlier bug where it was claimed it was not supported. $ vainfo --display drm libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Mesa Gallium driver 18.1.6 for AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.26.0, 4.18.5-200.fc28.x86_64, LLVM 6.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 107912] Please add support for PIPE_CAP_TGSI_MUL_ZERO_WINS to radeonsi
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107912 Bug ID: 107912 Summary: Please add support for PIPE_CAP_TGSI_MUL_ZERO_WINS to radeonsi Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: enhancement Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: davyaxel0(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org PIPE_CAP_TGSI_MUL_ZERO_WINS is a cap currently supported by nv50, nvc0 and r600, which means that TGSI_PROPERTY_MUL_ZERO_WINS is supported. When enabled, the affected shaders have the behaviour 0*anything = 0 (including inside a mad). It is used by gallium nine when available. All GCN cards support special legacy instructions to handle the behaviour. Since opengl compat used to be a thing "we will never support because lack of time" and is now implemented, I thought maybe this MUL_ZERO_WINS may get added to the new radeonsi TODO list. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 107864] Specific Shadertoy demo renders garbage in empty parts of target surface
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107864 Bug ID: 107864 Summary: Specific Shadertoy demo renders garbage in empty parts of target surface 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: kode54(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org The following Shadertoy demo: https://www.shadertoy.com/view/Xt3cWS renders garbage in the top and bottom strips of the target surface, which appears to be uninitialized VRAM being copied to the display surface. It does not appear to matter which WebGL capable browser I use to run the demo, they all replicate the issue on my RX480. I cannot get apitrace to run on Firefox without that particular page crashing on load, and I cannot get RenderDoc to attach to the tab's process and actually capture anything. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 107694] [wine] RAGE: texture problems
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107694 Bug ID: 107694 Summary: [wine] RAGE: texture problems Product: Mesa Version: 18.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 141292 --> https://bugs.freedesktop.org/attachment.cgi?id=141292&action=edit screenshot of bug in RAGE The game RAGE starts and runs, but have some quite severe texture problems. See attached screenshot. The problem is especially bad when loading new areas. Settings these options in default.cfg minimizes but doesn't get rid of the bug fully: jobs_numThreads 1 vt_maxPPF 128 as suggested in https://store.steampowered.com/news/6464/ This bug looks quite a lot like one that plagued the Windows drivers (ATI Performance) back when the game was released: https://www.youtube.com/watch?v=z-yl6pDFgtw I have seen video of RAGE rendering fine with radeonsi (https://www.youtube.com/watch?v=OgqgNrN16KM) so I tried jumping back quite a few Mesa releases* to see if there was a regression somewhere, but AFAICT it is still there as far back as 11.2.2. I'm guessing the bug happened as a change from radeon to amdgpu on the kernel side? * Using a hack for Wine to skip the check for a compat profile. System environment: -- system architecture: 64-bit -- Linux distribution: Debian unstable -- GPU: TONGA -- Model: Asus Strix R9 285 2GB -- Display connector: DVI -- xf86-video-amdgpu: 18.0.1 -- xserver: 1.20.1 -- mesa: 18.2.0~rc4 -- drm: 2.4.93 -- kernel: 4.17 -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 107692] [wine] Shadows missing in Mafia II
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107692 Bug ID: 107692 Summary: [wine] Shadows missing in Mafia II Product: Mesa Version: 18.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 141288 --> https://bugs.freedesktop.org/attachment.cgi?id=141288&action=edit radeonsi screenshot no shadows Shadows are missing in the game Mafia II, running in Wine 3.14. Attached screenshots are from a run with radeonsi (no shadows) and a comparison shot from a video clip (with shadows). Shadows are described as working with Wine 3.11 and above, but only for the Nvidia driver: https://bugs.winehq.org/show_bug.cgi?id=28251 Apitrace (236 MB): https://www.dropbox.com/s/wo8jmhy7wyykk9b/mafia2.trace.xz?dl=0 Replaying the trace shows some shader compiler issues: 19736 @0 glXCreateWindow(dpy = 0x7d46c620, config = 0x7b9b85c0, win = 48234528, attribList = {}) = 48234529 19736: warning: unsupported glXCreateWindow call 19747: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 16 Code Size: 72 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 19747: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 8 Code Size: 136 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 19747: message: shader compiler issue 2: LLVM diagnostic (remark): <unknown>:0:0: 4 instructions in function 120455: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 20 Code Size: 36 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120456: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 12 Code Size: 272 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120514: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 8 Code Size: 84 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 16 Code Size: 64 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 20 Code Size: 132 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 8 Code Size: 72 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 16 Code Size: 72 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 8 Code Size: 136 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 16 Code Size: 40 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 1: Shader Stats: SGPRS: 96 VGPRS: 4 Code Size: 108 LDS: 0 Scratch: 0 Max Waves: 8 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 120533: message: shader compiler issue 2: LLVM diagnostic (remark): <unknown>:0:0: 3 instructions in function 120533: message: shader compiler issue 2: LLVM diagnostic (remark): <unknown>:0:0: 2 instructions in function 141097 @0 glXDestroyWindow(dpy = 0x7d46c620, window = 48234529) 141097: warning: unsupported glXDestroyWindow call 141099 @0 glXCreateWindow(dpy = 0x7d46c620, config = 0x7b9b85c0, win = 48234562, attribList = {}) = 48234563 141099: warning: unsupported glXCreateWindow call -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 107684] [amdgpu] GPU Hangs running game Fall of Light
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107684 Bug ID: 107684 Summary: [amdgpu] GPU Hangs running game Fall of Light Product: Mesa Version: 18.1 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: l.gambetta(a)alice.it QA Contact: dri-devel(a)lists.freedesktop.org I'm trying to run the game "Fall of Light" from Steam (https://store.steampowered.com/app/633950/Fall_of_Light/) using Wine, but it causes a GPU hang, leading to a system crash. I'm using wine-staging-3.14 with DXVK 0.70. The game runs perfectly and plays the intro video, but then when I start a new game, the game crashes on the loading screen. I also tried to run the game using Steam Play with Proton 3.7 (a modified version of wine + dxvk 0.65) and the GPU hang exactly in the same point. This is the log from 2 subsequent tries with different Wine versions (Proton and wine-staging): ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x0b084402 ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0050D961 ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06044002 ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32775) at page 5298529, read from 'TC5' (0x54433500) (68) ago 25 11:27:50 luca-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=57598, last emitted seq=57600 ago 25 11:27:50 luca-pc kernel: [drm] IP block:gfx_v8_0 is hung! ago 25 11:27:50 luca-pc kernel: [drm] GPU recovery disabled. ago 25 11:31:10 luca-pc kernel: INFO: task kworker/u8:0:2750 blocked for more than 120 seconds. ago 25 11:31:10 luca-pc kernel: Not tainted 4.17.17-1-MANJARO #1 ago 25 11:31:10 luca-pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ago 25 11:31:10 luca-pc kernel: kworker/u8:0 D 0 2750 2 0x80000000 ago 25 11:31:10 luca-pc kernel: Workqueue: events_unbound commit_work [drm_kms_helper] ago 25 11:31:10 luca-pc kernel: Call Trace: ago 25 11:31:10 luca-pc kernel: ? __schedule+0x282/0x890 ago 25 11:31:10 luca-pc kernel: ? __switch_to_asm+0x34/0x70 ago 25 11:31:10 luca-pc kernel: ? __switch_to_asm+0x40/0x70 ago 25 11:31:10 luca-pc kernel: schedule+0x32/0x90 ago 25 11:31:10 luca-pc kernel: schedule_timeout+0x311/0x4a0 ago 25 11:31:10 luca-pc kernel: ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu] ago 25 11:31:10 luca-pc kernel: ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0 [amdgpu] ago 25 11:31:10 luca-pc kernel: dma_fence_default_wait+0x1e8/0x270 ago 25 11:31:10 luca-pc kernel: ? dma_fence_default_wait+0x270/0x270 ago 25 11:31:10 luca-pc kernel: dma_fence_wait_timeout+0x39/0x110 ago 25 11:31:10 luca-pc kernel: reservation_object_wait_timeout_rcu+0x1f2/0x370 ago 25 11:31:10 luca-pc kernel: ? preempt_count_add+0x68/0xa0 ago 25 11:31:10 luca-pc kernel: amdgpu_dm_do_flip+0x10c/0x350 [amdgpu] ago 25 11:31:10 luca-pc kernel: ? freed_request+0x38/0x60 ago 25 11:31:10 luca-pc kernel: amdgpu_dm_atomic_commit_tail+0x711/0xd80 [amdgpu] ago 25 11:31:10 luca-pc kernel: ? _raw_spin_unlock_irq+0x1d/0x30 ago 25 11:31:10 luca-pc kernel: commit_tail+0x3d/0x70 [drm_kms_helper] ago 25 11:31:10 luca-pc kernel: process_one_work+0x1d1/0x3b0 ago 25 11:31:10 luca-pc kernel: worker_thread+0x2b/0x3d0 ago 25 11:31:10 luca-pc kernel: ? process_one_work+0x3b0/0x3b0 ago 25 11:31:10 luca-pc kernel: kthread+0x112/0x130 ago 25 11:31:10 luca-pc kernel: ? kthread_flush_work_fn+0x10/0x10 ago 25 11:31:10 luca-pc kernel: ret_from_fork+0x22/0x40 -- Reboot -- ago 25 11:32:50 luca-pc kernel: Linux version 4.17.17-1-MANJARO (builduser@development) (gcc version 8.2.0 (GCC)) #1 SMP PREEMPT Sat Aug 18 14:38:10 UTC 2018 ago 25 11:32:50 luca-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.17-x86_64 root=UUID=c3345f8c-be04-4cb5-95cc-481223caaf4d rw quiet ago 25 11:27:01 luca-pc kscreen_backend_launcher[910]: kscreen.xcb.helper: Rotation: "Rotate_0" ago 25 11:27:01 luca-pc kscreen_backend_launcher[910]: kscreen.xcb.helper: Geometry: 0 0 1920 1080 ago 25 11:27:01 luca-pc plasmashell[925]: trying to show an empty dialog ago 25 11:27:02 luca-pc kscreen_backend_launcher[910]: kscreen.xrandr: Emitting configChanged() ago 25 11:27:02 luca-pc org_kde_powerdevil[972]: kscreen: Requesting missing EDID for outputs (89) ago 25 11:27:02 luca-pc kdeinit5[879]: kscreen: Requesting missing EDID for outputs (89) ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x0b084402 ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0050D961 ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x06044002 ago 25 11:27:40 luca-pc kernel: amdgpu 0000:01:00.0: VM fault (0x02, vmid 3, pasid 32775) at page 5298529, read from 'TC5' (0x54433500) (68) ago 25 11:27:50 luca-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=57598, last emitted seq=57600 ago 25 11:27:50 luca-pc kernel: [drm] IP block:gfx_v8_0 is hung! ago 25 11:27:50 luca-pc kernel: [drm] GPU recovery disabled. ago 25 11:31:10 luca-pc kernel: INFO: task kworker/u8:0:2750 blocked for more than 120 seconds. ago 25 11:31:10 luca-pc kernel: Not tainted 4.17.17-1-MANJARO #1 ago 25 11:31:10 luca-pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ago 25 11:31:10 luca-pc kernel: kworker/u8:0 D 0 2750 2 0x80000000 ago 25 11:31:10 luca-pc kernel: Workqueue: events_unbound commit_work [drm_kms_helper] ago 25 11:31:10 luca-pc kernel: Call Trace: ago 25 11:31:10 luca-pc kernel: ? __schedule+0x282/0x890 ago 25 11:31:10 luca-pc kernel: ? __switch_to_asm+0x34/0x70 ago 25 11:31:10 luca-pc kernel: ? __switch_to_asm+0x40/0x70 ago 25 11:31:10 luca-pc kernel: schedule+0x32/0x90 ago 25 11:31:10 luca-pc kernel: schedule_timeout+0x311/0x4a0 ago 25 11:31:10 luca-pc kernel: ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu] ago 25 11:31:10 luca-pc kernel: ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0 [amdgpu] ago 25 11:31:10 luca-pc kernel: dma_fence_default_wait+0x1e8/0x270 ago 25 11:31:10 luca-pc kernel: ? dma_fence_default_wait+0x270/0x270 ago 25 11:31:10 luca-pc kernel: dma_fence_wait_timeout+0x39/0x110 ago 25 11:31:10 luca-pc kernel: reservation_object_wait_timeout_rcu+0x1f2/0x370 ago 25 11:31:10 luca-pc kernel: ? preempt_count_add+0x68/0xa0 ago 25 11:31:10 luca-pc kernel: amdgpu_dm_do_flip+0x10c/0x350 [amdgpu] ago 25 11:31:10 luca-pc kernel: ? freed_request+0x38/0x60 ago 25 11:31:10 luca-pc kernel: amdgpu_dm_atomic_commit_tail+0x711/0xd80 [amdgpu] ago 25 11:31:10 luca-pc kernel: ? _raw_spin_unlock_irq+0x1d/0x30 ago 25 11:31:10 luca-pc kernel: commit_tail+0x3d/0x70 [drm_kms_helper] ago 25 11:31:10 luca-pc kernel: process_one_work+0x1d1/0x3b0 ago 25 11:31:10 luca-pc kernel: worker_thread+0x2b/0x3d0 ago 25 11:31:10 luca-pc kernel: ? process_one_work+0x3b0/0x3b0 ago 25 11:31:10 luca-pc kernel: kthread+0x112/0x130 ago 25 11:31:10 luca-pc kernel: ? kthread_flush_work_fn+0x10/0x10 ago 25 11:31:10 luca-pc kernel: ret_from_fork+0x22/0x40 -- Reboot -- My specs: $ inxi -F System: Host: luca-pc Kernel: 4.17.17-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.13.4 Distro: Manjaro Linux Machine: Type: Desktop Mobo: ASRock model: FM2A88X Extreme4+ serial: <root required> UEFI [Legacy]: American Megatrends v: P3.30 date: 05/13/2016 CPU: Topology: Quad Core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G bits: 64 type: MCP L2 cache: 2048 KiB Speed: 1924 MHz min/max: 1700/3700 MHz Core speeds (MHz): 1: 2774 2: 2812 3: 1696 4: 1696 Graphics: Card-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.1 driver: amdgpu,ati unloaded: modesetting resolution: 1920x1080~60Hz OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.25.0 4.17.17-1-MANJARO LLVM 6.0.1) v: 4.5 Mesa 18.1.6 Audio: Card-1: Advanced Micro Devices [AMD] FCH Azalia driver: snd_hda_intel Card-2: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 580] driver: snd_hda_intel Sound Server: ALSA v: k4.17.17-1-MANJARO Network: Card-1: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx IF: enp5s0 state: up speed: 100 Mbps duplex: half mac: d0:50:99:26:b3:1c Drives: Local Storage: total: 5.91 TiB used: 1.47 TiB (24.9%) ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB ID-2: /dev/sdb vendor: Seagate model: ST3000DM008-2DM166 size: 2.73 TiB ID-3: /dev/sdc vendor: Seagate model: ST3000DM008-2DM166 size: 2.73 TiB RAID: Device-1: md126 type: mdraid status: active raid: mirror report: 2/2 UU Components: online: sdc2~c0 sdb2~c2 Device-2: md127 type: mdraid status: active raid: mirror report: 2/2 UU Components: online: sdc1~c0 sdb1~c2 Partition: ID-1: / size: 143.19 GiB used: 10.07 GiB (7.0%) fs: ext4 dev: /dev/sda1 Sensors: System Temperatures: cpu: 25.8 C mobo: N/A gpu: amdgpu temp: 39 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 733 Info: Processes: 187 Uptime: 10m Memory: 15.67 GiB used: 1.11 GiB (7.1%) Shell: bash inxi: 3.0.20 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 107572] Unrecoverable GPU hang with IP block:gfx_v8_0 is hung
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107572 Bug ID: 107572 Summary: Unrecoverable GPU hang with IP block:gfx_v8_0 is hung 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: madcatx(a)atlas.cz Hello, I have been experiencing a worrying amount of these ever since I got my RX 570 a few months ago. I can reproduce the hang quite reliably by with some 3D workloads, for instance the Unigine Superposition run on High quality or Witcher 3 (through WINE) crash the GPU quite reliably within minutes. Once that happens I can always SSH into the machine and try to get at least some debugging information. Unfortunately, there does not seem to be much to go on. dmesg does not tell me more than this: [ 254.704581] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=103742, last emitted seq=103745 [ 254.704586] [drm] IP block:gfx_v8_0 is hung! [ 254.704629] [drm] GPU recovery disabled. Here are a few things I have tried so far: - Boot with amdgpu.dc=0 - Boot with amdgpu.vm_update_mode=3 - Force the GPU to max power state - Disable IOMMU (both by iommu=off and by disabling VT-d in BIOS) - Boot with amdgpu.gpu_recovery=1 (does not produce any additional info) I grabbed the umr tool to try to get the state of the GPU when in crashes but it does not seem to be able to read anything. Running: umr -R gfx[.] Leaves me with: [ERROR]: Could not open ring debugfs file# I check that entries in /sys/kernel/debug/amdgpu that look relevant are there, cat'ing them gives me "Operation not permitted". Yes, I am doing it as root. Once this happens the only way out is a hard reboot. I am running up-to-date Fedora 28, kernel 4.17.2, Mesa 18.0 series, LLVM 6.0.1. Is there anything else I can do? Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 24

[Bug 107509] corrupted Box in top Right corner in some games
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=107509 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #9 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/1322. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019