From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>,
Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
regressions@lists.linux.dev, amd-gfx@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [REGRESSION] AMD GPU regression in 5.16.18..5.17.4
Date: Sun, 24 Apr 2022 11:02:43 +0200 [thread overview]
Message-ID: <e1950610-ba09-7c42-4a1a-152ad41015b5@leemhuis.info> (raw)
In-Reply-To: <YmTqYkGEqiz1o2o6@kroah.com>
CCing the amdgpu maintainers
On 24.04.22 08:12, Greg KH wrote:
> On Sat, Apr 23, 2022 at 12:06:33PM -0400, Demi Marie Obenour wrote:
>> Two Qubes OS users reported that their AMD GPU systems did not work on
>> 5.17.4, while 5.16.18 worked fine. Details can be found on
>> https://github.com/QubesOS/qubes-issues/issues/7462. The initial report
>> listed the GPU as “Advanced Micro Devices, Inc. [AMD/ATI] Renoir
>> [1002:1636} (rev d3) (prog-if 00 [VGA controller])” and the CPU as
>> “AMD Ryzen 5 PRO 4650U with Radeon Graphics”.
>>
>> #regzbot introduced: v5.16.18..v5.17.4
>
> That's a big range, can you use 'git bisect' to track it down?
FWIW, in another mail in this thread and
https://github.com/QubesOS/qubes-issues/issues/7462#issuecomment-1107681126
it was clarified that the problem was introduced between 5.17.3 and
5.17.4, where a few amdgpu changes were applied. Maybe they are the reason.
Anyway: Yes, as Gregkh said, a bisection really would help. But maybe
the amdgfx developers might already have an idea what might be wrong
here? The QubesOS ticket linked above has some more details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
next prev parent reply other threads:[~2022-04-25 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 16:01 AMD GPU regression in 5.16.18..5.17.4 Demi Marie Obenour
2022-04-23 16:06 ` [REGRESSION] " Demi Marie Obenour
2022-04-24 1:40 ` Demi Marie Obenour
2022-04-24 6:12 ` Greg KH
2022-04-24 9:02 ` Thorsten Leemhuis [this message]
2022-04-24 15:52 ` Demi Marie Obenour
2022-04-24 15:58 ` Demi Marie Obenour
2022-04-24 23:38 ` Demi Marie Obenour
2022-04-25 21:29 ` Deucher, Alexander
2022-04-29 11:36 ` [REGRESSION] AMD GPU regression in 5.16.18..5.17.4 #forregzbot Thorsten Leemhuis
2022-05-09 8:04 ` Thorsten Leemhuis
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=e1950610-ba09-7c42-4a1a-152ad41015b5@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=demi@invisiblethingslab.com \
--cc=gregkh@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
/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).