On 08/21/2018 01:27 PM, Robert Moskowitz wrote:
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).
On the Fedora users list we have had a terrible time with suspend on
F28. 4.17.3 was ok, but then broke with 4.17.4 and was not, for the
most part, fixed until 4.17.11. But still even with 4.17.14 a number
of us are still reporting that suspend fails the first time with the
system immediately restarting and then when you unlock your system and
suspend again, that 'takes'.
And we have been getting a weekly kernel update on F28 64 for some time
now. I cannot remember another Fedora release where the kernel updates
have come so frequently for so long.
Some of the reported problems (by ME!) revolved around QEMU running an
image.
Most logs showed hangs occurring right after NetworkManager messages
(but not all that are typically seen on successful suspends).
So does not surprise me at all that we are not out of the woods here.
I wonder if anyone is testing this on x86_64 systems. I don't have
the wherewithall to do that.
I will put together a test on a Cubieboard2 with the Xfce desktop. But
I will be waiting for an image that contains openssl 1.1.1-pre9 to put
in the time. And I never really tested suspend to swap on my Cubies.
It will be painful with swap on an SD card.
And I think that is part of the suspend problem. If it takes too
long, some thing breaks.
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/message/VAQF4AGLJXHX726FBWF7IGQ63OAWN7MC/
_______________________________________________
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/message/5K6ZCYMDWC7AXLI5F5HHY5N3S5ESNIF3/
