From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [REGRESSION] AMD GPU regression in 5.16.18..5.17.4 #forregzbot
Date: Mon, 9 May 2022 10:04:52 +0200 [thread overview]
Message-ID: <db529b0f-c147-91f3-4382-01c636c5522c@leemhuis.info> (raw)
In-Reply-To: <0b0025c1-107b-8dab-f30a-87b428b45e08@leemhuis.info>
On 29.04.22 13:36, Thorsten Leemhuis wrote:
> TWIMC: this mail is primarily send for documentation purposes and for
> regzbot, my Linux kernel regression tracking bot. These mails usually
> contain '#forregzbot' in the subject, to make them easy to spot and filter.
>
> #regzbot fixed-by: 78b12008f20
Landed in mainline with a different ID:
#regzbot fixed-by: 19965d8259fdabc68
> On 25.04.22 23:29, Deucher, Alexander wrote:
>> [Public]
>>
>>> -----Original Message-----
>>> From: Demi Marie Obenour <demi@invisiblethingslab.com>
>>> Sent: Sunday, April 24, 2022 7:39 PM
>>> To: Thorsten Leemhuis <regressions@leemhuis.info>; Greg KH
>>> <gregkh@linuxfoundation.org>
>>> Cc: amd-gfx@lists.freedesktop.org; regressions@lists.linux.dev;
>>> Deucher, Alexander <Alexander.Deucher@amd.com>; Koenig, Christian
>>> <Christian.Koenig@amd.com>; Pan, Xinhui <Xinhui.Pan@amd.com>
>>> Subject: Re: [REGRESSION] AMD GPU regression in 5.16.18..5.17.4
>>>
>>> On Sun, Apr 24, 2022 at 11:02:43AM +0200, Thorsten Leemhuis wrote:
>>>> 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-
>>> 11076
>>>> 81126 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.
>>>
>>> The reporter was able to bisect the regression. I am not surprised
>>> that this commit caused problems for Qubes OS, as dom0 in Qubes OS is
>>> technically a guest of Xen.
>>>
>>> #regzbot ^introduced: b818a5d374542ccec73dcfe578a081574029820e
>>
>> Can you please follow up on the bug ticket:
>> https://gitlab.freedesktop.org/drm/amd/-/issues/1985
>> It will be easier to track everything there.
>>
>> Alex
prev parent reply other threads:[~2022-05-09 8:09 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
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 [this message]
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=db529b0f-c147-91f3-4382-01c636c5522c@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=amd-gfx@lists.freedesktop.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).