[Bug 263632] framework laptop crashes a few seconds after resuming from sleep

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 04 May 2022 03:57:01 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263632

--- Comment #10 from Jonathan Vasquez <jon@xyinn.org> ---
Some interesting updates.

So it seems that it may not be the kernel that's crashing (yet) but the X
server in combination with the kernel.. basically the behavior that I'm
experiencing can be reproduced (non-deterministically but it will happen) if I
do:

xrandr --output eDP-1 --scale 0.8

You can use any other number as well. As long you cause frequent changes, it
will eventually happen. Now something that's further interesting is that once
it locks up, pressing keys or moving your mouse won't work. Attempting to
switch to a virtual terminal also won't work, or at least it would seem like it
didn't. The first interesting thing I noticed was that even though I wasn't
able to do much after it locked up, if I pressed the power button, the system
actually received the signal and I could see my tty1 again and the system
eventually shuts down. So that would indicate that the kernel hasn't actually
crashed. I also saw the following message (same as before but with another
line):

drmn0: GPU HANG: ecode 12:1:85dffffb, in MainThread [100328]
drmn0: Resetting rcs0 for stopped heartbeat on rcs0
drmn0: Xorg[100328] context reset due to GPU hang

The second interesting thing was that once I got it locked again, I was
actually able to - eventually - switch to a TTY. I just kept pressing Ctrl +
Alt + F[1-4] until one of them got through to the system.

Lastly, after the system got locked, I managed to switch to a TTY and then kill
X, and start another session immediately. Once I locked it for a second time in
a row, my system was truly frozen and I had no chance of switching to a TTY and
the power button also stopped getting its shutdown signal through to the
kernel. I had to hard power off the machine. So it's interesting that a second
"hard crash" managed to be worse than the first, as if there was some remnant
state that managed to worsen things.

-- 
You are receiving this mail because:
You are the assignee for the bug.