linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Walt Holman <waltholman09@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: mario.limonciello@amd.com, alexander.deucher@amd.com
Subject: Re: AMDGPU - Regression: Black screen due to commit 16dc8bc27c2aa3c93905d3e885e27f1e3535f09a
Date: Sat, 21 Jun 2025 10:52:12 -0500	[thread overview]
Message-ID: <48ff3e59-db6f-4870-8f0b-3c49dd4d865e@kernel.org> (raw)
In-Reply-To: <CAMb39_mAWfeuyDjHR4Ej9fH=PXdH0qUda50R=iqGKVzN1mcHPQ@mail.gmail.com>



On 6/21/25 10:18 AM, Walt Holman wrote:
> Hello,
> 
> With the latest drm fixes this week on 6.16-rc2, I am experiencing a
> black screen instead of the sddm greeter and the GPU appears to be
> locked up. I can ssh into the laptop and reboot it, but that's about
> it. I have bisected the commit to commit id:
> 16dc8bc27c2aa3c93905d3e885e27f1e3535f09a and upon reverting the
> commit, the system works as normal. The hardware is an Asus Rog
> Zephyrus G16 with AMD Ryzen AI 9 HX 370 w/ Radeon 890M video. I'm able
> to test patches etc.. if need be.

Hi there,

By chance do you have an OLED panel?  If so can you please try the patch 
attached to this bug?

https://gitlab.freedesktop.org/drm/amd/-/issues/4338

Thanks,

> 
> 16dc8bc27c2aa3c93905d3e885e27f1e3535f09a is the first bad commit
> commit 16dc8bc27c2aa3c93905d3e885e27f1e3535f09a (HEAD)
> Author: Mario Limonciello <mario.limonciello@amd.com>
> Date:   Thu May 29 09:46:32 2025 -0500
> 
>      drm/amd/display: Export full brightness range to userspace
> 
>      [WHY]
>      Userspace currently is offered a range from 0-0xFF but the PWM is
>      programmed from 0-0xFFFF.  This can be limiting to some software
>      that wants to apply greater granularity.
> 
>      [HOW]
>      Convert internally to firmware values only when mapping custom
>      brightness curves because these are in 0-0xFF range. Advertise full
>      PWM range to userspace.
> 
>      Cc: Mario Limonciello <mario.limonciello@amd.com>
>      Cc: Alex Deucher <alexander.deucher@amd.com>
>      Reviewed-by: Roman Li <roman.li@amd.com>
>      Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>      Signed-off-by: Alex Hung <alex.hung@amd.com>
>      Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
>      Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>      (cherry picked from commit 8dbd72cb790058ce52279af38a43c2b302fdd3e5)
>      Cc: stable@vger.kernel.org
> 
>   drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 41
> +++++++++++++++++++++++++++--------------
>   1 file changed, 27 insertions(+), 14 deletions(-)
> 


  reply	other threads:[~2025-06-21 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21 15:18 AMDGPU - Regression: Black screen due to commit 16dc8bc27c2aa3c93905d3e885e27f1e3535f09a Walt Holman
2025-06-21 15:52 ` Mario Limonciello [this message]
2025-06-21 16:03   ` Walt Holman
2025-06-21 16:07     ` Walt Holman
2025-06-21 19:12       ` Mario Limonciello
2025-06-21 19:32         ` Walt Holman
2025-06-23 14:51           ` Mario Limonciello
2025-06-23 15:35             ` Walt Holman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48ff3e59-db6f-4870-8f0b-3c49dd4d865e@kernel.org \
    --to=superm1@kernel.org \
    --cc=alexander.deucher@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=waltholman09@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).