dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 97075] VCE encoding slow when GPU is not stressed (HD 7970M)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=97075 Bug ID: 97075 Summary: VCE encoding slow when GPU is not stressed (HD 7970M) Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: haagch(a)frickel.club This is on an intel + radeon laptop, so I need to run encoding with gstreamer with DRI_PRIME=1. Here is an example video: http://www.sample-videos.com/video/mp4/720/big_buck_bunny_720p_1mb.mp4 DRI_PRIME is doing a good job of waking up the GPU from runpm when needed for encoding via VAAPI and OMX, but for comparison I'll run glxgears both times. I'm encoding the mentioned example video with VAAPI with this exact command: $ time DRI_PRIME=1 LIBVA_DRIVER_NAME=radeonsi gst-launch-1.0 -e filesrc location=big_buck_bunny_720p_1mb.mp4 ! qtdemux ! h264parse ! avdec_h264 ! queue ! videoconvert ! queue ! video/x-raw,format=NV12 ! vaapih264enc ! h264parse ! matroskamux ! filesink location=output.mkv For low GPU stress I run the gst pipeline while glxgears with vsync is running: $ DRI_PRIME=1 glxgears Result: 0.75s user 0.33s system 2% cpu 52.779 total For higher GPU stress I run the gst pipeline while glxgears without vsync is running: $ DRI_PRIME=1 vblank_mode=0 glxgears Result: 0.99s user 0.28s system 43% cpu 2.928 total I also tried a very similar pipeline with OMX: $ time DRI_PRIME=1 gst-launch-1.0 -e filesrc location=big_buck_bunny_720p_1mb.mp4 ! qtdemux ! h264parse ! avdec_h264 ! queue ! videoconvert ! queue ! video/x-raw,format=NV12 ! omxh264enc ! h264parse ! matroskamux ! filesink location=output.mkv Low GPU stress: 0.96s user 0.24s system 19% cpu 6.298 total High GPU stress: 1.10s user 0.24s system 141% cpu 0.949 total Overall OMX encoding does a lot better, but it's still a large difference and still below "real time" for the 5 second video. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 96860] Aliasing when using vdpau with mpv
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=96860 Bug ID: 96860 Summary: Aliasing when using vdpau with mpv Product: Mesa Version: 11.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: dolohow(a)outlook.com QA Contact: dri-devel(a)lists.freedesktop.org When using hardware decoding with radeonsi along with mpv I can observe aliasing on rough edges. It was previously reported on mpv issue tracker https://github.com/mpv-player/mpv/issues/3317 but the main developer pointed out that the bug is in mesa. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 96508] Artefacts while playing video with vaapi or vdpau acceleration on amd apu (Radeon HD 8280E)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=96508 Bug ID: 96508 Summary: Artefacts while playing video with vaapi or vdpau acceleration on amd apu (Radeon HD 8280E) Product: Mesa Version: 11.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: jan.burgmeier(a)unicon-software.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 124502 --> https://bugs.freedesktop.org/attachment.cgi?id=124502&action=edit Video with artefacts While playing the attached video with mpv and vaapi or vdpau acceleration some artefacts are shown. The same artefacts are also shown when using gstreamer-0.10 with vaapi acceleration. Versions used: - Mesa: 11.2.2 and 12.0.0-rc4 - MPV: git commit 2b1656b1aced3d81b31c83e8c310a630ca5d5d1c - FFmpeg: 3.0.2 Hardware: - CPU: AMD GX-217GA SOC with Radeon(tm) HD Graphic - GPU: Radeon HD 8280E -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 95659] HD 7450, R9-270, GPU locked when testing glmark2
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=95659 Bug ID: 95659 Summary: HD 7450, R9-270, GPU locked when testing glmark2 Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: zduo006(a)163.com [ 427.367567] radeon 0000:01:00.0: ring 0 stalled for more than 10070msec [ 427.374151] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000ea28 last fence id 0x000000000000ea2d on ring 0) [ 427.500439] radeon 0000:01:00.0: Saved 151 dwords of commands on ring 0. [ 427.500464] radeon 0000:01:00.0: GPU softreset: 0x00000009 [ 427.500471] radeon 0000:01:00.0: GRBM_STATUS = 0xB2732828 [ 427.500476] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x1C000005 [ 427.500481] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 427.500486] radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 [ 427.500491] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 427.500495] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 427.500500] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x400C0000 [ 427.500505] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048004 [ 427.500509] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 [ 427.500513] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 427.513320] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 427.513378] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 427.514540] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 427.514544] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 427.514549] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 427.514554] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 427.514558] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 427.514563] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 427.514567] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 427.514571] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 427.514576] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 427.514580] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 427.514607] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 427.543125] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 427.612472] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000). [ 427.612666] radeon 0000:01:00.0: WB enabled [ 427.612673] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffffffc8dc366c00 [ 427.612678] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffffffc8dc366c0c [ 427.662677] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffff8018332118 [ 427.679867] [drm] ring test on 0 succeeded in 1 usecs [ 427.679884] [drm] ring test on 3 succeeded in 7 usecs [ 427.856598] [drm] ring test on 5 succeeded in 2 usecs [ 427.856613] [drm] UVD initialized successfully. [ 427.977870] [drm] ib test on ring 0 succeeded in 0 usecs [ 427.977919] [drm] ib test on ring 3 succeeded in 0 usecs [ 428.128994] [drm] ib test on ring 5 succeeded [ 792.996810] radeon 0000:01:00.0: ring 0 stalled for more than 10140msec [ 793.003403] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000184b0 last fence id 0x00000000000184b5 on ring 0) [ 793.140947] radeon 0000:01:00.0: Saved 151 dwords of commands on ring 0. [ 793.140974] radeon 0000:01:00.0: GPU softreset: 0x00000009 [ 793.140981] radeon 0000:01:00.0: GRBM_STATUS = 0xF7730828 [ 793.140986] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000001 [ 793.140992] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 793.140996] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 793.141001] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 793.141006] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 793.141010] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x400C0000 [ 793.141015] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048004 [ 793.141019] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 [ 793.141024] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 793.154522] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 793.154580] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 793.155741] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 793.155746] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 793.155751] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 793.155755] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 793.155759] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 793.155764] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 793.155768] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 793.155772] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 793.155777] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 793.155781] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 793.155808] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 793.184357] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 793.253690] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000). [ 793.253884] radeon 0000:01:00.0: WB enabled [ 793.253891] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffffffc8dc366c00 [ 793.253896] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffffffc8dc366c0c [ 793.303888] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffff8018332118 [ 793.321047] [drm] ring test on 0 succeeded in 2 usecs [ 793.321064] [drm] ring test on 3 succeeded in 7 usecs [ 793.497767] [drm] ring test on 5 succeeded in 2 usecs [ 793.497781] [drm] UVD initialized successfully. [ 793.619052] [drm] ib test on ring 0 succeeded in 0 usecs [ 793.619102] [drm] ib test on ring 3 succeeded in 0 usecs [ 793.770188] [drm] ib test on ring 5 succeeded when testing the following cases, GPU locked. First it stops responding for some seconds and screen goes black, then it return to normal. loop:vertex-step=5, fragment-steps=5, fragment-loop=false; loop:vertex-step=5, fragment-steps=5, fragment-uniform=false; loop:vertex-step=5, fragment-steps=5, fragment-uniform=ture; I've already tried several radeon boot flags, such as DPM on and off, radeon_lockup_timeout = 20000, without success. Upgrading the kernel version to 4.5.3 and 4.6.0 but it not fixed. The problem does not occur when i add a delay（such as 1ms using msleep） in the problem scene's draw function. I thought is the problem of Synchronization between the cpu and gpu using fence , can anyone have some idea? lspci:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] libdrm 2.4.67, xserver-xorg-video-ati 7.6.0, xorg-server 1.18.2, mesa 11.2.0 kernel 4.4 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 94471] Tonga UVD 4Kx4K = failed to allocate a buffer
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=94471 Bug ID: 94471 Summary: Tonga UVD 4Kx4K = failed to allocate a buffer 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: adf.lists(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I see >= tonga uvd height has recently been increased - https://cgit.freedesktop.org/mesa/mesa/commit/?id=353a4f844f9e845dad93de9c2… radeon/uvd: increase max height to 4096 for VI and newer With this issue 'mpv --hwdec=vdpau --vo=vdpau <stream>' fails for vdpau decode if the stream height is 4096. Vdpau decode of height upto 4096 is necessary usecase on amdgpu driver for VI and newer platforms. The fix is in driver specific implementation of "Decoder Query Capabilities" API to return 4096 for VI and newer platforms. With this fix vdpauinfo reports height support as 4096 and mpv for vdpau decode works fine for 4096 height streams. On agd5f drm-fixes-4.5 4096x4096 fails for me (also fails with --vo vdpau) andy [~]$ mpv --hwdec=vdpau /mnt/sdb1/ffmpeg-mpl-tests/x264-4096.mkv Playing: /mnt/sdb1/ffmpeg-mpl-tests/x264-4096.mkv (+) Video --vid=1 (*) (h264) amdgpu: Failed to allocate a buffer: amdgpu: size : 0 bytes amdgpu: alignment : 4096 bytes amdgpu: domains : 2 amdgpu: Failed to allocate a buffer: amdgpu: size : 0 bytes amdgpu: alignment : 4096 bytes amdgpu: domains : 2 EE radeon_uvd.c:1109 ruvd_create_decoder UVD - Can't allocated bitstream buffers. [vo/opengl/x11] Disabling screensaver failed (-1). Make sure the xdg-screensaver script is installed. Using software decoding. VO: [opengl] 4096x4096 => 7282x4096 yuv420p dmesg [ 8308.529176] [TTM] Illegal buffer object size [ 8308.529210] [drm:amdgpu_gem_object_create [amdgpu]] *ERROR* Failed to allocate GEM object (0, 2, 4096, -22) [ 8308.529326] [TTM] Illegal buffer object size [ 8308.529339] [drm:amdgpu_gem_object_create [amdgpu]] *ERROR* Failed to allocate GEM object (0, 2, 4096, -22) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 94410] [radeonsi] Unreal engine 4 Segmentation fault
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=94410 Bug ID: 94410 Summary: [radeonsi] Unreal engine 4 Segmentation fault 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: pontostroy(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Radeon Hd 7970 mesa\llvm git unreal editor git UE4Editor works fine on intel hd 2500, but on radeon i got bt full log http://pastebin.com/cX57pWcG Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff9afff700 (LWP 3209)] 0x00007ffff72e9e0f in je_arena_salloc (demote=false, ptr=<optimized out>) at include/jemalloc/internal/arena.h:1018 1018 include/jemalloc/internal/arena.h: No such file or directory. Missing separate debuginfos, use: zypper install Mesa-libglapi0-debuginfo-11.3~git20160305-1.1.x86_64 libFLAC8-debuginfo-1.3.1-219.6.x86_64 libX11-6-debuginfo-1.6.3-41.1.x86_64 libX11-xcb1-debuginfo-1.6.3-41.1.x86_64 libXau6-debuginfo-1.0.8-23.1.x86_64 libXcursor1-debuginfo-1.1.14-25.1.x86_64 libXdamage1-debuginfo-1.1.4-25.1.x86_64 libXext6-debuginfo-1.3.3-22.1.x86_64 libXfixes3-debuginfo-5.0.1-24.1.x86_64 libXi6-debuginfo-1.7.5-35.1.x86_64 libXinerama1-debuginfo-1.1.3-21.1.x86_64 libXrandr2-debuginfo-1.5.99-1.1.x86_64 libXrender1-debuginfo-0.9.9-22.1.x86_64 libXss1-debuginfo-1.2.2-20.1.x86_64 libXxf86vm1-debuginfo-1.1.4-23.1.x86_64 libdbus-1-3-debuginfo-1.8.16-5.2.x86_64 libdrm2-debuginfo-2.4.99~git20160303-1.1.x86_64 libdrm_amdgpu1-debuginfo-2.4.99~git20160303-1.1.x86_64 libdrm_intel1-debuginfo-2.4.99~git20160303-1.1.x86_64 libdrm_nouveau2-debuginfo-2.4.99~git20160303-1.1.x86_64 libdrm_radeon1-debuginfo-2.4.99~git20160303-1.1.x86_64 libelf1-debuginfo-0.158-9.5.x86_64 libexpat1-debuginfo-2.1.0-15.4.x86_64 libgcc_s1-debuginfo-5.2.1+r226025-4.2.x86_64 libgcrypt20-debuginfo-1.6.1-20.1.x86_64 libgpg-error0-debuginfo-1.13-3.6.x86_64 libjson-c2-debuginfo-0.12-4.2.x86_64 liblzma5-debuginfo-5.0.5-3.5.x86_64 libogg0-debuginfo-1.3.2-35.5.x86_64 libopenssl1_0_0-debuginfo-1.0.1i-12.1.x86_64 libpciaccess0-debuginfo-0.13.4-28.1.x86_64 libpulse0-debuginfo-8.0-2.1.x86_64 libsndfile1-debuginfo-1.0.26-74.2.x86_64 libspeex1-debuginfo-1.2~rc2-46.3.x86_64 libtxc_dxtn-debuginfo-1.0.1-6.1.x86_64 libudev1-debuginfo-210-86.1.x86_64 libvorbis0-debuginfo-1.3.5-57.30.x86_64 libvorbisenc2-debuginfo-1.3.5-57.30.x86_64 libxcb-dri2-0-debuginfo-1.11.1-50.1.x86_64 libxcb-dri3-0-debuginfo-1.11.1-50.1.x86_64 libxcb-glx0-debuginfo-1.11.1-50.1.x86_64 libxcb-present0-debuginfo-1.11.1-50.1.x86_64 libxcb-sync1-debuginfo-1.11.1-50.1.x86_64 libxcb1-debuginfo-1.11.1-50.1.x86_64 libxshmfence1-debuginfo-1.2-13.1.x86_64 libz1-debuginfo-1.2.8-6.4.x86_64 systemd-debuginfo-210-86.1.x86_64 (gdb) bt #0 0x00007ffff72e9e0f in je_arena_salloc (demote=false, ptr=<optimized out>) at include/jemalloc/internal/arena.h:1018 #1 je_isalloc (demote=false, ptr=<optimized out>) at include/jemalloc/internal/jemalloc_internal.h:849 #2 je_malloc_usable_size (ptr=<optimized out>) at src/jemalloc.c:1861 #3 0x00007ffff6f976d1 in FMallocJemalloc::Free(void*) () from /docker/tmp/UnrealEngine/Engine/Binaries/Linux/libUE4Editor-Core.so #4 0x00007ffff6f9e70a in FMemory::Free(void*) () from /docker/tmp/UnrealEngine/Engine/Binaries/Linux/libUE4Editor-Core.so #5 0x00007fffed8be9a6 in operator delete(void*) () from /docker/tmp/UnrealEngine/Engine/Binaries/Linux/libUE4Editor-UnrealEd.so #6 0x00007fffedb95e95 in std::_Rb_tree<std::string, std::pair<std::string const, std::string>, std::_Select1st<std::pair<std::string const, std::string> >, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > >::_M_erase(std::_Rb_tree_node<std::pair<std::string const, std::string> >*) () from /docker/tmp/UnrealEngine/Engine/Binaries/Linux/libUE4Editor-UnrealEd.so #7 0x00007fffb30cc888 in LLVMAddTargetDependentFunctionAttr () from /usr/lib64/libLLVM-3.9svn.so #8 0x00007fffb5fd3bfd in radeon_llvm_add_attribute (F=0x7fff9454ae58, name=0x7fffb60dfe83 "ShaderType", value=<optimized out>) at radeon_llvm_emit.c:63 #9 0x00007fffb5ef9aee in si_create_function (ctx=ctx@entry=0x7fff9aff4f70, returns=<optimized out>, num_returns=<optimized out>, params=params@entry=0x7fff9aff4870, num_params=<optimized out>, last_array_pointer=4, last_sgpr=7) at si_shader.c:3764 #10 0x00007fffb5ef9d25 in create_function (ctx=ctx@entry=0x7fff9aff4f70) at si_shader.c:4046 #11 0x00007fffb5f041c2 in si_compile_tgsi_shader (sscreen=sscreen@entry=0x773330, tm=tm@entry=0x7fff94073fa0, shader=shader@entry=0x7fff9454f630, is_monolithic=is_monolithic@entry=true, debug=debug@entry=0x7fff94002958) at si_shader.c:4926 #12 0x00007fffb5f04c8a in si_shader_create (sscreen=0x773330, tm=0x7fff94073fa0, shader=shader@entry=0x7fff9454f630, debug=debug@entry=0x7fff94002958) at si_shader.c:5909 #13 0x00007fffb5f10387 in si_shader_select_with_key (ctx=0x7fff940023a0, state=0x7fff94002fe0, key=0x7fff9affc800) at si_state_shaders.c:1014 #14 0x00007fffb5f104ac in si_shader_select (ctx=<optimized out>, state=<optimized out>) at si_state_shaders.c:1042 #15 0x00007fffb5f12b27 in si_update_shaders (sctx=sctx@entry=0x7fff940023a0) at si_state_shaders.c:1971 #16 0x00007fffb5f0d603 in si_draw_vbo (ctx=0x7fff940023a0, info=0x7fff9affca60) at si_state_draw.c:800 #17 0x00007fffb5bf994c in util_draw_arrays_instanced (mode=6, start=0, count=4, start_instance=0, instance_count=1, pipe=0x7fff940023a0) at util/u_draw.h:99 #18 blitter_draw (ctx=0x7fff94069390, x1=<optimized out>, y1=<optimized out>, x2=<optimized out>, y2=<optimized out>, depth=<optimized out>, num_instances=num_instances@entry=1) at util/u_blitter.c:1202 #19 0x00007fffb5bf9a4c in util_blitter_draw_rectangle (blitter=<optimized out>, x1=<optimized out>, y1=<optimized out>, x2=<optimized out>, y2=<optimized out>, depth=<optimized out>, type=<optimized out>, attrib=attrib@entry=0x7fff9affcc20) at util/u_blitter.c:1226 #20 0x00007fffb5fc4639 in r600_draw_rectangle (blitter=0x7fff94069390, x1=<optimized out>, y1=0, x2=600, y2=200, depth=<optimized out>, type=<optimized out>, attrib=0x7fff9affcc20) at r600_pipe_common.c:88 #21 0x00007fffb5bfc2eb in util_blitter_blit_generic (blitter=0x7fff94069390, dst=dst@entry=0x7fff945400f0, dstbox=dstbox@entry=0x7fff9affcd60, src=src@entry=0x7fff945401c0, srcbox=0x7fff9affce40, src_width0=src_width0@entry=600, src_height0=src_height0@entry=200, mask=mask@entry=63, filter=filter@entry=0, scissor=scissor@entry=0x0, alpha_blend=alpha_blend@entry=0 '\000') at util/u_blitter.c:1694 #22 0x00007fffb5ef06a7 in si_resource_copy_region (ctx=0x7fff940023a0, dst=<optimized out>, dst_level=<optimized out>, dstx=0, dsty=0, dstz=0, src=0x7fff94543140, src_level=0, src_box=<optimized out>) at si_blit.c:627 #23 0x00007fffb5fc92be in r600_copy_from_staging_texture (rtransfer=0x7fff945527f0, ctx=<optimized out>) at r600_texture.c:105 #24 r600_texture_transfer_unmap (ctx=<optimized out>, transfer=0x7fff945527f0) at r600_texture.c:1171 #25 0x00007fffb5ab92d1 in pipe_transfer_unmap (transfer=<optimized out>, context=<optimized out>) at ../../src/gallium/auxiliary/util/u_inlines.h:480 #26 st_texture_image_unmap (st=<optimized out>, stImage=<optimized out>, slice=<optimized out>) at state_tracker/st_texture.c:309 ---Type <return> to continue, or q <return> to quit--- #27 0x00007fffb5a12f6b in store_texsubimage (ctx=ctx@entry=0x7fff94081240, texImage=texImage@entry=0x7fff94550850, xoffset=xoffset@entry=0, yoffset=yoffset@entry=0, zoffset=zoffset@entry=0, width=600, height=200, depth=1, format=32993, type=5121, pixels=0x7fffa4b85000, packing=0x7fff9409c5b0, caller=0x7fffb601d075 "glTexSubImage") at main/texstore.c:1082 #28 0x00007fffb5a131e5 in _mesa_store_texsubimage (ctx=ctx@entry=0x7fff94081240, dims=dims@entry=2, texImage=texImage@entry=0x7fff94550850, xoffset=xoffset@entry=0, yoffset=yoffset@entry=0, zoffset=zoffset@entry=0, width=<optimized out>, width@entry=600, height=<optimized out>, height@entry=200, depth=<optimized out>, depth@entry=1, format=<optimized out>, format@entry=32993, type=<optimized out>, type@entry=5121, pixels=<optimized out>, pixels@entry=0x7fffa4b85000, packing=<optimized out>, packing@entry=0x7fff9409c5b0) at main/texstore.c:1139 #29 0x00007fffb5a79627 in st_TexSubImage (ctx=ctx@entry=0x7fff94081240, dims=dims@entry=2, texImage=texImage@entry=0x7fff94550850, xoffset=xoffset@entry=0, yoffset=yoffset@entry=0, zoffset=zoffset@entry=0, width=600, height=200, depth=1, format=format@entry=32993, type=type@entry=5121, pixels=pixels@entry=0x7fffa4b85000, unpack=unpack@entry=0x7fff9409c5b0) at state_tracker/st_cb_texture.c:1896 #30 0x00007fffb5a7b283 in st_TexImage (ctx=0x7fff94081240, dims=2, texImage=0x7fff94550850, format=32993, type=5121, pixels=0x7fffa4b85000, unpack=0x7fff9409c5b0) at state_tracker/st_cb_texture.c:1920 #31 0x00007fffb5a01383 in teximage (ctx=0x7fff94081240, compressed=compressed@entry=0 '\000', dims=dims@entry=2, target=3553, level=0, internalFormat=<optimized out>, width=600, height=200, depth=depth@entry=1, border=0, format=format@entry=32993, type=type@entry=5121, imageSize=imageSize@entry=0, pixels=pixels@entry=0x7fffa4b85000) at main/teximage.c:2980 #32 0x00007fffb5a02770 in _mesa_TexImage2D (target=<optimized out>, level=<optimized out>, internalFormat=<optimized out>, width=<optimized out>, height=<optimized out>, border=<optimized out>, format=32993, type=5121, pixels=0x7fffa4b85000) at main/teximage.c:3019 #33 0x00007ffff705dce7 in StartSplashScreenThread(void*) () from /docker/tmp/UnrealEngine/Engine/Binaries/Linux/libUE4Editor-Core.so #34 0x00007ffff735ed6b in SDL_RunThread (data=<optimized out>) at /home/rcl/build/2015-07-13/SDL-gui-backend/src/thread/SDL_thread.c:282 #35 0x00007ffff7379fe9 in RunThread (data=<optimized out>) at /home/rcl/build/2015-07-13/SDL-gui-backend/src/thread/pthread/SDL_systhread.c:74 #36 0x00007ffff7bc70a4 in start_thread (arg=0x7fff9afff700) at pthread_create.c:309 #37 0x00007fffeabcefed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 93784] Hybrid graphics: GPU lockup when running glxgears
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93784 Bug ID: 93784 Summary: Hybrid graphics: GPU lockup when running glxgears Product: Mesa Version: 11.0 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: nioko1337(a)googlemail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 121146 --> https://bugs.freedesktop.org/attachment.cgi?id=121146&action=edit dmesg output My laptop has the following discrete graphics card (lspci output): 0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] (rev ff) When running glxgears (or any graphical application) with DRI_PRIME=1, the window appears but it stays just black (also it does not print any FPS in the console). After starting glxgears the first time, the GPU locks up (see dmesg.txt). -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 93341] GPU lockups on RadeonHD 7770 (radeonsi driver) when running OpenGL games
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93341 Bug ID: 93341 Summary: GPU lockups on RadeonHD 7770 (radeonsi driver) when running OpenGL games Product: Mesa Version: 11.0 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: nekohayo(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Fedora 23, xorg-x11-drv-ati, on a Dell Precision T3500 (latest BIOS, A17) with a RadeonHD 7770 GPU. Running the latest up-to-date stock packages from Fedora. If I start a game like Xonotic (from the Fedora repos) or Unvanquished (latest alpha binary build downloaded from their github repo), after a minute or two of just looking around as a spectator player, I'll eventually see my computer's monitor turn off all of a sudden. Sound will continue to play for a while, then it might stop/loop. After a few seconds, the kernel will be locked up with the CapsLock LED no longer working. This also happened to me once simply by watching a video fullscreen in Totem (I'm running GNOME Shell, FWIW), but this is a much rarer occurrence. Unfortunately I don't have knowledge of debugging such things, and ABRT somehow thinks my kernel is tainted with the "I" status (meaning it's "working around a severe firmware bug"), which I suppose might be the radeon microcode, so I can't get ABRT to create a nice automated retrace/full debug thing for me. But at least it still has stuff stored on disk, if there's anything in there you'd need: # ls -lh /var/spool/abrt/oops-2015-12-10-21:50:22-777-1/ -rw-r----- 1 root abrt 5 10 déc 21:50 abrt_version -rw-r----- 1 root abrt 9 10 déc 21:50 analyzer -rw-r----- 1 root abrt 6 10 déc 21:50 architecture -rw-r----- 1 root abrt 3,7K 10 déc 21:50 backtrace -rw-r----- 1 root abrt 124 10 déc 21:50 cmdline -rw-r----- 1 root abrt 16 10 déc 21:50 component -rw-r----- 1 root abrt 1 10 déc 21:50 count -rw-r----- 1 root abrt 71K 10 déc 21:50 dmesg -rw-r----- 1 root abrt 40 10 déc 21:50 duphash -rw-r----- 1 root abrt 23 10 déc 21:50 extra-cc -rw-r----- 1 root abrt 8 10 déc 21:50 hostname -rw-r----- 1 root abrt 21 10 déc 21:50 kernel -rw-r----- 1 root abrt 25 10 déc 21:50 kernel_tainted_long -rw-r----- 1 root abrt 3 10 déc 21:50 kernel_tainted_short -rw-r----- 1 root abrt 10 10 déc 21:50 last_occurrence -rw-r----- 1 root abrt 173 10 déc 21:50 not-reportable -rw-r----- 1 root abrt 518 10 déc 21:50 os_info -rw-r----- 1 root abrt 32 10 déc 21:50 os_release -rw-r----- 1 root abrt 6 10 déc 21:50 package -rw-r----- 1 root abrt 7 10 déc 21:50 pkg_arch -rw-r----- 1 root abrt 2 10 déc 21:50 pkg_epoch -rw-r----- 1 root abrt 12 10 déc 21:50 pkg_name -rw-r----- 1 root abrt 9 10 déc 21:50 pkg_release -rw-r----- 1 root abrt 6 10 déc 21:50 pkg_version -rw-r----- 1 root abrt 4,4K 10 déc 21:50 proc_modules -rw-r----- 1 root abrt 37 10 déc 21:50 reason -rw-r----- 1 root abrt 8 10 déc 21:50 runlevel -rw-r----- 1 root abrt 269 10 déc 21:50 suspend_stats -rw-r----- 1 root abrt 10 10 déc 21:50 time -rw-r----- 1 root abrt 10 10 déc 21:50 type -rw-r----- 1 root abrt 40 10 déc 21:50 uuid This is what I get in journalctl/dmesg: -- Logs begin at lun 2015-11-30 21:48:19 EST, end at jeu 2015-12-10 23:48:33 EST. -- déc 10 21:49:00 the_PC kernel: radeon 0000:02:00.0: ring 3 stalled for more than 10115msec déc 10 21:49:00 the_PC kernel: radeon 0000:02:00.0: GPU lockup (current fence id 0x000000000000a5fe last fence id 0x000000000000a600 on ring 3) déc 10 21:49:01 the_PC kernel: BUG: unable to handle kernel paging request at ffffc90404239ffc déc 10 21:49:01 the_PC kernel: IP: [<ffffffffa00f850a>] radeon_ring_backup+0xda/0x190 [radeon] déc 10 21:49:01 the_PC kernel: PGD 6068a8067 PUD 0 déc 10 21:49:01 the_PC kernel: Oops: 0000 [#1] SMP déc 10 21:49:01 the_PC kernel: Modules linked in: fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack tun bridge stp llc ebtable déc 10 21:49:01 the_PC kernel: radeon i2c_algo_bit drm_kms_helper ttm drm serio_raw déc 10 21:49:01 the_PC kernel: CPU: 3 PID: 153 Comm: kworker/u64:7 Tainted: G I 4.2.6-301.fc23.x86_64 #1 déc 10 21:49:01 the_PC kernel: Hardware name: Dell Inc. Precision WorkStation T3500 /0K095G, BIOS A17 05/28/2013 déc 10 21:49:01 the_PC kernel: Workqueue: radeon-crtc radeon_flip_work_func [radeon] déc 10 21:49:01 the_PC kernel: task: ffff88060299b880 ti: ffff8805ff5c0000 task.ti: ffff8805ff5c0000 déc 10 21:49:01 the_PC kernel: RIP: 0010:[<ffffffffa00f850a>] [<ffffffffa00f850a>] radeon_ring_backup+0xda/0x190 [radeon] déc 10 21:49:01 the_PC kernel: RSP: 0018:ffff8805ff5c3c98 EFLAGS: 00010206 déc 10 21:49:01 the_PC kernel: RAX: ffffc9000fe50000 RBX: 00000000ffffffff RCX: 0000000000000000 déc 10 21:49:01 the_PC kernel: RDX: 0000000000000000 RSI: ffffc90404239ffc RDI: 0000000000080500 déc 10 21:49:01 the_PC kernel: RBP: ffff8805ff5c3cd8 R08: ffff8805771f8cc0 R09: 0000000000082000 déc 10 21:49:01 the_PC kernel: R10: 8000000000000163 R11: ffffffff81a609e9 R12: ffff880036a654d8 déc 10 21:49:01 the_PC kernel: R13: ffff880036a654b0 R14: 0000000000020141 R15: ffff8805ff5c3d30 déc 10 21:49:01 the_PC kernel: FS: 0000000000000000(0000) GS:ffff880606ec0000(0000) knlGS:0000000000000000 déc 10 21:49:01 the_PC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b déc 10 21:49:01 the_PC kernel: CR2: ffffc90404239ffc CR3: 0000000001c0b000 CR4: 00000000000006e0 déc 10 21:49:01 the_PC kernel: Stack: déc 10 21:49:01 the_PC kernel: ffff8805ff5c3cc8 ffffffffa00f9413 ffff880036a64000 ffff880036a64000 déc 10 21:49:01 the_PC kernel: ffff880036a654d8 ffff8805ff5c3d30 ffff880036a654d8 0000000000000000 déc 10 21:49:01 the_PC kernel: ffff8805ff5c3da8 ffffffffa00c6c80 ffffffff810df990 ffff880036a64738 déc 10 21:49:01 the_PC kernel: Call Trace: déc 10 21:49:01 the_PC kernel: [<ffffffffa00f9413>] ? radeon_irq_kms_disable_hpd+0x73/0x80 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffffa00c6c80>] radeon_gpu_reset+0xd0/0x330 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffff810df990>] ? wake_atomic_t_function+0x70/0x70 déc 10 21:49:01 the_PC kernel: [<ffffffffa00e058f>] ? radeon_fence_wait+0x9f/0xe0 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffffa00ed960>] radeon_flip_work_func+0x130/0x170 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffff810b650e>] process_one_work+0x19e/0x3f0 déc 10 21:49:01 the_PC kernel: [<ffffffff810b67ae>] worker_thread+0x4e/0x450 déc 10 21:49:01 the_PC kernel: [<ffffffff810b6760>] ? process_one_work+0x3f0/0x3f0 déc 10 21:49:01 the_PC kernel: [<ffffffff810b6760>] ? process_one_work+0x3f0/0x3f0 déc 10 21:49:01 the_PC kernel: [<ffffffff810bc8b8>] kthread+0xd8/0xf0 déc 10 21:49:01 the_PC kernel: [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160 déc 10 21:49:01 the_PC kernel: [<ffffffff817797df>] ret_from_fork+0x3f/0x70 déc 10 21:49:01 the_PC kernel: [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160 déc 10 21:49:01 the_PC kernel: Code: 10 e1 48 85 c0 49 89 07 74 6c 41 8d 7e ff 31 d2 48 c1 e7 02 eb 07 49 8b 07 48 83 c2 04 49 8b 74 24 08 8d 4b 01 89 db 48 8d 34 9e <8b> 36 89 34 10 41 23 4c 24 54 48 39 d7 89 cb 75 da 4c 89 ef e8 déc 10 21:49:01 the_PC kernel: RIP [<ffffffffa00f850a>] radeon_ring_backup+0xda/0x190 [radeon] déc 10 21:49:01 the_PC kernel: RSP <ffff8805ff5c3c98> déc 10 21:49:01 the_PC kernel: CR2: ffffc90404239ffc déc 10 21:49:01 the_PC kernel: ---[ end trace 37e2470f6b251992 ]--- déc 10 21:49:01 the_PC kernel: BUG: unable to handle kernel paging request at ffffffffffffffd8 déc 10 21:49:01 the_PC kernel: IP: [<ffffffff810bcd40>] kthread_data+0x10/0x20 déc 10 21:49:01 the_PC kernel: PGD 1c0e067 PUD 1c10067 PMD 0 déc 10 21:49:01 the_PC kernel: Oops: 0000 [#2] SMP déc 10 21:49:01 the_PC kernel: Modules linked in: fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack tun bridge stp llc ebtable déc 10 21:49:01 the_PC kernel: radeon i2c_algo_bit drm_kms_helper ttm drm serio_raw déc 10 21:49:01 the_PC kernel: CPU: 3 PID: 153 Comm: kworker/u64:7 Tainted: G D I 4.2.6-301.fc23.x86_64 #1 déc 10 21:49:01 the_PC kernel: Hardware name: Dell Inc. Precision WorkStation T3500 /0K095G, BIOS A17 05/28/2013 déc 10 21:49:01 the_PC kernel: task: ffff88060299b880 ti: ffff8805ff5c0000 task.ti: ffff8805ff5c0000 déc 10 21:49:01 the_PC kernel: RIP: 0010:[<ffffffff810bcd40>] [<ffffffff810bcd40>] kthread_data+0x10/0x20 déc 10 21:49:01 the_PC kernel: RSP: 0018:ffff8805ff5c3918 EFLAGS: 00010096 déc 10 21:49:01 the_PC kernel: RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000005 déc 10 21:49:01 the_PC kernel: RDX: 0000000000000005 RSI: 0000000000000003 RDI: ffff88060299b880 déc 10 21:49:01 the_PC kernel: RBP: ffff8805ff5c3918 R08: ffff88060299b910 R09: 0000000000000000 déc 10 21:49:01 the_PC kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000167c0 déc 10 21:49:01 the_PC kernel: R13: ffff88060299b880 R14: ffff880606ed67c0 R15: 0000000000000003 déc 10 21:49:01 the_PC kernel: FS: 0000000000000000(0000) GS:ffff880606ec0000(0000) knlGS:0000000000000000 déc 10 21:49:01 the_PC kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b déc 10 21:49:01 the_PC kernel: CR2: 0000000000000028 CR3: 0000000001c0b000 CR4: 00000000000006e0 déc 10 21:49:01 the_PC kernel: Stack: déc 10 21:49:01 the_PC kernel: ffff8805ff5c3938 ffffffff810b7385 ffff8805ff5c3938 ffff880606ed67c0 déc 10 21:49:01 the_PC kernel: ffff8805ff5c3988 ffffffff81774fc0 ffff880500000000 ffff88060299b880 déc 10 21:49:01 the_PC kernel: ffff8805ff5c3988 ffff8805ff5c4000 ffff8805ff5c39f0 ffff8805ff5c39f0 déc 10 21:49:01 the_PC kernel: Call Trace: déc 10 21:49:01 the_PC kernel: [<ffffffff810b7385>] wq_worker_sleeping+0x15/0xa0 déc 10 21:49:01 the_PC kernel: [<ffffffff81774fc0>] __schedule+0x620/0x950 déc 10 21:49:01 the_PC kernel: [<ffffffff81775327>] schedule+0x37/0x80 déc 10 21:49:01 the_PC kernel: [<ffffffff810a103a>] do_exit+0x80a/0xae0 déc 10 21:49:01 the_PC kernel: [<ffffffff810180fe>] oops_end+0x9e/0xd0 déc 10 21:49:01 the_PC kernel: [<ffffffff81064c25>] no_context+0x135/0x380 déc 10 21:49:01 the_PC kernel: [<ffffffff81064ef0>] __bad_area_nosemaphore+0x80/0x1f0 déc 10 21:49:01 the_PC kernel: [<ffffffff81065073>] bad_area_nosemaphore+0x13/0x20 déc 10 21:49:01 the_PC kernel: [<ffffffff81065357>] __do_page_fault+0xb7/0x400 déc 10 21:49:01 the_PC kernel: [<ffffffff810656cf>] do_page_fault+0x2f/0x80 déc 10 21:49:01 the_PC kernel: [<ffffffff8177b378>] page_fault+0x28/0x30 déc 10 21:49:01 the_PC kernel: [<ffffffffa00f850a>] ? radeon_ring_backup+0xda/0x190 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffffa00f85b0>] ? radeon_ring_backup+0x180/0x190 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffffa00f9413>] ? radeon_irq_kms_disable_hpd+0x73/0x80 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffffa00c6c80>] radeon_gpu_reset+0xd0/0x330 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffff810df990>] ? wake_atomic_t_function+0x70/0x70 déc 10 21:49:01 the_PC kernel: [<ffffffffa00e058f>] ? radeon_fence_wait+0x9f/0xe0 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffffa00ed960>] radeon_flip_work_func+0x130/0x170 [radeon] déc 10 21:49:01 the_PC kernel: [<ffffffff810b650e>] process_one_work+0x19e/0x3f0 déc 10 21:49:01 the_PC kernel: [<ffffffff810b67ae>] worker_thread+0x4e/0x450 déc 10 21:49:01 the_PC kernel: [<ffffffff810b6760>] ? process_one_work+0x3f0/0x3f0 déc 10 21:49:01 the_PC kernel: [<ffffffff810b6760>] ? process_one_work+0x3f0/0x3f0 déc 10 21:49:01 the_PC kernel: [<ffffffff810bc8b8>] kthread+0xd8/0xf0 déc 10 21:49:01 the_PC kernel: [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160 déc 10 21:49:01 the_PC kernel: [<ffffffff817797df>] ret_from_fork+0x3f/0x70 déc 10 21:49:01 the_PC kernel: [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160 déc 10 21:49:01 the_PC kernel: Code: c4 08 44 89 e8 5b 41 5c 41 5d 5d c3 4c 89 e7 e8 e7 eb fd ff eb 88 0f 1f 44 00 00 66 66 66 66 90 48 8b 87 90 05 00 00 55 48 89 e5 <48> 8b 40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 déc 10 21:49:01 the_PC kernel: RIP [<ffffffff810bcd40>] kthread_data+0x10/0x20 déc 10 21:49:01 the_PC kernel: RSP <ffff8805ff5c3918> déc 10 21:49:01 the_PC kernel: CR2: ffffffffffffffd8 déc 10 21:49:01 the_PC kernel: ---[ end trace 37e2470f6b251993 ]--- déc 10 21:49:01 the_PC kernel: Fixing recursive fault but reboot is needed! -- Reboot -- -- You are receiving this mail because: You are the assignee for the bug.

1 31

[Bug 93101] GPU Fault almost burned the CPU
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93101 Bug ID: 93101 Summary: GPU Fault almost burned the CPU 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: dev(a)illwieckz.net QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120103 --> https://bugs.freedesktop.org/attachment.cgi?id=120103&action=edit syslog (short) Hi, this is an issue about the fact that some GPU lockup can lead to some CPU burn (for real). Some hours ago I get a GPU lockup while I was trying to read a DVD with VLC. The video rendering wasn't functionnal (no picture), then the GPU started to display weird things (see attached photo) then locked up. I've joined some log, one very long syslog, and some abstract for this one (more easy to read, but I gave you the original one in case of I missed something). To summarize, you can read lines like that in the syslog: ``` Nov 24 22:58:18 gollum gnome-session[3720]: [00007f134c173c20] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding Nov 24 22:58:18 gollum kernel: [97035.599456] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00002126 Nov 24 22:58:18 gollum kernel: [97035.599460] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0408800C Nov 24 22:58:18 gollum kernel: [97035.599465] VM fault (0x0c, vmid 2) at page 8486, read from 'TC4' (0x54433400) (136) Nov 24 22:58:55 gollum kernel: [97072.747472] radeon 0000:01:00.0: ring 0 stalled for more than 10088msec Nov 24 22:58:55 gollum kernel: [97072.747483] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000059fcff last fence id 0x000000000059fd12 on ring 0) Nov 24 22:59:04 gollum kernel: [97081.259933] WARNING: CPU: 4 PID: 23502 at /home/kernel/COD/linux/drivers/gpu/drm/radeon/radeon_object.c:83 radeon_ttm_bo_destroy+0xe7/0xf0 [radeon]() ``` My system is running: vlc 3.0.0~~git20151123+r62463+34~ubuntu15.10.1 linux-image-4.3.0-040300-generic 4.3.0-040300.201511020949 libdrm-radeon1 2.4.65+git1511161830.8913cd~gd~w xserver-xorg-video-radeon 7.6.99+git1511170732.10b7c3~gd~w libgl1-mesa-dri 11.2~git1511231930.e4c122~gd~w mesa-vdpau-drivers 11.2~git1511231930.e4c122~gd~w That is a real issue but it's not the topic of this ticket. The really big problem is this bug almost burned my CPU. I explain. When the bug occurred, I tried to track it. Instead of rebooting my computer I started a laptop in order to connect to my computer using ssh, and to diagnose some stuff on the living system. While the laptop were booting, I took some photo of my screen. But suddenly, my computer shutdown itself. The CPU critical temperature was reached. Normal operation temperature is normally between 30°C and 40°C on my system. In case of emergency, I have two regulators running on my computer. The first one raises fan speed from 128 tr/min to 1400 tr/min when temperature reaches 50°C, and the second one downclocks all the 8 core from 4.7 GHz to 1.4GHz when the temperature reaches 70°C. Both regulators are userspace regulators. The first is the well-known fancontrol, and the other one is mine. Both works well (if I use cpuburn for example). The fact is, when the GPU lockup occurred, something from the driver goes wrong on the CPU side. It looks like some infinite loop started on my cores, doing some extensive tasks, probably without having to deal with external components (like central memory unit) in order to never slow done the CPU. In fact, the computer acted exactly like if I was running one cpuburn process per core using performance cpu governor during a summer noon. But there was an exception, the fan never accelerated (so it was still running at 128 tr/min when the CPU reached 90°, and the cpu was never downclocked too. That's why I wrote this issue. When this bug occured, the system goes so wrong the CPU was on knees and no regulator was able to control the CPU fan so the CPU endlessly heating. Hopefully, the internal CPU temperature protection shutdown automatically my computer to save itself. But if someone use a CPU with a faulty temperature safety mechanisme, this GPU lockup can lead to a CPU burn for real ! -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 92428] Sword Coast Legends causing GPU lockup. radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000afd1 last fence id 0x000000000000b194 on ring 3)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=92428 Bug ID: 92428 Summary: Sword Coast Legends causing GPU lockup. radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000000afd1 last fence id 0x000000000000b194 on ring 3) Product: Mesa Version: 10.6 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: h0ser(a)h0sed.org QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 118821 --> https://bugs.freedesktop.org/attachment.cgi?id=118821&action=edit System Logs Bear with me as it's my first time submitting a bug report. When loading a level in Sword Coast Legends, the driver crashes and hard locks the PC. Attached is what I believe are the relevant portions of the logs. -- You are receiving this mail because: You are the assignee for the bug.

1 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017