Bug#1077204: systemd fails to boot on a 5.4 kernel
Luca Boccassi
bluca at debian.org
Sun Jul 28 13:21:53 BST 2024
On Sun, 28 Jul 2024 at 12:04, Kornilios Kourtis <kkourt at kkourt.io> wrote:
>
> On Sun, Jul 28, 2024 at 11:16:33AM +0100, Luca Boccassi wrote:
> > > Booting the kernel.
> > > [ 0.000000] Linux version 5.4.280 (root at buildkitsandbox) (gcc
> > version 13.2.0 (Ubuntu 13.2.0-23ubuntu4)) #1 SMP Fri Jul 26 13:40:53
> > UTC 2024
> >
> > You are running an Ubuntu kernel on Debian? That doesn't make sense and
> > it's not supported. You are probably hitting some apparmor denials that
> > are blocking some setup step from working:
> >
> > dev-hugepages.mount: Failed to spawn executor: Argument list too long
> >
> > Use the Debian kernel from the Debian version you are running, or if
> > you want to use an Ubuntu kernel, install Ubuntu instead.
>
> This is not an ubuntu kernel. It is a custom kernel that we build on our
> own (we just happen to build the kernels in ubuntu) and we use them in
> our testing pipeline with a debian rootfs. FWIW, 5.4 kernels booted fine
> with previous versions of systemd.
>
> My expectation would be that debian's systemd would be able to boot the
> machine even with a custom kernel.
Please do not open bugs for issues happening on custom kernels. Only
Debian kernels are supported, for anything else you'll have to either
figure it out yourself, or pay a contractor to do so.
More information about the Pkg-systemd-maintainers
mailing list