On Mon, Apr 4, 2022 at 3:39 PM Michele Ballabio <ballabio.m@xxxxxxxxx> wrote: > > On Mon, 4 Apr 2022 13:03:41 -0400 > Alex Deucher <alexdeucher@xxxxxxxxx> wrote: > > > On Sun, Apr 3, 2022 at 10:19 AM Michele Ballabio > > <ballabio.m@xxxxxxxxx> 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/ ? 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 problems. Thanks, Alex > > Thanks, > Michele Ballabio
