dri-devel July 2019

dri-devel@lists.freedesktop.org

323 participants
2301 discussions

[Bug 202043] New: amdgpu: Vega 56 SCLK drops to 700 Mhz when undervolting
by bugzilla-daemon＠bugzilla.kernel.org 08 Feb '21

08 Feb '21

https://bugzilla.kernel.org/show_bug.cgi?id=202043 Bug ID: 202043 Summary: amdgpu: Vega 56 SCLK drops to 700 Mhz when undervolting Product: Drivers Version: 2.5 Kernel Version: 4.19.8, 4.20.0-rc6 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: antifermion(a)protonmail.com Regression: No When undervolting my Sapphire Pulse Vega 56 by just 1mV, SCLK immediately drops down to 700 Mhz and pstate 1-2 under load (`gputest /test=fur /width=1920 /height=1080`). Script to undervolt: ``` echo "s 7 1630 1199" > /sys/class/drm/card0/device/pp_od_clk_voltage echo "c" > /sys/class/drm/card0/device/pp_od_clk_voltage ``` Stock voltage would be 1200 on the Vega 64 Bios. The same behavior can be observed with the stock Vega 56 Bios. Undervolting the memory by 1mV results in similar behavior. Overvolting by 1mV has no discernable effect. `echo r > pp_od_clk_voltage` does not work to go back to the normal behavior. Instead, I need to use `echo "s 7 1630 1200" > pp_od_clk_voltage` as above. Without undervolting, SCLK is around 1330 Mhz, which matches the behavior on Windows, where undervolting by around 150 mV is no problem and increases clock. With an increased power limit of 300W, the clocks increase to around 1100 Mhz while the card uses the full 300W. It even maxes that limit with a significant underclock/undervolt which would pull around 200W on Windows. I tested with current Manjaro (4.19.8-2-MANJARO), as well as Kubuntu 18.10 with stock (4.18) and 4.20 from https://github.com/M-Bab/linux-kernel-amdgpu-binaries. -- You are receiving this mail because: You are watching the assignee of the bug.

1 10

[PATCH v5 00/19] R-Car DU display writeback support
by Laurent Pinchart 16 Dec '20

16 Dec '20

Hello everybody, This patch series implements display writeback support for the R-Car Gen3 platforms in the VSP1 and DU drivers. Patches 01/19 to 11/19 prepare the VSP1 driver for writeback support with all the necessary plumbing, including extensions of the API between the VSP1 and DU drivers. Compared to v4 the major change is the move from V4L2 to DRM writeback connectors for the userspace API. This has caused a few issues with writeback support to be uncovered, and they are addressed by patches 12/19 to 14/19. Patch 15/19 is an unrelated drive-by fix. Patches 16/19 to 18/19 then perform refactoring of the DU driver, to finally add writeback support in patch 19/19. The writeback pixel format is restricted to RGB, due to the VSP1 outputting RGB to the display and lacking a separate colour space conversion unit for writeback. The resolution can be freely picked by will result in cropping or composing, not scaling. Writeback requests are queued to the hardware on page flip (atomic flush), and complete at the next vblank. This means that a queued writeback buffer will not be processed until the next page flip, but once it starts being written to by the VSP, it will complete at the next vblank regardless of whether another page flip occurs at that time. The code is based on a merge of the media master branch, the drm-next branch and the R-Car DT next branch. For convenience patches can be found at git://linuxtv.org/pinchartl/media.git v4l2/vsp1/writeback Kieran Bingham (1): Revert "[media] v4l: vsp1: Supply frames to the DU continuously" Laurent Pinchart (18): media: vsp1: wpf: Fix partition configuration for display pipelines media: vsp1: Replace leftover occurrence of fragment with body media: vsp1: Fix addresses of display-related registers for VSP-DL media: vsp1: Refactor vsp1_video_complete_buffer() for later reuse media: vsp1: Replace the display list internal flag with a flags field media: vsp1: dl: Support one-shot entries in the display list media: vsp1: wpf: Add writeback support media: vsp1: drm: Split RPF format setting to separate function media: vsp1: drm: Extend frame completion API to the DU driver media: vsp1: drm: Implement writeback support drm: writeback: Cleanup job ownership handling when queuing job drm: writeback: Fix leak of writeback job drm: writeback: Add job prepare and cleanup operations drm/msm: Remove prototypes for non-existing functions drm: rcar-du: Fix rcar_du_crtc structure documentation drm: rcar-du: Store V4L2 fourcc in rcar_du_format_info structure drm: rcar-du: vsp: Extract framebuffer (un)mapping to separate functions drm: rcar-du: Add writeback support for R-Car Gen3 drivers/gpu/drm/arm/malidp_mw.c | 3 +- drivers/gpu/drm/drm_atomic_helper.c | 11 ++ drivers/gpu/drm/drm_atomic_state_helper.c | 4 + drivers/gpu/drm/drm_atomic_uapi.c | 31 +-- drivers/gpu/drm/drm_writeback.c | 71 ++++++- drivers/gpu/drm/msm/msm_drv.h | 2 - drivers/gpu/drm/rcar-du/Kconfig | 4 + drivers/gpu/drm/rcar-du/Makefile | 3 +- drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 9 +- drivers/gpu/drm/rcar-du/rcar_du_kms.c | 37 ++++ drivers/gpu/drm/rcar-du/rcar_du_kms.h | 1 + drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 121 ++++++------ drivers/gpu/drm/rcar-du/rcar_du_vsp.h | 17 ++ drivers/gpu/drm/rcar-du/rcar_du_writeback.c | 203 ++++++++++++++++++++ drivers/gpu/drm/rcar-du/rcar_du_writeback.h | 39 ++++ drivers/gpu/drm/vc4/vc4_txp.c | 2 +- drivers/media/platform/vsp1/vsp1_dl.c | 127 ++++++++++-- drivers/media/platform/vsp1/vsp1_dl.h | 8 +- drivers/media/platform/vsp1/vsp1_drm.c | 92 ++++++--- drivers/media/platform/vsp1/vsp1_drm.h | 2 +- drivers/media/platform/vsp1/vsp1_drv.c | 15 ++ drivers/media/platform/vsp1/vsp1_pipe.c | 5 + drivers/media/platform/vsp1/vsp1_pipe.h | 1 + drivers/media/platform/vsp1/vsp1_regs.h | 6 +- drivers/media/platform/vsp1/vsp1_rwpf.h | 2 + drivers/media/platform/vsp1/vsp1_video.c | 49 +++-- drivers/media/platform/vsp1/vsp1_wpf.c | 68 +++++-- include/drm/drm_modeset_helper_vtables.h | 7 + include/drm/drm_writeback.h | 30 ++- include/media/vsp1.h | 19 +- 30 files changed, 790 insertions(+), 199 deletions(-) create mode 100644 drivers/gpu/drm/rcar-du/rcar_du_writeback.c create mode 100644 drivers/gpu/drm/rcar-du/rcar_du_writeback.h -- Regards, Laurent Pinchart

6 64

[Bug 201139] New: amdgpu: [drm] enabling link 1 failed: 15 (vega)
by bugzilla-daemon＠bugzilla.kernel.org 12 Dec '20

12 Dec '20

https://bugzilla.kernel.org/show_bug.cgi?id=201139 Bug ID: 201139 Summary: amdgpu: [drm] enabling link 1 failed: 15 (vega) Product: Drivers Version: 2.5 Kernel Version: 4.19-rc3 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: mezin.alexander(a)gmail.com Regression: No My setup: - RX Vega 64 - Arch Linux - GNOME 3.28.3 on Xorg 1.20.1 - modesetting Xorg driver - LG 27UD69P and Dell P2415Q I have "screen blanking" enabled in Gnome. Sometimes (very rarely) one display (Dell, connected to 2nd DisplayPort) doesn't wake up correctly. It turns on, shows only black screen, then quickly shows "no signal" message. In kernel log I see: [39215.008773] [drm] enabling link 1 failed: 15 If I manually turn the display off and on, it starts to work. Can't tell if it is a regression (hardly it is) because on 4.18 and earlier screen blanking just makes the driver hang: https://bugzilla.kernel.org/show_bug.cgi?id=200531 I've never seen a similar issue on Windows on the same machine. If I'm not mistaken, I've seen the same issue with Gnome on Wayland too (but I'm not sure). -- You are receiving this mail because: You are watching the assignee of the bug.

1 14

[Bug 94061] New: [radeon - Kaveri] dpm works badly - much to high power consumption compared to catalyst
by bugzilla-daemon＠bugzilla.kernel.org 03 Dec '20

03 Dec '20

https://bugzilla.kernel.org/show_bug.cgi?id=94061 Bug ID: 94061 Summary: [radeon - Kaveri] dpm works badly - much to high power consumption compared to catalyst Product: Drivers Version: 2.5 Kernel Version: 3.14.x ... 3.19. Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: abcdmail(a)freenet.de Regression: No With all kernel versions >= 3.14 (I didn't test versions below), radeon / dpm consumes about 6 W more compared to catalyst in idle mode (X-server 1.15 / 1.16) with Kaveri graphics (AMD A10-7800 Radeon R7). Idle mode: Xorg runs (KDE 4.11.x), screen saver off, static screen, load: 0.0 If the screen is turned off by X, the power consumption finally reaches the same level as with catalyst. It's raising immediately again at the moment the screen is switched on again by X. Seams the lowest rate is never reached as long as even a static screen has to be drawn - but it should! -- You are receiving this mail because: You are watching the assignee of the bug.

1 12

[Bug 78111] New: APU turbo core boost not working when radeon.dpm=1
by bugzilla-daemon＠bugzilla.kernel.org 03 Dec '20

03 Dec '20

https://bugzilla.kernel.org/show_bug.cgi?id=78111 Bug ID: 78111 Summary: APU turbo core boost not working when radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: 3.14.6 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: bgz.marko(a)gmail.com Regression: No I am testing with A6-1450 APU on Arch Linux. If I pass radeon.dpm=1 parameter at boot and start a single core workload then turbostat will report max frequency of about 1000 MHz: Core CPU Avg_MHz Bzy_MHz TSC_MHz time - - 262 998 998 5** 0 0 12 998 998 5** 1 1 998 998 998 2 2 16 998 998 3 3 21 998 998 "cpupower frequency-info" reports that boost state support is supported, but not active: boost state support: Supported: yes Active: no However, when dynamic power management is disabled (radeon.dpm=0), turbostat reports higher frequencies for single core load, up to 1300 Mhz: Core CPU Avg_MHz Bzy_MHz TSC_MHz time - - 320 1214 998 5** 0 0 9 1226 998 5** 1 1 13 1194 998 2 2 41 1143 998 3 3 1216 1216 998 "cpupower frequency-info" confirms that boost is now active. boost state support: Supported: yes Active: yes -- You are receiving this mail because: You are watching the assignee of the bug.

1 14

[Bug 201763] New: amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!
by bugzilla-daemon＠bugzilla.kernel.org 19 Nov '20

19 Nov '20

https://bugzilla.kernel.org/show_bug.cgi?id=201763 Bug ID: 201763 Summary: amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0! Product: Drivers Version: 2.5 Kernel Version: 4.18.10 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: rbrito(a)ime.usp.br Regression: No Dear developers, I have a notebook that is giving me a lot of trouble, especially as it is the newest computer that I have at my disposal where I can perform any actual work. This notebook has VERY frequent lockups (hard freezes, where the screen displays something where I am working, but the keyboard does not respond, the mouse doesn't either etc.). The only way that I can resume any work is by forcibly shutting it down (by pushing the power button for many seconds) and, of course, having all previous unsaved work lost (including a previous report of this bug with the bugzilla interface). :-( There is no particular pattern that I could discover so far that triggers the problem (for the past year, at least), but I do see some error messages on my dmesg logs and I would like start with some of the more salient points by sharing some problems that I have and, perhaps, zero in on potentially loose ends that may help everybody with hardware that is similar. The notebook in question is a Dell Inspiron 5548 with a Core i7-5500U, with two graphic cards (or so I am told), with one of them being integrated with the CPU and another being a discrete AMD GPU. The userspace that I am using is a Debian testing (soon to be Debian 10) with Debian's kernel 4.18.0-2-amd64 (which is actually a kernel 4.18.10-2). I can, of course, test any other kernels for the sake of getting things fixed. Just let me know and I will do my best to fix things. BTW, no kernel that I have ever used on this machine has every worked perfectly, even the prebuilt, unpatched kernels that Ubuntu compiles daily. With that being said, when the kernel boots up, there are some red messages on the dmesg log that are related to this AMD GPU (the entire dmesg log will be attached) with some prominent lines being: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ dmesg | grep -E -i "drm|amdgpu|i965" [ 13.054583] fb: switching to inteldrmfb from EFI VGA [ 13.059874] [drm] Replacing VGA console driver [ 13.060448] [drm] ACPI BIOS requests an excessive sleep of 10000 ms, using 1500 ms instead [ 13.061122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 13.061126] [drm] Driver supports precise vblank timestamp query. [ 13.067596] [drm] Initialized i915 1.6.0 20180514 for 0000:00:02.0 on minor 0 [ 13.071479] fbcon: inteldrmfb (fb0) is primary device [ 13.475640] [drm] amdgpu kernel modesetting enabled. [ 14.237446] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 14.238730] amdgpu 0000:04:00.0: enabling device (0100 -> 0103) [ 14.240876] [drm] initializing kernel modesetting (TOPAZ 0x1002:0x6900 0x1028:0x0643 0x00). [ 14.240888] [drm] register mmio base: 0xC2000000 [ 14.240888] [drm] register mmio size: 262144 [ 14.240898] [drm] probing gen 2 caps for device 8086:9c98 = 5323c42/0 [ 14.240899] [drm] probing mlw for device 8086:9c98 = 5323c42 [ 14.240901] [drm] add ip block number 0 <vi_common> [ 14.240901] [drm] add ip block number 1 <gmc_v7_0> [ 14.240902] [drm] add ip block number 2 <iceland_ih> [ 14.240902] [drm] add ip block number 3 <powerplay> [ 14.240903] [drm] add ip block number 4 <gfx_v8_0> [ 14.240904] [drm] add ip block number 5 <sdma_v2_4> [ 14.240905] amdgpu 0000:04:00.0: kfd not supported on this ASIC [ 14.262237] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 14.346850] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_mc.bin [ 14.347897] amdgpu 0000:04:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 14.348877] amdgpu 0000:04:00.0: GTT: 256M 0x0000000000000000 - 0x000000000FFFFFFF [ 14.350661] [drm] Detected VRAM RAM=2048M, BAR=256M [ 14.351494] [drm] RAM width 64bits DDR3 [ 14.358584] [drm] amdgpu: 2048M of VRAM memory ready [ 14.359442] [drm] amdgpu: 3072M of GTT memory ready. [ 14.360290] [drm] GART: num cpu pages 65536, num gpu pages 65536 [ 14.361807] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000). [ 14.363257] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 14.364522] [drm] Driver supports precise vblank timestamp query. [ 14.365629] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_pfp.bin [ 14.366113] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_me.bin [ 14.366262] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_ce.bin [ 14.366264] [drm] Chained IB support enabled! [ 14.366414] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_rlc.bin [ 14.381603] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_mec.bin [ 14.384759] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_sdma.bin [ 14.386476] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_sdma1.bin [ 14.461717] amdgpu 0000:04:00.0: firmware: direct-loading firmware amdgpu/topaz_smc.bin [ 14.465233] amdgpu: [powerplay] can't get the mac of 5 [ 14.467411] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0! [ 14.477284] [drm] Initialized amdgpu 3.26.0 20150101 for 0000:04:00.0 on minor 1 [ 21.824595] amdgpu: [powerplay] VI should always have 2 performance levels [ 21.871775] amdgpu 0000:04:00.0: GPU pci config reset [ 22.574755] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000). [ 22.577374] amdgpu: [powerplay] can't get the mac of 5 [ 22.578782] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0! [ 29.802702] amdgpu: [powerplay] VI should always have 2 performance levels [ 29.848230] amdgpu 0000:04:00.0: GPU pci config reset - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Well, that's it. Please let me know whatever information you want me to get and I will post it here. Reiterating: I can compile kernels and or run other programs to diagnose anything that you want me to to fix these issues. Thanks in advance, Rogério Brito. -- You are receiving this mail because: You are watching the assignee of the bug.

1 13

[Bug 203339] New: AMDGPU: virtual_display disables physical outputs
by bugzilla-daemon＠bugzilla.kernel.org 21 Oct '20

21 Oct '20

https://bugzilla.kernel.org/show_bug.cgi?id=203339 Bug ID: 203339 Summary: AMDGPU: virtual_display disables physical outputs Product: Drivers Version: 2.5 Kernel Version: 5.0.7 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: parker.l.reed(a)gmail.com Regression: No Created attachment 282351 --> https://bugzilla.kernel.org/attachment.cgi?id=282351&action=edit Kernel log Unable to tell if this is intended or if caused by a crash. I have a monitor connected via HDMI. When I use the virtual_display kernel parameter, only the virtual displays show up. amdgpu.virtual_display=0000:07:00.0,2 Original patchset doesn't mention this usecase. https://lists.freedesktop.org/archives/amd-gfx/2016-August/001058.html Kernel log attached shows some crashes related to dce_virtual_crtc -- You are receiving this mail because: You are watching the assignee of the bug.

1 5

[Bug 203471] New: Tearing on Raven Ridge and RX560X PRIME setup even with Vsync enabled
by bugzilla-daemon＠bugzilla.kernel.org 16 Oct '20

16 Oct '20

https://bugzilla.kernel.org/show_bug.cgi?id=203471 Bug ID: 203471 Summary: Tearing on Raven Ridge and RX560X PRIME setup even with Vsync enabled Product: Drivers Version: 2.5 Kernel Version: 5.1 rc6 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: haxk612(a)gmail.com Regression: No I have Acer Nitro 5 AN515-42 with Ryzen 5 2500U and RX560X. When i launch some game with DRI_PRIME=1 to have it on dGPU there is huge tearing on top of the screen that is there with or without Vsync. If i launch the game on iGPU there is no tearing at all. Also the tearing happens only when the game is in fullscreen. If i take a screenshot there is no tearing in the screenshot. And i cannot post a picture as my phone camera is broken in my latest build of android. I have tried 5.2-wip branch and there is the same issue. Will post dmesg and journalctl in few hours. -- You are receiving this mail because: You are watching the assignee of the bug.

1 26

[Bug 199979] New: amdgpu: changing pwm1_enable from 1 to 2 does not resume automatic fan control
by bugzilla-daemon＠bugzilla.kernel.org 06 Oct '20

06 Oct '20

https://bugzilla.kernel.org/show_bug.cgi?id=199979 Bug ID: 199979 Summary: amdgpu: changing pwm1_enable from 1 to 2 does not resume automatic fan control Product: Drivers Version: 2.5 Kernel Version: 4.17.0 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: CWidmer(a)umbrox.de Regression: No When using the hardware monitoring interface to change pwm1_enable to 2 (automatic) from 1 (manual), the automatic fan control does not work as expected. Instead, the pwm1 value keeps jumping around between at least two values and a continuous, persisting, and unpleasantly high-pitched sound can be heard from inside the computer case. The only way to stop those things is writing some valid value to pwm1, which in turn also switches pwm1_enable back to 1. If the system is booted without ever manually changing the pwm1_enable value, which then defaults to 2, automatic fan control does work as intended. I am using a custom RX 580 (Sapphire Nitro+ Radeon RX 580 8GD5 Special Edition) on a Gentoo x86_64 system and was able to reproduce the issue with the 4.17.0 kernel with Gentoo patches, the Ubuntu kernel on the 18.04 image (should be a 4.15 one) and also with amd-staging-drm-next. -- You are receiving this mail because: You are watching the assignee of the bug.

1 1

[Bug 198551] New: amdgpu error on shutdown or gpu intense game
by bugzilla-daemon＠bugzilla.kernel.org 24 Sep '20

24 Sep '20

https://bugzilla.kernel.org/show_bug.cgi?id=198551 Bug ID: 198551 Summary: amdgpu error on shutdown or gpu intense game Product: Drivers Version: 2.5 Kernel Version: 4.14.14-1 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: illuslion1998(a)gmail.com Regression: No Created attachment 273797 --> https://bugzilla.kernel.org/attachment.cgi?id=273797&action=edit amdgpu error log I get this error sometimes when I try to shutdown my computer. It freezes everything and I have to hard reset my computer. This sometimes also happens when I play a GPU intense game. (Example CS:GO). My GPU is Radeon R5 M255. -- You are receiving this mail because: You are watching the assignee of the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2019