Bug#929655: Confirmed issue 11810, release-critical

[Kathryn Tolsen]

I am confirming that this is issue 11810 as described:
https://github.com/systemd/systemd/issues/11810

a reboot solves the problem, but a S3 state causes it routinely on AMD
processors.

I have updated my logs available at http://kbt.ddns.net/ until this issue
is resolved, showing a fresh boot, sleep, and stopping several services and
restarting them.. services affected include nfs, samba, ssh, minidlna,
webmin (unofficial), services that did not seem to be affected was the
lighttpd which restarted just fine it would seem.

I am reporting this update to say without a doubt this issue exists, and
its a pretty serious issue for a large number of people, and it should most
certainly be considered release-critical to get a newer systemd into buster
prior to release.. as this issue is not security related, yet it results in
a cascading failure of even simple services like logrotation and tempfile
cleanup, for a large number of our user base. It would not be a good thing
to make a stable release with a known issue that causes total breakdown in
a package so many people already loathe... it would just seem negligent and
would cause unnecessary stress on our support teams because this is not a
very easy issue to track down as the error message gives no hints as to
what the actual problem, cause, or solution is and it only affects AMD
processors it would seem.

Thank you, and *pokes the D-I team* this means YOU! We need this update to
241-4 or 241-5!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190528/c4605790/attachment.html>