Hi,
I could eventually reboot the workstation after I upgraded to Linux
4.19.8, and updated to today's sid.
Let me go through your config hints first:
# grep CGROUP /boot/config-4.18.0-3-amd64
...
I checked and these were all active in my kernel build as well.
$ findmnt
...
Maybe check i
> I assume the main difference is that you are not using a Debian
> provided
> kernel and I do?
Yes i'm running my own compiled 4.19.5 kernel, old habit of mine to use
make-kpkg builds.
I'll install the standard debian kernel and give a try on next reboot (may not
happen before end of the week)
Package: systemd-container
Version: 239-14
Severity: important
Dear Maintainer,
Current systemd-nspawn fails to start a container when going through
the systemd machine target or using machinectl.
I'll illustrate this using a debian stable debootstrap.
I found a thread discussing similar issues
Package: initramfs-tools
Version: 0.93.4
Severity: important
*** Please type your report below this line ***
After a power grid problem in my neighborhood, my workstation
rebooted and detected problems in the ext4 LVM volumes.
It appears that after a manual fsck.ext4, these problems were
trigerr
4 matches
Mail list logo
