From: Thorsten Leemhuis <email@example.com>
Cc: LKML <firstname.lastname@example.org>,
Maling list - DRI developers <email@example.com>,
amd-gfx list <firstname.lastname@example.org>
Subject: Re: AMDGPU: regression on 5.17.1 #forregzbot
Date: Sat, 9 Apr 2022 19:32:37 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
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.
On 09.04.22 18:28, Michele Ballabio wrote:
> On Tue, 5 Apr 2022 10:23:16 -0400
> Alex Deucher <firstname.lastname@example.org> wrote:
>> On Mon, Apr 4, 2022 at 3:39 PM Michele Ballabio
>> <email@example.com> wrote:
>>> On Mon, 4 Apr 2022 13:03:41 -0400
>>> Alex Deucher <firstname.lastname@example.org> wrote:
>>>> On Sun, Apr 3, 2022 at 10:19 AM Michele Ballabio
>>>> <email@example.com> wrote:
>>>>> I've hit a regression on 5.17.1 (haven't tested 5.17.0,
>>>>> but 5.16-stable didn't have this problem).
>>>>> The machine is a Ryzen 5 1600 with AMD graphics (RX 560).
>>>>> The regression I hit seems to trigger when the machine is left
>>>>> idle at boot (I don't boot straight to X, I boot to a tty, login
>>>>> and then start X). The machine after a while blanks the screen.
>>>>> Usually, the screen unblanks as the keyboard is hit or the mouse
>>>>> moves, but with kernel 5.17.1 the screen does not wake up. The
>>>>> machine seems to run mostly fine: I can login from ssh, but I
>>>>> cannot reboot or halt it: a sysrq sequence is needed for that.
>>>>> Note that if the screen goes blank under X, it wakes up fine.
>>>>> Below a dmesg and two traces from syslog (they're quite
>>>> Can you bisect? Does setting amdgpu.runpm=0 help?
>>> I can try to bisect, should I narrow the search to drivers/gpu/drm/
>> I would just do a full bisect if possible in case the change happens
>> to be outside of drm.
>>> Setting amdgpu.runpm=0 works, the display now unblanks without
> I bisected this, and the first bad commit is
> [087451f372bf76d971184caa258807b7c35aac8f] drm/amdgpu: use generic fb
> helpers instead of setting up AMD own's.
#regzbot introduced: 087451f372bf76d971184caa258807b7c35aac8f
next prev parent reply other threads:[~2022-04-09 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 11:23 AMDGPU: regression on 5.17.1 Michele Ballabio
2022-04-04 7:17 ` Thorsten Leemhuis
2022-04-04 17:03 ` Alex Deucher
2022-04-04 19:39 ` Michele Ballabio
2022-04-05 14:23 ` Alex Deucher
2022-04-09 16:28 ` Michele Ballabio
2022-04-09 17:32 ` Thorsten Leemhuis [this message]
2022-04-11 18:34 ` Alex Deucher
2022-04-13 17:33 ` Michele Ballabio
2022-04-13 18:14 ` Alex Deucher
2022-04-13 19:41 ` Michele Ballabio
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).