Nicolas,
I finally have an Xfce desktop. So I decided to try suspend to ram.
It did something, but then stopped. Monitor is still on, in character
mode. And I realized, WHAT do I do to get the system to resume? What
do I have on this SOC that will trigger the resume. I am stumped!
So I will power cycle...
[ 1422.375877] PM: Syncing filesystems ... done.
[ 1427.191217] Freezing user space processes ... (elapsed 0.004 seconds)
done.
[ 1427.203321] OOM killer disabled.
[ 1427.206678] Freezing remaining freezable tasks ... (elapsed 0.001
seconds) done.
[ 1427.216019] Suspending console(s) (use no_console_suspend to debug)
On 08/21/2018 11:40 AM, Nicolas Chauvet wrote:
Hi there,
While testing upstream kernel on some devices, I've recently
discovered that suspend was broken for "distro kernel" (not only
related to fedora kernel, but also ubuntu).
I order to debug this, I was advised to use a serial console and boot
with theses options:
no_console_suspend=1 initcall_debug
Then using systemctl suspend outputs this report for me:
https://bugzilla.redhat.com/show_bug.cgi?id=1619699
Basically, I'm running a tegra device, but a pxa driver (unrelated to
the device) lead to a crash preventing suspend.
I would like others on this list to try to report such use case, I
don't expect pxa_gpio to be the only driver to have issue in the
fedora config. Specially as it does not have problem at boot time or
shutdown so this problem might remains silent.
Please don't forget to block ARMTracker on bugzilla.redhat.com, and
mention it there if you uses upstream bug tracker.
Thx for any report.
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
