dri-devel January 2019

dri-devel@lists.freedesktop.org

279 participants
2022 discussions

[Bug 109389] memory leak in `amdgpu_bo_create()`
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109389 Bug ID: 109389 Summary: memory leak in `amdgpu_bo_create()` Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: pmenzel+bugs.freedesktop.org(a)molgen.mpg.de Created attachment 143156 --> https://bugs.freedesktop.org/attachment.cgi?id=143156&action=edit Output of kmemleak With Linux 5.0-rc2+ the memory leaks below are reported by kmemleak. ``` unreferenced object 0xffff9f83850c5000 (size 2048): comm "gnome-shell", pid 569, jiffies 4294682217 (age 9133.583s) hex dump (first 32 bytes): 02 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................ 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<000000001aec1dd8>] amdgpu_bo_create+0x40/0x220 [amdgpu] [<000000007da39c30>] amdgpu_gem_object_create+0x9e/0x120 [amdgpu] [<00000000099484e9>] amdgpu_gem_create_ioctl+0x1d3/0x290 [amdgpu] [<000000009d8251d3>] drm_ioctl_kernel+0xa9/0xf0 [<0000000050b61811>] drm_ioctl+0x201/0x3a0 [<000000007c88aae3>] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] [<0000000083291747>] do_vfs_ioctl+0xa4/0x630 [<00000000722b6176>] ksys_ioctl+0x60/0x90 [<000000001bfa30dc>] __x64_sys_ioctl+0x16/0x20 [<000000007862c966>] do_syscall_64+0x55/0x170 [<00000000a8eeee88>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [<000000001242345f>] 0xffffffffffffffff unreferenced object 0xffff9f837cdd36c0 (size 64): comm "gnome-shell", pid 569, jiffies 4294682217 (age 9133.583s) hex dump (first 32 bytes): d4 23 b4 d5 ab e2 45 94 d0 53 43 86 83 9f ff ff .#....E..SC..... 01 00 00 00 04 00 00 00 60 ab cc 5c 83 9f ff ff ........`..\.... backtrace: [<000000000768e015>] ttm_bo_mem_space+0x41/0x4a0 [<00000000f11076b2>] ttm_bo_validate+0xc7/0x130 [<00000000c820992e>] ttm_bo_init_reserved+0x32f/0x390 [<00000000fcfd5ce2>] amdgpu_bo_do_create+0x1ed/0x420 [amdgpu] [<000000001aec1dd8>] amdgpu_bo_create+0x40/0x220 [amdgpu] [<000000007da39c30>] amdgpu_gem_object_create+0x9e/0x120 [amdgpu] [<00000000099484e9>] amdgpu_gem_create_ioctl+0x1d3/0x290 [amdgpu] [<000000009d8251d3>] drm_ioctl_kernel+0xa9/0xf0 [<0000000050b61811>] drm_ioctl+0x201/0x3a0 [<000000007c88aae3>] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] [<0000000083291747>] do_vfs_ioctl+0xa4/0x630 [<00000000722b6176>] ksys_ioctl+0x60/0x90 [<000000001bfa30dc>] __x64_sys_ioctl+0x16/0x20 [<000000007862c966>] do_syscall_64+0x55/0x170 [<00000000a8eeee88>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [<000000001242345f>] 0xffffffffffffffff ``` -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 93809] playing Just Cause causes system crash
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93809 Bug ID: 93809 Summary: playing Just Cause causes system crash 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: aaalmosss(a)gmail.com It happens randomly, usually when lots of things are happening, like during settlement takeovers. The screen freezes, sound stops, and only the magic sysrq keys are working. GPU is Radeon R9 270x, Linux 4.3.3, libdrm 2.4.66, Mesa 11.1.1, wine 1.7.55. I also tried gallium nine, and that made it more unstable, it crashes even when just riding around. BTW nine doesn't help with the horrible performance (5-15 fps), but it introduces several graphical glitches. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 93753] Sometimes wrong clk frequency of Display after dpms mode changes.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93753 Bug ID: 93753 Summary: Sometimes wrong clk frequency of Display after dpms mode changes. Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: t.graziadei(a)bachmann.info Created attachment 121103 --> https://bugs.freedesktop.org/attachment.cgi?id=121103&action=edit Screenshot of failure Sometimes after the deactivation of the screensaver or also on bootup the screen shows flickering noise and a duplicated screen image. (Attached there is the used test image and a screenshot of the failure image). We tested on various kernel versions, latest kernel tested was 4.4.0. We run a customized debian image. Further investigations showed, that in the failure scenario the measured clk frequency was only 25MHz but it should be 35MHz. We also tried to deactivate dpms completly (radeon.dpm=0 in kernel parameters) and also turned the dpms off in the screensaver, but we still sometimes encounter the problem after a reboot. Attached you will find a dmesg output with drm.debug=0xf activated. We use a Radeon PALM on a AMD G-T40E 2x1GHz -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 93713] System hangs (beomes totaly unresponsive) when trying to use hybrid graphics with ATI 7730M videocard
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93713 Bug ID: 93713 Summary: System hangs (beomes totaly unresponsive) when trying to use hybrid graphics with ATI 7730M videocard Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: g0000ga(a)gmail.com When trying to use my discrete video card whole system freezes after couple of seconds and doesn't react on anything. I've tried to have a delayed killall -9 running in the background like "sleep 60 && killall -9 glmark2 &" but it seems to be never run or having no effect. Only hard reset helps. Have Intel HD4000 + muxless Radeon 7730M [g0ga@work ~]✘ xrandr --setprovideroffloadsink radeon Intel [g0ga@work ~]✘ DRI_PRIME=1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE (DRM 2.43.0, LLVM 3.7.0) doesn't matter what to run, everything is going to die. kernel 4.3.3 + xorg 1.18.0, archlinux distribution, most recent at time of writing this post. Please let me know how to provide more data for you being able to debug this. Thanks, Victor -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 109384] Bad DisplayPort enumeration and wrong refresh rate with Hawaii chip
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109384 Bug ID: 109384 Summary: Bad DisplayPort enumeration and wrong refresh rate with Hawaii chip Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: fabio0x(a)keemail.me Created attachment 143150 --> https://bugs.freedesktop.org/attachment.cgi?id=143150&action=edit Xorg.0 log with DC off I'm running Solus KDE with kernel 4.20.2 but I've had these issues since kernel 4.19. Here's the list of issues with AMDGPU DC enabled: - With Solus' default kernel flags I have wrong DisplayPort enumeration, meaning that I get DisplayPort-1 when I turn on the computer, and then DisplayPort-2 when I get my monitor to sleep and then I wake it up. - If I put my computer on sleep (suspension) and then wake it up, I cannot set a usable refresh rate. This means I actually get 40 Hz when I set 60, and 45 Hz when I set 74 (yeah, I have a bit of screen "overclocking". That's how I found DisplayPort enumeration is wrong). - I get microstuttering, particularly noticeable when I drag windows around. Now, all these issues are non existant if I set the amdgpu.dc=0 kernel flag. Also, DisplayPort number is DisplayPort-0 under any circumstances. ❯ inxi -G Graphics: Device-1: AMD Hawaii PRO [Radeon R9 290/390] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.3 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon R9 200 Series (HAWAII DRM 3.27.0 4.20.2-107.current LLVM 7.0.0) v: 4.5 Mesa 18.3.1 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 93525] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93525 Bug ID: 93525 Summary: [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: rafaelrcenteio(a)gmail.com Created attachment 120720 --> https://bugs.freedesktop.org/attachment.cgi?id=120720&action=edit dmesg output. I am receiving the following message on boot: "[ 13.198262] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume" uname -a Linux rafael 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14) x86_64 GNU/Linux lspci In attachment: dmesg's output. >From dmidecode: Vendor: Hewlett-Packard Version: F.48 Release Date: 11/09/2011 ROM Size: 2048 kB ... BIOS Revision: 15.48 Firmware Revision: 60.80 Worth mentioning that the behaviour of the fans and the temperatures change a lot after suspension/hibernation. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 93452] kernel crash(3.19 up) DRI_PRIME=1 HP zbook 14
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93452 Bug ID: 93452 Summary: kernel crash(3.19 up) DRI_PRIME=1 HP zbook 14 Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lathanderjk(a)gmail.com I have issue with new kernels since 3.19 up 4.1 distribution openSUSE/Fedora but on Arch works stable for some reasons. Kernels crash when i use DRI_PRIME=1 after few minutes (max. 7) and kdump is not created. I try openSUSE leap with old 3.16.7 and works fine also try AMD only configuration(AMD as primary GPU) and also works fine. 4.2.5/4.3.0 DRI_PRIME=1 works different , crashing randomly ( two times during day test) Some more info https://bugzilla.opensuse.org/show_bug.cgi?id=954783 (drm.debug=0x0e,dmesg -n 8) openSUSE 4.1.13 [ 147.171197] [drm:i915_gem_open] [ 156.538080] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [ 156.538093] [drm] PCIE gen 2 link speeds already enabled [ 156.542218] [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). [ 156.542345] radeon 0000:03:00.0: WB enabled [ 156.542349] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880036d62c00 [ 156.542351] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff880036d62c04 [ 156.542354] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff880036d62c08 [ 156.542356] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880036d62c0c [ 156.542358] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff880036d62c10 [ 156.543910] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001435a18 [ 156.544585] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 156.544592] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 156.781101] [drm] ring test on 0 succeeded in 1 usecs [ 156.781114] [drm] ring test on 1 succeeded in 1 usecs [ 156.781121] [drm] ring test on 2 succeeded in 1 usecs [ 156.781131] [drm] ring test on 3 succeeded in 5 usecs [ 156.781140] [drm] ring test on 4 succeeded in 4 usecs [ 156.956763] [drm] ring test on 5 succeeded in 2 usecs [ 156.956772] [drm] UVD initialized successfully. [ 156.956811] [drm] ib test on ring 0 succeeded in 0 usecs [ 156.956858] [drm] ib test on ring 1 succeeded in 0 usecs [ 156.956901] [drm] ib test on ring 2 succeeded in 0 usecs [ 156.956932] [drm] ib test on ring 3 succeeded in 0 usecs [ 156.956966] [drm] ib test on ring 4 succeeded in 0 usecs [ 157.605812] [drm] ib test on ring 5 succeeded [ 157.614315] snd_hda_intel 0000:03:00.1: Enabling via VGA-switcheroo [ 157.719256] snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP = 65535 [ 157.765449] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 163.932378] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 167.286021] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 171.125632] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 174.384673] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 177.111597] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 180.648221] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 183.863776] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 187.519144] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 191.038127] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! --and crash 3.16.7 (stable) [ 75.808416] [drm:intel_crtc_cursor_set] cursor off [ 76.279634] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [ 76.279644] [drm] PCIE gen 2 link speeds already enabled [ 76.283764] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [ 76.283904] radeon 0000:03:00.0: WB enabled [ 76.283908] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880238c1dc00 [ 76.283910] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff880238c1dc04 [ 76.283912] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff880238c1dc08 [ 76.283915] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880238c1dc0c [ 76.283917] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff880238c1dc10 [ 76.285473] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011135a18 [ 76.286084] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 76.286089] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 76.481930] [drm] ring test on 0 succeeded in 1 usecs [ 76.481942] [drm] ring test on 1 succeeded in 1 usecs [ 76.481948] [drm] ring test on 2 succeeded in 1 usecs [ 76.481956] [drm] ring test on 3 succeeded in 4 usecs [ 76.481964] [drm] ring test on 4 succeeded in 4 usecs [ 76.667487] [drm] ring test on 5 succeeded in 2 usecs [ 76.667497] [drm] UVD initialized successfully. [ 76.667531] [drm] ib test on ring 0 succeeded in 0 usecs [ 76.667561] [drm] ib test on ring 1 succeeded in 0 usecs [ 76.667589] [drm] ib test on ring 2 succeeded in 0 usecs [ 76.667617] [drm] ib test on ring 3 succeeded in 0 usecs [ 76.667644] [drm] ib test on ring 4 succeeded in 0 usecs [ 76.818256] [drm] ib test on ring 5 succeeded [ 76.827403] snd_hda_intel 0000:03:00.1: Enabling via VGA-switcheroo [ 76.827546] snd_hda_intel 0000:03:00.1: irq 69 for MSI/MSI-X [ 76.861702] [drm:radeon_info_ioctl] Invalid request 37 [ 76.861713] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 79.192677] [drm:radeon_info_ioctl] Invalid request 37 [ 79.192690] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 83.737880] [drm:radeon_info_ioctl] Invalid request 37 [ 83.737892] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 89.062058] [drm:radeon_info_ioctl] Invalid request 37 [ 89.062070] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 93.254184] [drm:radeon_info_ioctl] Invalid request 37 [ 93.254197] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 96.922265] [drm:radeon_info_ioctl] Invalid request 37 [ 96.922280] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 101.272998] [drm:radeon_info_ioctl] Invalid request 37 [ 101.273015] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 104.574944] [drm:radeon_info_ioctl] Invalid request 37 [ 104.574969] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 108.408574] [drm:radeon_info_ioctl] Invalid request 37 [ 108.408597] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 111.561355] [drm:radeon_info_ioctl] Invalid request 37 [ 111.561369] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 117.931164] [drm:intel_crtc_cursor_set] cursor off [ 123.179592] [drm:intel_crtc_cursor_set] cursor off [ 130.923942] [drm:intel_crtc_cursor_set] cursor off And 4.1.15 on Arch (stable) [ 451.911996] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [ 451.912004] [drm] PCIE gen 2 link speeds already enabled [ 451.916190] [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000). [ 451.916363] radeon 0000:03:00.0: WB enabled [ 451.916366] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88023eb98c00 [ 451.916368] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff88023eb98c04 [ 451.916369] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff88023eb98c08 [ 451.916371] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88023eb98c0c [ 451.916373] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff88023eb98c10 [ 451.917925] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004435a18 [ 451.918490] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 451.918494] [drm:radeon_crtc_handle_flip] radeon_crtc->flip_status = 0 != RADEON_FLIP_SUBMITTED(2) [ 452.156274] [drm] ring test on 0 succeeded in 1 usecs [ 452.156282] [drm] ring test on 1 succeeded in 1 usecs [ 452.156287] [drm] ring test on 2 succeeded in 1 usecs [ 452.156297] [drm] ring test on 3 succeeded in 5 usecs [ 452.156305] [drm] ring test on 4 succeeded in 5 usecs [ 452.333329] [drm] ring test on 5 succeeded in 2 usecs [ 452.333338] [drm] UVD initialized successfully. [ 452.333379] [drm] ib test on ring 0 succeeded in 0 usecs [ 452.333412] [drm] ib test on ring 1 succeeded in 0 usecs [ 452.333443] [drm] ib test on ring 2 succeeded in 0 usecs [ 452.333474] [drm] ib test on ring 3 succeeded in 0 usecs [ 452.333504] [drm] ib test on ring 4 succeeded in 0 usecs [ 452.982823] [drm] ib test on ring 5 succeeded [ 452.989772] snd_hda_intel 0000:03:00.1: Enabling via VGA-switcheroo [ 453.094277] snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP = 65535 [ 453.120392] [drm:radeon_info_ioctl] macrotile mode array is cik+ only! [ 453.192020] [drm:drm_mode_addfb2] [FB:75] [ 466.009035] snd_hda_intel 0000:03:00.1: Disabling via VGA-switcheroo -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 109359] Flickering and artifacts on dual 4K displays from RX 570
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109359 Bug ID: 109359 Summary: Flickering and artifacts on dual 4K displays from RX 570 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: venemo(a)msn.com There are two Dell U2718Q 4K monitors connected to a Sapphire Pulse RX 570 ITX card, one using the DisplayPort output and the other using the HDMI output. There is a visible flickering artifact on both displays. There is no problem when only a single display is connected. Searching online yields a couple of results that suggest a workaround: manually increasing the shader and/or memory clock of the GPU. On the RX 570 the following commands can get rid of the problem: echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level echo "2" > /sys/class/drm/card0/device/pp_dpm_mclk echo "5 6 7" > /sys/class/drm/card0/device/pp_dpm_sclk However, I believe the amdgpu driver should be able to figure out the correct necessary clock settings on its own. The problem exists in Linux 4.19 and 5.0-rc1 as well. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 93450] Static in sound in Metro Redux games over HDMI
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93450 Bug ID: 93450 Summary: Static in sound in Metro Redux games over HDMI 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: acutiator(a)outlook.com Created attachment 120596 --> https://bugs.freedesktop.org/attachment.cgi?id=120596&action=edit Sound sinks I experience severe static issues when playing Metro 2033 Redux or Metro Last Light Redux on Fedora 23 with my Radeon HD5770 (Juniper) card over the HDMI port. Using the line-out port for my headphones, there is no such sound corruption. Attached are the sound sinks that are shown when I run `pacmd list-sinks`. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 93404] radeon fail when creating a new session with the same user
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=93404 Bug ID: 93404 Summary: radeon fail when creating a new session with the same user Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: bifrost(a)hotmail.it Using plasma 5, when from the lock screen i try to enter with a "New Session" and then enter the same user i was logged in, the computer hang and even the virtual console are inaccessible. Clean shutdown with power button works. GPU is AMD Radeon R9 M265X Enthusiast Graphics Log show radeon crash, but is triggered 100% by "New Session" Reproducible: Always Steps to Reproduce: 1. wait for lock screen 2. choose a "New Session" 3. try to log in with the same user already log on (with other account seems ok) log from journalctl: WARNING: CPU: 3 PID: 468 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x66/0x80() Dec 15 21:03:44 metal kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/power_dpm_state' Dec 15 21:03:44 metal kernel: Modules linked in: cmac ecb rfcomm fuse bnep joydev mousedev mmc_block arc4 nls_iso8859_1 nls_cp437 vfat fat intel_rapl iwlmvm iosf_mbi x86_pkg_temp_thermal intel_powerclamp mac80211 kvm_intel snd_hda_codec_realtek Dec 15 21:03:44 metal kernel: toshiba_bluetooth mei_me intel_gtt soundcore i2c_algo_bit mei edac_core shpchp toshiba_haps wmi thermal rfkill button battery video ac processor sch_fq_codel nfs lockd grace sunrpc fscache ip_tables x_tables ext4 Dec 15 21:03:44 metal kernel: CPU: 3 PID: 468 Comm: Xorg Tainted: G W 4.2.5-1-ARCH #1 Dec 15 21:03:44 metal kernel: Hardware name: TOSHIBA SATELLITE P50-B-115/VG20SQ, BIOS 1.50 12/09/2014 Dec 15 21:03:44 metal kernel: 0000000000000000 00000000afbaeab0 ffff880317c67ac8 ffffffff81570d0a Dec 15 21:03:44 metal kernel: 0000000000000000 ffff880317c67b20 ffff880317c67b08 ffffffff810748a6 Dec 15 21:03:44 metal kernel: 0000623b17c67b08 ffff88025af5a000 ffffffffa09ec5a8 ffff880320822bb8 Dec 15 21:03:44 metal kernel: Call Trace: Dec 15 21:03:44 metal kernel: [<ffffffff81570d0a>] dump_stack+0x4c/0x6e Dec 15 21:03:44 metal kernel: [<ffffffff810748a6>] warn_slowpath_common+0x86/0xc0 Dec 15 21:03:44 metal kernel: [<ffffffff81074935>] warn_slowpath_fmt+0x55/0x70 Dec 15 21:03:44 metal kernel: [<ffffffff81245808>] ? kernfs_path+0x48/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff81248df6>] sysfs_warn_dup+0x66/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff81248b07>] sysfs_add_file_mode_ns+0x127/0x180 Dec 15 21:03:44 metal kernel: [<ffffffff81248b8a>] sysfs_create_file_ns+0x2a/0x30 Dec 15 21:03:44 metal kernel: [<ffffffff813cf532>] device_create_file+0x42/0x90 Dec 15 21:03:44 metal kernel: [<ffffffffa091b976>] radeon_pm_late_init+0x76/0x1a0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b7945>] radeon_resume_kms+0x255/0x3b0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b5143>] radeon_pmops_runtime_resume+0x73/0xb0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff812f9e6f>] pci_pm_runtime_resume+0x7f/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813cc759>] vga_switcheroo_runtime_resume+0x39/0x40 Dec 15 21:03:44 metal kernel: [<ffffffff813ddf96>] __rpm_callback+0x36/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813de008>] rpm_callback+0x28/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813df340>] rpm_resume+0x490/0x690 Dec 15 21:03:44 metal kernel: [<ffffffff813df57f>] __pm_runtime_resume+0x3f/0x60 Dec 15 21:03:44 metal kernel: [<ffffffffa08b5037>] radeon_drm_ioctl+0x37/0x80 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff811e2b65>] do_vfs_ioctl+0x295/0x480 Dec 15 21:03:44 metal kernel: [<ffffffff811ecc67>] ? __fget+0x77/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff811e2dc9>] SyS_ioctl+0x79/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff8157626e>] entry_SYSCALL_64_fastpath+0x12/0x71 Dec 15 21:03:44 metal kernel: ---[ end trace 33afaf6a1bc49611 ]--- Dec 15 21:03:44 metal kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for dpm state Dec 15 21:03:44 metal kernel: ------------[ cut here ]------------ Dec 15 21:03:44 metal kernel: WARNING: CPU: 3 PID: 468 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x66/0x80() Dec 15 21:03:44 metal kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/power_dpm_force_performance_level' Dec 15 21:03:44 metal kernel: Modules linked in: cmac ecb rfcomm fuse bnep joydev mousedev mmc_block arc4 nls_iso8859_1 nls_cp437 vfat fat intel_rapl iwlmvm iosf_mbi x86_pkg_temp_thermal intel_powerclamp mac80211 kvm_intel snd_hda_codec_realtek Dec 15 21:03:44 metal kernel: toshiba_bluetooth mei_me intel_gtt soundcore i2c_algo_bit mei edac_core shpchp toshiba_haps wmi thermal rfkill button battery video ac processor sch_fq_codel nfs lockd grace sunrpc fscache ip_tables x_tables ext4 Dec 15 21:03:44 metal kernel: CPU: 3 PID: 468 Comm: Xorg Tainted: G W 4.2.5-1-ARCH #1 Dec 15 21:03:44 metal kernel: Hardware name: TOSHIBA SATELLITE P50-B-115/VG20SQ, BIOS 1.50 12/09/2014 Dec 15 21:03:44 metal kernel: 0000000000000000 00000000afbaeab0 ffff880317c67ac8 ffffffff81570d0a Dec 15 21:03:44 metal kernel: 0000000000000000 ffff880317c67b20 ffff880317c67b08 ffffffff810748a6 Dec 15 21:03:44 metal kernel: 0000623b17c67b08 ffff88025af5a000 ffffffffa09e1ba8 ffff880320822bb8 Dec 15 21:03:44 metal kernel: Call Trace: Dec 15 21:03:44 metal kernel: [<ffffffff81570d0a>] dump_stack+0x4c/0x6e Dec 15 21:03:44 metal kernel: [<ffffffff810748a6>] warn_slowpath_common+0x86/0xc0 Dec 15 21:03:44 metal kernel: [<ffffffff81074935>] warn_slowpath_fmt+0x55/0x70 Dec 15 21:03:44 metal kernel: [<ffffffff81245808>] ? kernfs_path+0x48/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff81248df6>] sysfs_warn_dup+0x66/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff81248b07>] sysfs_add_file_mode_ns+0x127/0x180 Dec 15 21:03:44 metal kernel: [<ffffffff81248b8a>] sysfs_create_file_ns+0x2a/0x30 Dec 15 21:03:44 metal kernel: [<ffffffff813cf532>] device_create_file+0x42/0x90 Dec 15 21:03:44 metal kernel: [<ffffffffa091b98d>] radeon_pm_late_init+0x8d/0x1a0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b7945>] radeon_resume_kms+0x255/0x3b0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b5143>] radeon_pmops_runtime_resume+0x73/0xb0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff812f9e6f>] pci_pm_runtime_resume+0x7f/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813cc759>] vga_switcheroo_runtime_resume+0x39/0x40 Dec 15 21:03:44 metal kernel: [<ffffffff813ddf96>] __rpm_callback+0x36/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813de008>] rpm_callback+0x28/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813df340>] rpm_resume+0x490/0x690 Dec 15 21:03:44 metal kernel: [<ffffffff813df57f>] __pm_runtime_resume+0x3f/0x60 Dec 15 21:03:44 metal kernel: [<ffffffffa08b5037>] radeon_drm_ioctl+0x37/0x80 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff811e2b65>] do_vfs_ioctl+0x295/0x480 Dec 15 21:03:44 metal kernel: [<ffffffff811ecc67>] ? __fget+0x77/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff811e2dc9>] SyS_ioctl+0x79/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff8157626e>] entry_SYSCALL_64_fastpath+0x12/0x71 Dec 15 21:03:44 metal kernel: ---[ end trace 33afaf6a1bc49612 ]--- Dec 15 21:03:44 metal kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for dpm state Dec 15 21:03:44 metal kernel: ------------[ cut here ]------------ Dec 15 21:03:44 metal kernel: WARNING: CPU: 3 PID: 468 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x66/0x80() Dec 15 21:03:44 metal kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/power_profile' Dec 15 21:03:44 metal kernel: Modules linked in: cmac ecb rfcomm fuse bnep joydev mousedev mmc_block arc4 nls_iso8859_1 nls_cp437 vfat fat intel_rapl iwlmvm iosf_mbi x86_pkg_temp_thermal intel_powerclamp mac80211 kvm_intel snd_hda_codec_realtek Dec 15 21:03:44 metal kernel: toshiba_bluetooth mei_me intel_gtt soundcore i2c_algo_bit mei edac_core shpchp toshiba_haps wmi thermal rfkill button battery video ac processor sch_fq_codel nfs lockd grace sunrpc fscache ip_tables x_tables ext4 Dec 15 21:03:44 metal kernel: CPU: 3 PID: 468 Comm: Xorg Tainted: G W 4.2.5-1-ARCH #1 Dec 15 21:03:44 metal kernel: Hardware name: TOSHIBA SATELLITE P50-B-115/VG20SQ, BIOS 1.50 12/09/2014 Dec 15 21:03:44 metal kernel: 0000000000000000 00000000afbaeab0 ffff880317c67ac8 ffffffff81570d0a Dec 15 21:03:44 metal kernel: 0000000000000000 ffff880317c67b20 ffff880317c67b08 ffffffff810748a6 Dec 15 21:03:44 metal kernel: 0000623b17c67b08 ffff88025af5a000 ffffffffa09ec5c5 ffff880320822bb8 Dec 15 21:03:44 metal kernel: Call Trace: Dec 15 21:03:44 metal kernel: [<ffffffff81570d0a>] dump_stack+0x4c/0x6e Dec 15 21:03:44 metal kernel: [<ffffffff810748a6>] warn_slowpath_common+0x86/0xc0 Dec 15 21:03:44 metal kernel: [<ffffffff81074935>] warn_slowpath_fmt+0x55/0x70 Dec 15 21:03:44 metal kernel: [<ffffffff81245808>] ? kernfs_path+0x48/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff81248df6>] sysfs_warn_dup+0x66/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff81248b07>] sysfs_add_file_mode_ns+0x127/0x180 Dec 15 21:03:44 metal kernel: [<ffffffff81248b8a>] sysfs_create_file_ns+0x2a/0x30 Dec 15 21:03:44 metal kernel: [<ffffffff813cf532>] device_create_file+0x42/0x90 Dec 15 21:03:44 metal kernel: [<ffffffffa091b9a4>] radeon_pm_late_init+0xa4/0x1a0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b7945>] radeon_resume_kms+0x255/0x3b0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b5143>] radeon_pmops_runtime_resume+0x73/0xb0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff812f9e6f>] pci_pm_runtime_resume+0x7f/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813cc759>] vga_switcheroo_runtime_resume+0x39/0x40 Dec 15 21:03:44 metal kernel: [<ffffffff813ddf96>] __rpm_callback+0x36/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813de008>] rpm_callback+0x28/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813df340>] rpm_resume+0x490/0x690 Dec 15 21:03:44 metal kernel: [<ffffffff813df57f>] __pm_runtime_resume+0x3f/0x60 Dec 15 21:03:44 metal kernel: [<ffffffffa08b5037>] radeon_drm_ioctl+0x37/0x80 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff811e2b65>] do_vfs_ioctl+0x295/0x480 Dec 15 21:03:44 metal kernel: [<ffffffff811ecc67>] ? __fget+0x77/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff811e2dc9>] SyS_ioctl+0x79/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff8157626e>] entry_SYSCALL_64_fastpath+0x12/0x71 Dec 15 21:03:44 metal kernel: ---[ end trace 33afaf6a1bc49613 ]--- Dec 15 21:03:44 metal kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for power profile Dec 15 21:03:44 metal kernel: ------------[ cut here ]------------ Dec 15 21:03:44 metal kernel: WARNING: CPU: 3 PID: 468 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x66/0x80() Dec 15 21:03:44 metal kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/power_method' Dec 15 21:03:44 metal kernel: Modules linked in: cmac ecb rfcomm fuse bnep joydev mousedev mmc_block arc4 nls_iso8859_1 nls_cp437 vfat fat intel_rapl iwlmvm iosf_mbi x86_pkg_temp_thermal intel_powerclamp mac80211 kvm_intel snd_hda_codec_realtek Dec 15 21:03:44 metal kernel: toshiba_bluetooth mei_me intel_gtt soundcore i2c_algo_bit mei edac_core shpchp toshiba_haps wmi thermal rfkill button battery video ac processor sch_fq_codel nfs lockd grace sunrpc fscache ip_tables x_tables ext4 Dec 15 21:03:44 metal kernel: CPU: 3 PID: 468 Comm: Xorg Tainted: G W 4.2.5-1-ARCH #1 Dec 15 21:03:44 metal kernel: Hardware name: TOSHIBA SATELLITE P50-B-115/VG20SQ, BIOS 1.50 12/09/2014 Dec 15 21:03:44 metal kernel: 0000000000000000 00000000afbaeab0 ffff880317c67ac8 ffffffff81570d0a Dec 15 21:03:44 metal kernel: 0000000000000000 ffff880317c67b20 ffff880317c67b08 ffffffff810748a6 Dec 15 21:03:44 metal kernel: 0000623b17c67b08 ffff88025af5a000 ffffffffa09ec5b8 ffff880320822bb8 Dec 15 21:03:44 metal kernel: Call Trace: Dec 15 21:03:44 metal kernel: [<ffffffff81570d0a>] dump_stack+0x4c/0x6e Dec 15 21:03:44 metal kernel: [<ffffffff810748a6>] warn_slowpath_common+0x86/0xc0 Dec 15 21:03:44 metal kernel: [<ffffffff81074935>] warn_slowpath_fmt+0x55/0x70 Dec 15 21:03:44 metal kernel: [<ffffffff81245808>] ? kernfs_path+0x48/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff81248df6>] sysfs_warn_dup+0x66/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff81248b07>] sysfs_add_file_mode_ns+0x127/0x180 Dec 15 21:03:44 metal kernel: [<ffffffff81248b8a>] sysfs_create_file_ns+0x2a/0x30 Dec 15 21:03:44 metal kernel: [<ffffffff813cf532>] device_create_file+0x42/0x90 Dec 15 21:03:44 metal kernel: [<ffffffffa091b9bb>] radeon_pm_late_init+0xbb/0x1a0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b7945>] radeon_resume_kms+0x255/0x3b0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffffa08b5143>] radeon_pmops_runtime_resume+0x73/0xb0 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff812f9e6f>] pci_pm_runtime_resume+0x7f/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813cc759>] vga_switcheroo_runtime_resume+0x39/0x40 Dec 15 21:03:44 metal kernel: [<ffffffff813ddf96>] __rpm_callback+0x36/0x80 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813de008>] rpm_callback+0x28/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff813cc720>] ? vga_switcheroo_runtime_suspend+0x60/0x60 Dec 15 21:03:44 metal kernel: [<ffffffff813df340>] rpm_resume+0x490/0x690 Dec 15 21:03:44 metal kernel: [<ffffffff813df57f>] __pm_runtime_resume+0x3f/0x60 Dec 15 21:03:44 metal kernel: [<ffffffffa08b5037>] radeon_drm_ioctl+0x37/0x80 [radeon] Dec 15 21:03:44 metal kernel: [<ffffffff811e2b65>] do_vfs_ioctl+0x295/0x480 Dec 15 21:03:44 metal kernel: [<ffffffff811ecc67>] ? __fget+0x77/0xb0 Dec 15 21:03:44 metal kernel: [<ffffffff811e2dc9>] SyS_ioctl+0x79/0x90 Dec 15 21:03:44 metal kernel: [<ffffffff8157626e>] entry_SYSCALL_64_fastpath+0x12/0x71 Dec 15 21:03:44 metal kernel: ---[ end trace 33afaf6a1bc49614 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2019