From: Mario Limonciello <mario.limonciello@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Michael Larabel <Michael@michaellarabel.com>
Subject: Re: Kernel 6.5 black screen regression
Date: Thu, 7 Sep 2023 09:06:15 -0500 [thread overview]
Message-ID: <2b6d2117-b76d-4e86-87ba-48ebc6da11a9@amd.com> (raw)
In-Reply-To: <2023090729-struggle-poison-4ebc@gregkh>
On 9/7/2023 05:13, Greg KH wrote:
> On Wed, Sep 06, 2023 at 12:55:29PM -0500, Mario Limonciello wrote:
>> Hi,
>>
>> The following patch fixes a regression reported by Michael Larabel on an
>> Acer Phoenix laptop where there is a black screen in GNOME with kernel 6.5.
>>
>> It's marked CC to stable, but I checked the stable queue and didn't see it
>> so I wanted to make sure it wasn't missed.
>
> The fixes tag in that commit is odd, it says it fixes something that is
> NOT in 6.5, so are you sure about this?
>
I believe it's one of those cases that the same commit landed twice. So
the wrong SHA got added to the fixes tag.
This is the one it should have been:
1ca67aba8d11 ("drm/amd/display: only accept async flips for fast updates")
>> a7c0cad0dc06 ("drm/amd/display: ensure async flips are only accepted for
>> fast updates")
>>
>> Reported-by: Michael Larabel <Michael@MichaelLarabel.com>
>
> Ok, now queued up, thanks.
Thanks!
Seeing the correct sha1; I find the problematic one backported to:
* 6.4.7 as cd013a58cf64 ("drm/amd/display: only accept async flips for
fast updates")
and
* 6.1.42 as 438542074174 ("drm/amd/display: only accept async flips for
fast updates")
Did you only queue for 6.5.y? If so, can you please add to 6.1.y and
6.4.y as well?
Thanks!
next prev parent reply other threads:[~2023-09-07 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 17:55 Kernel 6.5 black screen regression Mario Limonciello
2023-09-07 10:13 ` Greg KH
2023-09-07 14:06 ` Mario Limonciello [this message]
2023-09-07 14:44 ` Greg KH
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=2b6d2117-b76d-4e86-87ba-48ebc6da11a9@amd.com \
--to=mario.limonciello@amd.com \
--cc=Michael@michaellarabel.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/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