dri-devel July 2021

dri-devel@lists.freedesktop.org

321 participants
829 discussions

[PARCH v2 0/7] drm/msm/dpu: merge dpu_core_irq into dpu_hw_interrupts
by Dmitry Baryshkov 01 Feb '22

01 Feb '22

This patch series reworks DPU's irq handling code by merging dpu_core_irq into dpu_hw_intr, reworking/dropping irq-related helpers and wrappers, etc. Changes since v1: - Rework callbacks registration code to allow just single callback per interrupt. This removes need to do any memory allocation in reg/unreg code and simplifies handling of interrupts. The following changes since commit 7e0230fd096c03e9662e66150f951075dd16e496: drm/msm/mdp5: provide dynamic bandwidth management (2021-06-17 09:51:44 -0700) are available in the Git repository at: https://git.linaro.org/people/dmitry.baryshkov/kernel.git dpu-irq-simplify-5 for you to fetch changes up to b2ae835c61b2065037c55b4596e16053484f4904: drm/msm/dpu: remove struct dpu_encoder_irq and enum dpu_intr_idx (2021-06-18 01:12:04 +0300) ---------------------------------------------------------------- Dmitry Baryshkov (7): drm/msm/dpu: squash dpu_core_irq into dpu_hw_interrupts drm/msm/dpu: don't clear IRQ register twice drm/msm/dpu: merge struct dpu_irq into struct dpu_hw_intr drm/msm/dpu: allow just single IRQ callback drm/msm/dpu: remove extra wrappers around dpu_core_irq drm/msm/dpu: get rid of dpu_encoder_helper_(un)register_irq drm/msm/dpu: remove struct dpu_encoder_irq and enum dpu_intr_idx drivers/gpu/drm/msm/Makefile | 1 - drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.c | 256 -------------------- drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.h | 30 ++- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 111 ++------- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys.h | 66 +----- .../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c | 99 ++++---- .../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 56 ++--- drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.c | 264 +++++++++++++++------ drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.h | 96 +------- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 27 +-- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 25 -- drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 51 ++-- 12 files changed, 334 insertions(+), 748 deletions(-) delete mode 100644 drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.c

2 16

[Bug 204611] New: amdgpu error scheduling IBs when waking from sleep
by bugzilla-daemon＠bugzilla.kernel.org 30 Jan '22

30 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=204611 Bug ID: 204611 Summary: amdgpu error scheduling IBs when waking from sleep Product: Drivers Version: 2.5 Kernel Version: 5.2.9 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: tones111(a)hotmail.com Regression: No Created attachment 284485 --> https://bugzilla.kernel.org/attachment.cgi?id=284485&action=edit journalctl: amdgpu lockup on resume from sleep. My system locks up when trying to wake from sleep (open lid). The screen remains black and is unresponsive to keyboard/mouse input. I'm able to ssh from another machine and have attached the output from journalctl -b. The log shows scrolling errors... kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <gfx> This is a Lenovo E585 laptop with an AMD R5 2500U APU. -- You are receiving this mail because: You are watching the assignee of the bug.

2 15

[PATCH v3] drm/ast: Don't check new mode if CRTC is being disabled
by Thomas Zimmermann 24 Jan '22

24 Jan '22

Suspending failed because there's no mode if the CRTC is being disabled. Early-out in this case. This fixes runtime PM for ast. v3: * fixed commit message v2: * added Tested-by/Reported-by tags * added Fixes tags and CC (Sam) * improved comment Signed-off-by: Thomas Zimmermann <tzimmermann(a)suse.de> Reported-by: Cary Garrett <cogarre(a)gmail.com> Tested-by: Cary Garrett <cogarre(a)gmail.com> Fixes: b48e1b6ffd28 ("drm/ast: Add CRTC helpers for atomic modesetting") Cc: Thomas Zimmermann <tzimmermann(a)suse.de> Cc: Gerd Hoffmann <kraxel(a)redhat.com> Cc: Dave Airlie <airlied(a)redhat.com> Cc: Daniel Vetter <daniel.vetter(a)ffwll.ch> Cc: Sam Ravnborg <sam(a)ravnborg.org> Cc: <stable(a)vger.kernel.org> # v5.6+ --- drivers/gpu/drm/ast/ast_mode.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c index 7a9f20a2fd303..0cbbb21edb4e1 100644 --- a/drivers/gpu/drm/ast/ast_mode.c +++ b/drivers/gpu/drm/ast/ast_mode.c @@ -801,6 +801,9 @@ static int ast_crtc_helper_atomic_check(struct drm_crtc *crtc, return -EINVAL; } + if (!state->enable) + return 0; /* no mode checks if CRTC is being disabled */ + ast_state = to_ast_crtc_state(state); format = ast_state->format; -- 2.26.0

3 3

[Bug 211277] New: sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu, drm, commit_tail, amdgpu_dm_atomic_commit_tail
by bugzilla-daemon＠bugzilla.kernel.org 23 Jan '22

23 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=211277 Bug ID: 211277 Summary: sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu, drm, commit_tail, amdgpu_dm_atomic_commit_tail Product: Drivers Version: 2.5 Kernel Version: 5.10.4 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: kolAflash(a)kolahilft.de Regression: No I'm currently on Debian-11-Testing (Bullseye). And since a few weeks the system sometimes (not always) doesn't wake up from suspend. Most of the time suspend works. But about 1 in 10 times it crashes. I attached /var/log/kern.log which holds plenty of information about the crash. Looks like the crash happened in amdgpu_dm.c:7273 (amdgpu_dm_atomic_commit_tail, Linux-5.10.4). I'm pretty sure this behavior didn't appeared a few month before. So I guess a recent change is causing it. This may either be: 1. an updated package by Debian-Testing Indeed I'm pretty sure the problem didn't appeared before Linux-5.9. So maybe this is being caused by a change between Linux-5.8 and Linux-5.9. I'll try to test going back to Linux-5.8 in the next days. 2. a BIOS update In November 2020 I installed the BIOS update sp110770.exe. Before I was using sp107599.exe. You can find the BIOS history attached. I'll also see if I can test a BIOS downgrade in the next days. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 86

[PATCH 0/6] drm/meson: add support for AXG & MIPI-DSI
by Neil Armstrong 20 Jan '22

20 Jan '22

The Amlogic AXG SoC family has a downgraded VPU with the following changes : - Only a single OSD plane, no overlay video plane - The primary plane doesn't support HW scaling - The pixels are read directly from DDR without any Canvas module - Doesn't support HDMI or CVBS - Ouputs only with ENCL encoder to a DPI-to-DSI Synopsys DW-MIPI-DSI transceiver The Amlogic AXg SoCs embeds a Synopsys DW-MIPI-DSI transceiver (ver 1.21a), with a custom glue managing the IP resets, clock and data input similar to the DW-HDMI Glue on other Amlogic SoCs. This adds support for the Glue managing the transceiver, mimicing the init flow provided by Amlogic to setup the ENCl encoder, the glue, the transceiver, the digital D-PHY and the Analog PHY in the proper way. The DW-MIPI-DSI transceiver + D-PHY are directly clocked by the VCLK2 clock, which pixel clock is derived and feeds the ENCL encoder and the VIU pixel reader. An optional "MEAS" clock can be enabled to measure the delay between each vsync feeding the DW-MIPI-DSI transceiver. Neil Armstrong (6): dt-bindings: display: amlogic,meson-vpu: add bindings for VPU found in AXG SoCs dt-bindings: display: add Amlogic MIPI DSI Host Controller bindings drm/meson: add support for VPU found in AXG SoCs drm/meson: venc: add ENCL encoder setup for MIPI-DSI output drm/meson: remove useless recursive components matching drm/meson: add support for MIPI-DSI transceiver .../display/amlogic,meson-dw-mipi-dsi.yaml | 115 ++++ .../bindings/display/amlogic,meson-vpu.yaml | 36 +- drivers/gpu/drm/meson/Kconfig | 7 + drivers/gpu/drm/meson/Makefile | 1 + drivers/gpu/drm/meson/meson_crtc.c | 8 +- drivers/gpu/drm/meson/meson_drv.c | 163 ++--- drivers/gpu/drm/meson/meson_drv.h | 10 +- drivers/gpu/drm/meson/meson_dw_mipi_dsi.c | 562 ++++++++++++++++++ drivers/gpu/drm/meson/meson_plane.c | 74 ++- drivers/gpu/drm/meson/meson_registers.h | 1 + drivers/gpu/drm/meson/meson_venc.c | 230 ++++++- drivers/gpu/drm/meson/meson_venc.h | 6 + drivers/gpu/drm/meson/meson_viu.c | 50 +- drivers/gpu/drm/meson/meson_vpp.c | 6 +- drivers/gpu/drm/meson/meson_vpp.h | 2 + 15 files changed, 1176 insertions(+), 95 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/amlogic,meson-dw-mipi-dsi.yaml create mode 100644 drivers/gpu/drm/meson/meson_dw_mipi_dsi.c -- 2.22.0

4 21

[Bug 213561] New: [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3
by bugzilla-daemon＠bugzilla.kernel.org 20 Jan '22

20 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=213561 Bug ID: 213561 Summary: [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 Product: Drivers Version: 2.5 Kernel Version: 5.13rc7 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: untaintableangel(a)hotmail.co.uk Regression: No Nature of the problem: RX 5700 is unable to enter low power state at idle (see below for usual behaviour) Sensors at idle prior to the commit: amdgpu-pci-0f00 Adapter: PCI adapter vddgfx: 775.00 mV fan1: 0 RPM (min = 0 RPM, max = 3200 RPM) edge: +48.0°C (crit = +100.0°C, hyst = -273.1°C) (emerg = +105.0°C) junction: +48.0°C (crit = +110.0°C, hyst = -273.1°C) (emerg = +115.0°C) mem: +52.0°C (crit = +105.0°C, hyst = -273.1°C) (emerg = +110.0°C) power1: 8.00 W (cap = 165.00 W) After the commit, the lowest is: amdgpu-pci-0f00 Adapter: PCI adapter vddgfx: 1.03 V fan1: 0 RPM (min = 0 RPM, max = 3200 RPM) edge: +54.0°C (crit = +100.0°C, hyst = -273.1°C) (emerg = +105.0°C) junction: +56.0°C (crit = +110.0°C, hyst = -273.1°C) (emerg = +115.0°C) mem: +52.0°C (crit = +105.0°C, hyst = -273.1°C) (emerg = +110.0°C) power1: 31.00 W (cap = 165.00 W) This problem wasn't present in rc6 but is present in 5.13rc7 and bisects to: 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 is the first bad commit commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 Author: Yifan Zhang <yifan1.zhang(a)amd.com> Date: Thu Jun 10 10:10:07 2021 +0800 drm/amdgpu/gfx10: enlarge CP_MEC_DOORBELL_RANGE_UPPER to cover full doorbell. If GC has entered CGPG, ringing doorbell > first page doesn't wakeup GC. Enlarge CP_MEC_DOORBELL_RANGE_UPPER to workaround this issue. Signed-off-by: Yifan Zhang <yifan1.zhang(a)amd.com> Reviewed-by: Felix Kuehling <Felix.Kuehling(a)amd.com> Reviewed-by: Alex Deucher <alexander.deucher(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org The device is a Sapphire Pulse RX5700 and this problem is seen even with one monitor set at 60Hz. GPU: 0f:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.

1 20

[Bug 204559] New: amdgpu: kernel oops with constant gpu resets while using mpv
by bugzilla-daemon＠bugzilla.kernel.org 17 Jan '22

17 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=204559 Bug ID: 204559 Summary: amdgpu: kernel oops with constant gpu resets while using mpv Product: Drivers Version: 2.5 Kernel Version: 5.2.7 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: shoegaze(a)tutanota.com Regression: No Created attachment 284335 --> https://bugzilla.kernel.org/attachment.cgi?id=284335&action=edit oops.txt While watching a video using mpv (default config) the system will hang eventually - this is actually a kernel oops that happens after lots of GPU resets every second or so (in the span of ~5 minutes; it seems to be alright in the beginning): > Aug 12 00:46:49 mashedpotato kernel: [drm] UVD and UVD ENC initialized > successfully. > Aug 12 00:46:49 mashedpotato kernel: [drm] VCE initialized successfully. > Aug 12 00:46:56 mashedpotato kernel: amdgpu 0000:01:00.0: GPU pci config > reset > Aug 12 00:46:59 mashedpotato kernel: [drm] PCIE GART of 256M enabled (table > at 0x000000F400000000). This block of warnings repeats itself many times and then it is this error: > Aug 12 00:52:20 mashedpotato kernel: amdgpu 0000:01:00.0: > [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110) > Aug 12 00:52:20 mashedpotato kernel: [drm:amdgpu_device_resume [amdgpu]] > *ERROR* resume of IP block <sdma_v3_0> failed -110 > Aug 12 00:52:20 mashedpotato kernel: [drm:amdgpu_device_resume [amdgpu]] > *ERROR* amdgpu_device_ip_resume failed (-110). > Aug 12 00:52:25 mashedpotato kernel: BUG: kernel NULL pointer dereference, > address: 0000000000000000 > Aug 12 00:52:25 mashedpotato kernel: #PF: supervisor instruction fetch in > kernel mode > Aug 12 00:52:25 mashedpotato kernel: #PF: error_code(0x0010) - not-present > page In the end it is a kernel oops, log is in the attachment. The system is only recoverable via a hard reset afterwards, though the sound from a video keeps playing just fine. My system is a ASUS laptop, TUF FX505-DY with the latest BIOS. lspci: > 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root > Complex > 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU > 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 00h-1fh) PCIe Dummy Host Bridge > 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:01.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP > Bridge [6:0] > 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 00h-1fh) PCIe Dummy Host Bridge > 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal > PCIe GPP Bridge 0 to Bus A > 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev > 61) > 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev > 51) > 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 0 > 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 1 > 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 2 > 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 3 > 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 4 > 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 5 > 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 6 > 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device > 24: Function 7 > 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin > [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev e5) > 02:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. > Device 5008 (rev 01) > 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE > 802.11ac PCIe Wireless Network Adapter > 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) > 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Picasso (rev c2) > 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > Raven/Raven2/Fenghuang HDMI/DP Audio Controller > 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h > (Models 10h-1fh) Platform Security Processor > 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 > 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 > 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models > 10h-1fh) HD Audio Controller I have amdgpu.gpu_reset=1 in my kernel commandline as I want to figure out another issue - sometimes the system hangs after locking and disabling screen, and I guess it is GPU reset-related. -- You are receiving this mail because: You are watching the assignee of the bug.

1 15

[Bug 210263] New: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet"
by bugzilla-daemon＠bugzilla.kernel.org 12 Jan '22

12 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=210263 Bug ID: 210263 Summary: brightness device returns ENXIO (?) on brightness restore at boot, with bootoption "quiet" Product: Drivers Version: 2.5 Kernel Version: 5.9.8 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: plusfabi(a)gmail.com Regression: No Created attachment 293729 --> https://bugzilla.kernel.org/attachment.cgi?id=293729&action=edit dmesg Following: https://github.com/systemd/systemd/issues/17645 If I set kernel boot option "quiet", systemd fails to restore brightness level with error Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. At boot. full journal output is: journalctl -b -1 -u systemd-backlight@backlight:amdgpu_bl0.service -- Logs begin at Thu 2020-09-17 08:15:00 CEST, end at Tue 2020-11-17 14:19:18 CET. -- Nov 17 14:15:15 frigg systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0... Nov 17 14:15:15 frigg systemd-backlight[325]: amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Nov 17 14:15:15 frigg systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, code=exited, status=1/FAILURE Nov 17 14:15:15 frigg systemd[1]: systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'. Nov 17 14:15:15 frigg systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. This is an AMD Renoir system, with AMD Ryzen 5 4500U APU, This happens only, if I set 'quiet' as boot option. If I remove it, brightness restore works fine. If I boot with quiet set, after login I can do systemctl start systemd-backlight@backlight:amdgpu_bl0.service And it will successfully restore my brightness level. -- You are receiving this mail because: You are watching the assignee of the bug.

1 8

[PATCH 1/3] drm/dp/mst: Handle errors from drm_atomic_get_private_obj_state() correctly
by ville.syrjala＠linux.intel.com 12 Jan '22

12 Jan '22

From: Ville Syrjälä <ville.syrjala(a)linux.intel.com> On failure drm_atomic_get_private_obj_state() returns and error pointer instead of NULL. Adjust the checks in the callers to match. Cc: stable(a)vger.kernel.org Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan(a)intel.com> Cc: Harry Wentland <harry.wentland(a)amd.com> Cc: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> Fixes: edb1ed1ab7d3 ("drm/dp: Add DP MST helpers to atomically find and release vcpi slots") Signed-off-by: Ville Syrjälä <ville.syrjala(a)linux.intel.com> --- drivers/gpu/drm/drm_dp_mst_topology.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c index bfd237c15e76..18cecd94acb6 100644 --- a/drivers/gpu/drm/drm_dp_mst_topology.c +++ b/drivers/gpu/drm/drm_dp_mst_topology.c @@ -2515,8 +2515,8 @@ int drm_dp_atomic_find_vcpi_slots(struct drm_atomic_state *state, int req_slots; topology_state = drm_atomic_get_mst_topology_state(state, mgr); - if (topology_state == NULL) - return -ENOMEM; + if (IS_ERR(topology_state)) + return PTR_ERR(topology_state); port = drm_dp_get_validated_port_ref(mgr, port); if (port == NULL) @@ -2555,8 +2555,8 @@ int drm_dp_atomic_release_vcpi_slots(struct drm_atomic_state *state, struct drm_dp_mst_topology_state *topology_state; topology_state = drm_atomic_get_mst_topology_state(state, mgr); - if (topology_state == NULL) - return -ENOMEM; + if (IS_ERR(topology_state)) + return PTR_ERR(topology_state); /* We cannot rely on port->vcpi.num_slots to update * topology_state->avail_slots as the port may not exist if the parent -- 2.13.0

4 7

[Bug 206475] New: amdgpu under load drop signal to monitor until hard reset
by bugzilla-daemon＠bugzilla.kernel.org 06 Jan '22

06 Jan '22

https://bugzilla.kernel.org/show_bug.cgi?id=206475 Bug ID: 206475 Summary: amdgpu under load drop signal to monitor until hard reset Product: Drivers Version: 2.5 Kernel Version: 5.5.2 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: rodomar705(a)protonmail.com Regression: No Created attachment 287265 --> https://bugzilla.kernel.org/attachment.cgi?id=287265&action=edit dmesg for the amdgpu hardware freeze While gaming the monitor goes blank randomly, only with this error in the logs of the system kernel: amdgpu: [powerplay] last message was failed ret is 65535 kernel: amdgpu: [powerplay] failed to send message 200 ret is 65535 kernel: amdgpu: [powerplay] last message was failed ret is 65535 kernel: amdgpu: [powerplay] failed to send message 282 ret is 65535 kernel: amdgpu: [powerplay] last message was failed ret is 65535 kernel: amdgpu: [powerplay] failed to send message 201 ret is 65535 with the occasional kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=5275264, emitted seq=5275266 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Hand of Fate 2. pid 682062 thread Hand of Fa:cs0 pid 682064 kernel: amdgpu 0000:06:00.0: GPU reset begin! over and over again. If I reset the system no video output is seen until the system is fully shut off. B450 chipset + Ryzen 5 2600 + Radeon RX580 GPU Full log is attached to this post. Can anyone at AMD give me some pointers to what the problem is? Thanks, Marco. -- You are receiving this mail because: You are watching the assignee of the bug.

1 22

← Newer
1
2
3
4
5
6
7
...
83
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2021