Bug #989705: Suspend to RAM hangs computer with nouveau driver and kernel 5.10.0-7-amd64
Hi everybody,
With the Acer Aspire 5930G notebook computer (equipped by a GPU
GeForce 9600M GT), suspend to ram and suspend to disk always hangs or
leave the computer in an unstable state both booting Debian Bullseye
from kernel ver. 5.10.0-7-amd64 (current Debian Testing a.k.a.
"Bullseye") and following versions of the kernel up to
vanilla/upstream "stable" and "mainline" and, also, booting from
kernels at least starting from version 5.9 (compiled from upstream).
On the contrary, suspend to ram and suspend to disk are always
successfully completed booting Debian Bullseye from kernel version
4.19.0-11-amd64 (that is still installed after upgrading from current
Debian Stable "Buster" to Debian Testing "Bullseye").
If computer boots from affected kernels, when suspend to RAM is
started (both, for example, from the Desktop Environment KDE or the
command line with Desktop Environment running / the graphical greater
running):
a) computer starts suspend to RAM as usual and the display goes dark;
b) the notebook stays alive with fan running for about *20 minutes*
with dark screen and keyboard/power leds staying on;
c) after b), the suspend to RAM is apparently completed and computer
shuts down with the usual blinking orange led;
d) when computer is resumed (eg, pressing a key), it hangs showing
briefly or forever a garbled screen (just like the one showed in the
bug report https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/547);
e) at this stage:
e.1) computer sometime is completely frozen (not responding to REISUB
sequence, either)
e.2) computer sometime is remotely accessible after starting resume by
ssh (for example, to obtain logs or to reboot system) or sometimes
switching to textual console and in this case it responds to REISUB
sequence, too.
Such a bug was already reported here
(https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/547),
but a solution has not been proposed, yet. Then I opened a bug report
upstream (https://bugzilla.kernel.org/show_bug.cgi?id=213617) but I
haven't received any response so far. Then I opened the debian bug
report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989705.
I tried to bisect the bug, but I didn't succeed.
More detailed system log and specific suspend-resume logs log are
available in the bug reports.
I send this email to the kernel mailing list hoping someone can give
me a hint to further analyse the issue and/or to fin a solution.
Thanks in advance.
Reply to: