All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michele Ballabio <ballabio.m@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	regressions@lists.linux.dev
Subject: Re: AMDGPU: regression on 5.17.1
Date: Mon, 4 Apr 2022 21:39:40 +0200	[thread overview]
Message-ID: <20220404213940.09a56d15@darkstar.example.org> (raw)
In-Reply-To: <CADnq5_M+M_iykM0Ag6RF+kxzgpEopUBtp82h7tRM3G+B3AWZ2w@mail.gmail.com>

On Mon, 4 Apr 2022 13:03:41 -0400
Alex Deucher <alexdeucher@gmail.com> wrote:

> On Sun, Apr 3, 2022 at 10:19 AM Michele Ballabio
> <ballabio.m@gmail.com> wrote:
> >
> > Hi,
> >         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 similar).  
> 
> Can you bisect?  Does setting amdgpu.runpm=0 help?

I can try to bisect, should I narrow the search to drivers/gpu/drm/ ?

Setting amdgpu.runpm=0 works, the display now unblanks without problems.

Thanks,
    Michele Ballabio

WARNING: multiple messages have this Message-ID (diff)
From: Michele Ballabio <ballabio.m@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	regressions@lists.linux.dev,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: AMDGPU: regression on 5.17.1
Date: Mon, 4 Apr 2022 21:39:40 +0200	[thread overview]
Message-ID: <20220404213940.09a56d15@darkstar.example.org> (raw)
In-Reply-To: <CADnq5_M+M_iykM0Ag6RF+kxzgpEopUBtp82h7tRM3G+B3AWZ2w@mail.gmail.com>

On Mon, 4 Apr 2022 13:03:41 -0400
Alex Deucher <alexdeucher@gmail.com> wrote:

> On Sun, Apr 3, 2022 at 10:19 AM Michele Ballabio
> <ballabio.m@gmail.com> wrote:
> >
> > Hi,
> >         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 similar).  
> 
> Can you bisect?  Does setting amdgpu.runpm=0 help?

I can try to bisect, should I narrow the search to drivers/gpu/drm/ ?

Setting amdgpu.runpm=0 works, the display now unblanks without problems.

Thanks,
    Michele Ballabio

  reply	other threads:[~2022-04-04 19:39 UTC|newest]

Thread overview: 21+ 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  7:17   ` Thorsten Leemhuis
2022-04-04 17:03 ` Alex Deucher
2022-04-04 17:03   ` Alex Deucher
2022-04-04 19:39   ` Michele Ballabio [this message]
2022-04-04 19:39     ` Michele Ballabio
2022-04-05 14:23     ` Alex Deucher
2022-04-05 14:23       ` Alex Deucher
2022-04-09 16:28       ` Michele Ballabio
2022-04-09 16:28         ` Michele Ballabio
2022-04-09 17:32         ` AMDGPU: regression on 5.17.1 #forregzbot Thorsten Leemhuis
2022-04-09 17:32           ` Thorsten Leemhuis
2022-04-11 18:34         ` AMDGPU: regression on 5.17.1 Alex Deucher
2022-04-11 18:34           ` Alex Deucher
2022-04-13 17:33           ` Michele Ballabio
2022-04-13 17:33             ` Michele Ballabio
2022-04-13 18:14             ` Alex Deucher
2022-04-13 18:14               ` Alex Deucher
2022-04-13 19:41               ` Michele Ballabio
2022-04-13 19:41                 ` Michele Ballabio

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=20220404213940.09a56d15@darkstar.example.org \
    --to=ballabio.m@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.