Bug#1072524: systemd: On a debian trixie, after upgrading systemd to latest version the system fails to reboot.

Christophe Trophime christophe.trophime at lncmi.cnrs.fr
Tue Jun 4 08:00:57 BST 2024


Indeed, it seems that I have tweeked my debian box for nvidia-docker at the time.
In /etc/default/grub:

# Add this line for nvidia-docker
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=0"

Christophe TROPHIME 
Research Engineer 

CNRS - LNCMI 
25, rue des Martyrs 
BP 166 
38042 GRENOBLE Cedex 9 
FRANCE 

Tel : +33 (0)4 76 88 90 02 
Fax : +33 (0) 4 76 88 10 01 
Office U 19 
M at il : christophe.trophime at lncmi.cnrs.fr

----- Original Message -----
> From: "Luca Boccassi" <bluca at debian.org>
> To: "Christophe Trophime" <christophe.trophime at lncmi.cnrs.fr>
> Cc: 1072524 at bugs.debian.org
> Sent: Monday, June 3, 2024 7:33:45 PM
> Subject: Re: systemd: On a debian trixie, after upgrading systemd to latest version the system fails to reboot.

> On Mon, 3 Jun 2024 at 18:29, Christophe Trophime
> <christophe.trophime at lncmi.cnrs.fr> wrote:
>>
>> Hi,
>> could you please just tell what info do you need?
> 
> As already mentioned: did you customize the kernel command line?
> Cgroupsv2 has been the default for years
> 
>> ----- Original Message -----
>> > From: "Luca Boccassi" <bluca at debian.org>
>> > To: 1072524 at bugs.debian.org
>> > Cc: "Christophe Trophime" <christophe.trophime at lncmi.cnrs.fr>
>> > Sent: Monday, June 3, 2024 6:53:19 PM
>> > Subject: Re: systemd: On a debian trixie, after upgrading systemd to latest
>> > version the system fails to reboot.
>>
>> > Control: tags -1 moreinfo
>> >
>> > On Mon, 03 Jun 2024 18:41:12 +0200 Christophe Trophime
>> > <christophe.trophime at lncmi.cnrs.fr> wrote:
>> >> Package: systemd
>> >> Version: 256~rc3
>> >> Severity: important
>> >> X-Debbugs-Cc: christophe.trophime at lncmi.cnrs.fr
>> >>
>> >> Dear Maintainer,
>> >>
>> >> After upgrading systemd the machine does not reboot.
>> >> The error message says:
>> >>
>> >> systemd freezing execution
>> >> refusing to run under cgroup v1, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1
>> >> shall be passed to kernel command line
>> >>
>> >>
>> >> As far as I have understood cgroup v1 is no longer supported.
>> >> So I think I have 2 choices:
>> >> * add the variable to the kernel starting command line,
>> >> * disable cgroup v1
>> >>
>> >> The point is that I cannot figure out how to do?
>> >> Cannot find how to set the variable, nor how to eventually disable
>> >> cgroup v1?
>> >>
>> >> Which packages may use the cgroup v1 features?
>> >> I'm using container tools like docker (nvidia-container), singularity
>> > and charliecloud
>> >>
>> >> Thanks for your help
>> >> Best
>> >> C
>> >>
>> >> PS: cannot provide any additional info about my debian trixie host.
>> >
>> > cgroupsv2 is the default and has been since Bookworm, did you apply
>> > some custom kernel command line that disables it?
>> >
>> > --
>> > Kind regards,
> > > Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2288 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240604/055ff630/attachment-0001.bin>


More information about the Pkg-systemd-maintainers mailing list