[systemd] Version 245.6-1 breaks suspended + resume

[Sedat Dilek]

On Mon, Jun 8, 2020 at 1:07 PM Michael Biebl <biebl at debian.org> wrote:
>
> Hi Sedat
> Am 08.06.20 um 10:12 schrieb Sedat Dilek:
>
> > Today, I switched over from systemd version 245.5-3 to 245.6-1 on
> > Debian/testing AMD64.
> >
> > On the upgrade, I read there is a new version of journald.conf.
> > I have not checked what changed.
> >
> > Here I have a 00-journal-size.conf file:
> >
> > # cat /etc/systemd/journald.conf.d/00-journal-size.conf
> > [Journal]
> > SystemMaxUse=100M
> >
> > I increased the value for SystemMaxUse from 50M to 100M (see below status).
> > Too small?
> > Unsure, if this is related or not.
>
> Seems unrelated to your problem
>
> > And did a 2nd suspend and resume.
> >>From my memory:
> > Ext4-FS block issues
> > systemd-journald: /var/log/journal/... is read-only
> >
> > The system is in an awful and unusable situation.
> > Typing any command in konsole shows command not known/found.
> > I have not found a way to debug this.
> >
> > Known issue?
>
> The symptoms you see point to a kernel problem / file system corruption
> which are highly unlikely related to the systemd upgrade.
>
> > What informations do you need?
> > Can you give help on debugging?
>
> I think you need help from the kernel folks. I doubt this is a systemd
> issue.
>

Hi Michael,

just as a short feedback.

I am in contact with Ted (tytso) linux-ext4 maintainer.

For me, it looks like the root cause is my Root-FS (Ext4-FS) is on an
external USB-3.0 HDD connected via an ASMedia USB-3.0 controller.
I tried with blacklisting via udev-rules to control usb/pci/device
(auto)suspend and (acpi-)wakeup.
With no success.

Unsure, how suspend+resume in Debian really works.
For me everything concerning/controlling the access to the external
USB HDD has to resume first before any other actions.
Maybe, when I find more time I will dig into this.

In the end I decided to revert all my changes as I am not really using
suspend+resume these days.

Yes, you are right it is not an issue with the latest systemd-upgrade.

Thanks.

Regards,
- Sedat -