On 7/18/25 8:03 PM, Lauri Tirkkonen wrote:
On Fri, Jul 18 2025 12:13:30 -0500, Mario Limonciello wrote:
On 7/18/2025 9:36 AM, Lauri Tirkkonen wrote:
On Fri, Jul 18 2025 08:10:06 -0500, Mario Limonciello wrote:
Do you by chance have an OLED panel? I believe what's going on is that
userspace
From: Mario Limonciello
During the 2025 Display Next Hackfest the topic from the 2024 display
next hackfest about what to do with adaptive backlight modulation was
revisited.
The general consensus was that the 2024 proposed solution [1] although
functional was not desirable because it was a bina
On 2025-07-18 17:33, Alex Deucher wrote:
> On Fri, Jul 18, 2025 at 5:02 PM Leo Li wrote:
>>
>>
>>
>> On 2025-07-18 16:07, Alex Deucher wrote:
>>> On Fri, Jul 18, 2025 at 1:57 PM Brian Geffon wrote:
On Thu, Jul 17, 2025 at 10:59 AM Alex Deucher
wrote:
>
> On Wed, Jul 16
On 2025-07-14 08:46, James Zhu wrote:
dst MIGRATE_PFN_VALID bit and src MIGRATE_PFN_MIGRATE bit
should always be set when migration success. cpage includes
src MIGRATE_PFN_MIGRATE bit set and MIGRATE_PFN_VALID bit
unset pages for both ram and vram when memory is only allocated
without access befo
On 2025-07-18 12:09, Sunday Clement wrote:
For security reasons it is safer to have the kernel driver handle
calculating the sizing for the control stack on queue creation for
gfx9, rather than having it done in userspace where arbitrarily large
values can be passed in potentially wasting space i
On 2025-07-18 16:07, Alex Deucher wrote:
> On Fri, Jul 18, 2025 at 1:57 PM Brian Geffon wrote:
>>
>> On Thu, Jul 17, 2025 at 10:59 AM Alex Deucher wrote:
>>>
>>> On Wed, Jul 16, 2025 at 8:13 PM Brian Geffon wrote:
On Wed, Jul 16, 2025 at 5:03 PM Alex Deucher wrote:
>
> On W
On Fri, Jul 18, 2025 at 6:01 PM Leo Li wrote:
>
>
>
> On 2025-07-18 17:33, Alex Deucher wrote:
> > On Fri, Jul 18, 2025 at 5:02 PM Leo Li wrote:
> >>
> >>
> >>
> >> On 2025-07-18 16:07, Alex Deucher wrote:
> >>> On Fri, Jul 18, 2025 at 1:57 PM Brian Geffon wrote:
>
> On Thu, Jul 17, 20
On Fri, Jul 18, 2025 at 1:57 PM Brian Geffon wrote:
>
> On Thu, Jul 17, 2025 at 10:59 AM Alex Deucher wrote:
> >
> > On Wed, Jul 16, 2025 at 8:13 PM Brian Geffon wrote:
> > >
> > > On Wed, Jul 16, 2025 at 5:03 PM Alex Deucher
> > > wrote:
> > > >
> > > > On Wed, Jul 16, 2025 at 12:40 PM Brian
thanks!
Tested-by: David (Ming Qiang) Wu
Reviewed-by: David (Ming Qiang) Wu
On 7/18/2025 3:57 PM, Alex Deucher wrote:
Update the client id mapping so the correct clients
get printed when there is a mmhub page fault.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/mmhub_v4_1_0.c
On Fri, Jul 18, 2025 at 5:02 PM Leo Li wrote:
>
>
>
> On 2025-07-18 16:07, Alex Deucher wrote:
> > On Fri, Jul 18, 2025 at 1:57 PM Brian Geffon wrote:
> >>
> >> On Thu, Jul 17, 2025 at 10:59 AM Alex Deucher
> >> wrote:
> >>>
> >>> On Wed, Jul 16, 2025 at 8:13 PM Brian Geffon wrote:
>
> >>
Melisa,
The following NULL pointer error was reported from promotion test with
this patch:
[ 31.525028] amdgpu :c4:00.0: [drm] *ERROR* No EDID read.
[ 31.525596] amdgpu :c4:00.0: [drm:drm_dp_dpcd_read
[drm_display_helper]] AMDGPU DM aux hw bus 2: 0x6921d AUX -> (ret= 3)
00 00 0
Update the client id mapping so the correct clients
get printed when there is a mmhub page fault.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/mmhub_v3_3.c | 104 +++-
1 file changed, 103 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/mmhu
Update the client id mapping so the correct clients
get printed when there is a mmhub page fault.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/mmhub_v4_1_0.c | 34 +--
1 file changed, 13 insertions(+), 21 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/mmh
Update the client id mapping so the correct clients
get printed when there is a mmhub page fault.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/mmhub_v3_0_1.c | 57 +--
1 file changed, 32 insertions(+), 25 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/mmh
From: Mario Limonciello
commit 0887054d14ae2 ("drm/amd: Drop abm_level property") dropped the
abm level property in favor of sysfs control. Since then there have
been discussions that compositors showed an interest in modifying
a vendor specific property instead.
So re-introduce the abm level pr
On 16/07/2025 21:44, Maíra Canal wrote:
Hi Tvrtko,
On 16/07/25 11:46, Tvrtko Ursulin wrote:
On 16/07/2025 15:30, Maíra Canal wrote:
Hi Tvrtko,
On 16/07/25 10:49, Tvrtko Ursulin wrote:
On 16/07/2025 14:31, Maíra Canal wrote:
Hi Tvrtko,
On 16/07/25 05:51, Tvrtko Ursulin wrote:
Currently
On Thu, Jul 17, 2025 at 12:43 PM Melissa Wen wrote:
>
>
>
> On 17/07/2025 16:28, Matthew Schwartz wrote:
> > On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote:
> >> On 17-07-2025 17:57, Matthew Schwartz wrote:
> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario
> wrote:
>
> O
On 18/07/2025 10:31, Philipp Stanner wrote:
On Fri, 2025-07-18 at 08:13 +0100, Tvrtko Ursulin wrote:
On 16/07/2025 21:44, Maíra Canal wrote:
Hi Tvrtko,
On 16/07/25 11:46, Tvrtko Ursulin wrote:
On 16/07/2025 15:30, Maíra Canal wrote:
Hi Tvrtko,
On 16/07/25 10:49, Tvrtko Ursulin wrote:
[Public]
What if when the kernel queue and user queue are enabled at the same time,
then how to handle the case when userq mapped to a queue that has been
enabled privileged bit by kernel queue?
Regards,
Prike
> -Original Message-
> From: amd-gfx On Behalf Of Lazar, Lijo
> Sent: F
On 18/07/2025 10:41, Philipp Stanner wrote:
On Fri, 2025-07-18 at 10:35 +0100, Tvrtko Ursulin wrote:
On 18/07/2025 10:31, Philipp Stanner wrote:
On Fri, 2025-07-18 at 08:13 +0100, Tvrtko Ursulin wrote:
On 16/07/2025 21:44, Maíra Canal wrote:
Hi Tvrtko,
On 16/07/25 11:46, Tvrtko Ursulin w
On 7/18/25 2:29 AM, Lauri Tirkkonen wrote:
Hi,
I hit this regression on the stable kernel on Alpine with a Lenovo Yoga
Slim 7 Pro 17ACH5. During early boot, when the amdgpu module gets
loaded, backlight brightness is set to zero, resulting in a black
screen (and nothing in userspace is runnin
On 18-07-2025 00:51, Matthew Schwartz wrote:
[...]
>
> Sure, going to use my Legion Go S w/ Z2 Go for this (DCN 3.1.2). All
> of these are from amd-staging-drm-next with AMD_PRIVATE_COLOR=y.
>
> DTN log from Hades II with MangoHud enabled:
> https://gist.github.com/matte-schwartz/0c290ffe99bdb4f0
Hi,
I hit this regression on the stable kernel on Alpine with a Lenovo Yoga
Slim 7 Pro 17ACH5. During early boot, when the amdgpu module gets
loaded, backlight brightness is set to zero, resulting in a black
screen (and nothing in userspace is running yet to handle brightness
keys; I need to use a
On Fri, 2025-07-18 at 08:13 +0100, Tvrtko Ursulin wrote:
>
> On 16/07/2025 21:44, Maíra Canal wrote:
> > Hi Tvrtko,
> >
> > On 16/07/25 11:46, Tvrtko Ursulin wrote:
> > >
> > > On 16/07/2025 15:30, Maíra Canal wrote:
> > > > Hi Tvrtko,
> > > >
> > > > On 16/07/25 10:49, Tvrtko Ursulin wrote:
>
On Fri, 2025-07-18 at 10:35 +0100, Tvrtko Ursulin wrote:
>
> On 18/07/2025 10:31, Philipp Stanner wrote:
> > On Fri, 2025-07-18 at 08:13 +0100, Tvrtko Ursulin wrote:
> > >
> > > On 16/07/2025 21:44, Maíra Canal wrote:
> > > > Hi Tvrtko,
> > > >
> > > > On 16/07/25 11:46, Tvrtko Ursulin wrote:
>
[Public]
> -Original Message-
> From: Nathan Chancellor
> Sent: Tuesday, July 15, 2025 7:50 PM
> To: Deucher, Alexander ; Koenig, Christian
>
> Cc: Gao, Likun ; Zhang, Hawking
> ; amd-gfx@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; l...@lists.linux.dev; patc...@lists.linux
> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario
> wrote:
>
> On 7/17/25 11:55 AM, Melissa Wen wrote:
>> On 17-07-2025 13:39, Limonciello, Mario wrote:
>>> On 7/17/25 9:36 AM, Melissa Wen wrote:
This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81.
The commit causes a
Hi,
just tested that this Bug still exists in kernel version 6.16-rc6. The
example trigger from my previous mail still works triggering screen
freezing shortly after invocation.
I also learned that setting kernel param `amdgpu.dcdebugmask=0x10` works
as a workaround.
Kind regards,
Felix Ri
On 7/17/25 5:18 PM, Melissa Wen wrote:
> On 17-07-2025 19:17, Matthew Schwartz wrote:
>> On Thu, Jul 17, 2025 at 12:43 PM Melissa Wen wrote:
>>>
>>>
>>>
>>> On 17/07/2025 16:28, Matthew Schwartz wrote:
On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote:
> On 17-07-2025 17:57, Matthew Sch
On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote:
>
> On 17-07-2025 17:57, Matthew Schwartz wrote:
> >> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario
> >> wrote:
> >>
> >> On 7/17/25 11:55 AM, Melissa Wen wrote:
> >>> On 17-07-2025 13:39, Limonciello, Mario wrote:
> On 7/17/25 9:36 AM,
[AMD Official Use Only - AMD Internal Distribution Only]
Reviewed-by: Tao Zhou
> -Original Message-
> From: Chai, Thomas
> Sent: Friday, July 18, 2025 11:26 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Chai, Thomas ; Zhang, Hawking
> ; Zhou1, Tao ; Chai, Thomas
>
> Subject: [PATCH V2]
On 17.07.25 19:58, Gang Ba wrote:
> If vm belongs to another process, this is fclose after fork,
> wait may enable signaling KFD eviction fence and cause parent process queue
> evicted.
>
> [677852.634569] amdkfd_fence_enable_signaling+0x56/0x70 [amdgpu]
> [677852.634814] __dma_fence_enable_sig
Some PSPv11 SOCs take a longer time for PSP based mode-1 reset. Instead
of checking for C2PMSG_33 status, add the callback wait_for_bootloader.
Wait for bootloader to be back to steady state is already part of the
generic mode-1 reset flow. Increase the retry count for bootloader wait
and also fix
From: Ivan Lipski
[Why & How]
The AMD display hardware does not use dedicated cursor planes.
Instead, the cursor is rendered either using the primary plane
or an available overlay plane. This test verifies that the
cursor correctly falls back from native to overlay mode
when the underneath primar
On Fri, Jul 18, 2025 at 12:23 PM Lijo Lazar wrote:
>
> Some PSPv11 SOCs take a longer time for PSP based mode-1 reset. Instead
> of checking for C2PMSG_33 status, add the callback wait_for_bootloader.
> Wait for bootloader to be back to steady state is already part of the
> generic mode-1 reset fl
On 7/18/2025 9:36 AM, Lauri Tirkkonen wrote:
On Fri, Jul 18 2025 08:10:06 -0500, Mario Limonciello wrote:
Do you by chance have an OLED panel? I believe what's going on is that
userspace is writing zero or near zero and on OLED panels with older kernels
this means non-visible.
Yes, this is an
For security reasons it is safer to have the kernel driver handle
calculating the sizing for the control stack on queue creation for
gfx9, rather than having it done in userspace where arbitrarily large
values can be passed in potentially wasting space in VMID0.
Signed-off-by: Sunday Clement
---
Applied. Thanks!
Alex
On Thu, Jul 17, 2025 at 4:58 PM Peter Shkenev wrote:
>
> HUBBUB structure is not initialized on DCE hardware, so check if it is NULL
> to avoid null dereference while accessing amdgpu_dm_capabilities file in
> debugfs.
>
> Signed-off-by: Peter Shkenev
> ---
> drivers/gpu
On Fri, Jul 18, 2025 at 04:23:57PM +0530, Vignesh Raman wrote:
> Uprev IGT to the latest version and update expectation files.
>
> Signed-off-by: Vignesh Raman
> ---
> drivers/gpu/drm/ci/gitlab-ci.yml | 2 +-
> .../gpu/drm/ci/xfails/amdgpu-stoney-fails.txt | 2 +
> .../drm/ci/xf
Uprev mesa to adapt to the latest changes in Mesa CI, including support
for firmware via LAVA overlays, removal of the python-artifacts job,
split container and build rules, use of the alpine container for LAVA
jobs, and various misc fixes.
Signed-off-by: Vignesh Raman
---
drivers/gpu/drm/ci/bui
Uprev IGT to the latest version and update expectation files.
Signed-off-by: Vignesh Raman
---
drivers/gpu/drm/ci/gitlab-ci.yml | 2 +-
.../gpu/drm/ci/xfails/amdgpu-stoney-fails.txt | 2 +
.../drm/ci/xfails/amdgpu-stoney-flakes.txt| 7 ++
drivers/gpu/drm/ci/xfails/i915-aml
This series introduces new jobs to drm-ci for testing the following
devices:
- rk3588-rock-5b
- mt8192-asurada-spherion-r0
Other updates include:
- Uprev IGT and updating test expectations accordingly.
- Adapting to recent changes in Mesa CI, such as:
- LAVA overlay-based firmware handling
-
These devices are being moved to LAVA. The jobs will be enabled and the
job definitions will be updated once the move is complete.
Signed-off-by: Vignesh Raman
---
drivers/gpu/drm/ci/test.yml | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ci/test.yml b/
The sm8350-hdk jobs are short and each test takes around 2–3 minutes and
the full job completes in about 10 minutes. Running 4 parallel jobs uses
4 devices at once, which is not needed. Set parallel to 2 to reduce
device usage.
Signed-off-by: Vignesh Raman
---
drivers/gpu/drm/ci/test.yml | 2 +-
asus-C436FA-Flip-hatch has fewer devices available in the LAVA lab and
drm-ci uses only 2 DUTs, causing tests to time out. Update drm-ci to
use puff instead of hatch so the tests can run on 5 DUTs.
Also increase parallel count for amly jobs to 3.
Signed-off-by: Vignesh Raman
---
drivers/gpu/drm
Add job that executes the IGT test suite for rk3588-rock-5b.
Signed-off-by: Vignesh Raman
---
MAINTAINERS | 1 +
drivers/gpu/drm/ci/arm64.config | 5
drivers/gpu/drm/ci/build.sh | 1 +
drivers/gpu/drm/ci/gitlab-ci.yml
Add job that executes the IGT test suite for mt8192-asurada-spherion-r0.
Signed-off-by: Deborah Brouwer
Signed-off-by: Vignesh Raman
---
drivers/gpu/drm/ci/arm64.config | 4 +++
drivers/gpu/drm/ci/test.yml | 13 +--
.../drm/ci/xfails/mediatek-mt8192-fails.tx
On Fri, Jul 18, 2025 at 12:08 AM Lijo Lazar wrote:
>
> If driver load fails too early, asic_funcs pointer remains unassigned.
> Add NULL check to sanitize unwind path.
>
> Signed-off-by: Lijo Lazar
Acked-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_nbio.c | 3 ++-
> 1 file chang
On Fri, Jul 18, 2025 at 6:28 AM Liang, Prike wrote:
>
> [Public]
>
> What if when the kernel queue and user queue are enabled at the same time,
> then how to handle the case when userq mapped to a queue that has been
> enabled privileged bit by kernel queue?
These settings are per queue. kernel
[AMD Official Use Only - AMD Internal Distribution Only]
Reviewed-by: Leo Liu
> -Original Message-
> From: Sundararaju, Sathishkumar
> Sent: July 14, 2025 2:01 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Liu, Leo ; Sundararaju, Sathishkumar
>
> Subject: [PATCH] drm/amdgpu: Check vcn s
Add generic helper functions for vcn devcoredump support
which can be re-used for all vcn versions.
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 86 +
drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.h | 8 +++
2 files changed, 94 insertions(+)
diff
This patch series adds generic vcn register dump helper functions
and reuses it in all vcn versions instead of redefining the same
in every vcn version.
Sathishkumar S (8):
drm/amdgpu/vcn: Add regdump helper functions
drm/amdgpu/vcn: Register dump cleanup in VCN5
drm/amdgpu/vcn: Register du
Use generic vcn devcoredump helper functions for VCN5
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v5_0_0.c | 86 ++---
drivers/gpu/drm/amd/amdgpu/vcn_v5_0_0.h | 5 --
drivers/gpu/drm/amd/amdgpu/vcn_v5_0_1.c | 44 +++--
3 files changed, 44 inserti
Use generic vcn devcoredump helper functions for VCN4_0_0
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v4_0.c | 79 ++-
1 file changed, 5 insertions(+), 74 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v4_0.c
b/drivers/gpu/drm/amd/amdgpu/v
Use generic vcn devcoredump helper functions for VCN4_0_3
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v4_0_3.c | 78 ++---
1 file changed, 5 insertions(+), 73 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v4_0_3.c
b/drivers/gpu/drm/amd/amdgpu
Use generic vcn devcoredump helper functions for VCN4_0_5
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v4_0_5.c | 78 ++---
1 file changed, 5 insertions(+), 73 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v4_0_5.c
b/drivers/gpu/drm/amd/amdgpu
Use generic vcn devcoredump helper functions for VCN3_0
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c | 77 ++-
1 file changed, 5 insertions(+), 72 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v3_0.c
b/drivers/gpu/drm/amd/amdgpu/vcn
Use generic vcn devcoredump helper functions for VCN2_0_0
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v2_0.c | 78 ++-
1 file changed, 5 insertions(+), 73 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v2_0.c
b/drivers/gpu/drm/amd/amdgpu/v
Use generic vcn devcoredump helper functions for VCN2_5 and VCN2_6
Signed-off-by: Sathishkumar S
---
drivers/gpu/drm/amd/amdgpu/vcn_v2_5.c | 82 +++
1 file changed, 7 insertions(+), 75 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/vcn_v2_5.c
b/drivers/gpu/drm/amd
On 7/17/2025 2:42 PM, Felix Richter wrote:
Hi,
just tested that this Bug still exists in kernel version 6.16-rc6. The
example trigger from my previous mail still works triggering screen
freezing shortly after invocation.
I also learned that setting kernel param `amdgpu.dcdebugmask=0x10` work
60 matches
Mail list logo
