From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Sergio Callegari" <sergio.callegari@gmail.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
stable@vger.kernel.org,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Linux kernel regressions list" <regressions@lists.linux.dev>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Christian König" <christian.koenig@amd.com>,
"George Zhang" <george.zhang@amd.com>
Subject: Re: [REGRESSION] Please revert 1191285ecb42 from 7.1.y
Date: Wed, 12 Aug 2026 09:12:26 +0900 [thread overview]
Message-ID: <2026081216-goon-nicotine-6d62@gregkh> (raw)
In-Reply-To: <CADnq5_Pb=ox3nWfdpb3Qeo_eSQayuc7UqUOnm0x+WS+EQTVWjA@mail.gmail.com>
On Tue, Aug 11, 2026 at 01:25:14PM -0400, Alex Deucher wrote:
> On Tue, Aug 11, 2026 at 11:25 AM Sergio Callegari
> <sergio.callegari@gmail.com> wrote:
> >
> > On 11/08/2026 10:08, Greg KH wrote:
> > > We aim to be "bug compatible" with Linus's branch, otherwise the
> > > "pressure" to fix those bugs goes down. But I defer to the maintainers
> > > of the code involved if it is being worked on, and they want it
> > > reverted, great, we can do that. Otherwise we prefer to leave it as-is.
> >
> > I understand. Sorry for asking about things that might be obvious to
> > most people here. My expectation was that only a selected subset of the
> > patches on the Linus' tree were to enter in stable, so do we really need
> > to have stable "bug compatible" wrt this bug? The original behavior was
> > not free of issues, but they were rather minor (a reporting issue). Now
> > we have this very bad behavior where the display remains dark.
> >
> > To make the matter worse, on systems that have encrypted root the screen
> > remains dark also on that password prompt (observed with plymouth).
> >
> > In any case, I managed testing 7.2.0RC7 and it is fine again.
> >
> > Looks like the Linus' tree has more changes wrt backlight, and the
> > interesting ones are probably those in the cumulative fix
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=973fd9493ec21f12e760fbbedeb7b0b2317c02f4.
> >
>
> Thanks for testing. It sounds like we should revert the change from
> stable. There must be some dependency we are missing in stable.
Great, can someone send a revert?
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-12 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c6acb62-4080-48e6-9ba2-d1c457c4ec88@gmail.com>
[not found] ` <2026081106-pebbly-cahoots-37a7@gregkh>
2026-08-11 5:24 ` [REGRESSION] Please revert 1191285ecb42 from 7.1.y Thorsten Leemhuis
2026-08-11 7:28 ` Sergio Callegari
2026-08-11 8:08 ` Greg KH
2026-08-11 12:26 ` Sergio Callegari
2026-08-11 17:25 ` Alex Deucher
2026-08-12 0:12 ` Greg KH [this message]
2026-08-12 14:49 ` Alex Deucher
2026-08-12 22:21 ` Sasha Levin
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=2026081216-goon-nicotine-6d62@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=george.zhang@amd.com \
--cc=mario.limonciello@amd.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sergio.callegari@gmail.com \
--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