From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dVWTq0ZcVz30Jj for ; Mon, 15 Dec 2025 20:13:35 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dVWTl3JqJz2xWj for ; Mon, 15 Dec 2025 20:13:31 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dVWTk3nhcz4x; Mon, 15 Dec 2025 20:13:30 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1765829610; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DHlqBCkhNoaeZNb4VB6nE+9blYiE4J68MXa7nEGMgY4=; b=AcZnOmwAFoOj8u3uVSyNshAH3naTAdKiKZelNJyc3o8ErgI9Tj4ve5RsIryUM6tmhbKRBG KblfyK+eHP41duAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1765829610; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DHlqBCkhNoaeZNb4VB6nE+9blYiE4J68MXa7nEGMgY4=; b=gu3ujAEMbaKqToa5oSb7rI0vmyPufv8PJY0eSU/L9blf9EGMsRb6vW8cO++PxCdNAwCuA3 HySdcqqL4bWkV1eYeZfVAE8O3Yj0gz9vYObNs2aR5Ena7NTs3F/NULPIkXLr7v21/cVxF6 YNc/CFXQguVwSTboFTUouagTk/15KqxNvUtipBUeSNtk8T7U6lOS2+d2O1pFOzPWJcexgQ easAYSh0R4R/QxsL4OVSMB6H7gESb40WVYS1N9z6k/45OPsVMvg66zXjAbppWOB5ee/H2O Bd08zjdHvxmKVJvRz2UE92cnJfl+Nllc4THwgokdlUlgBUZSnQEb5ru+d70vfA== Date: Mon, 15 Dec 2025 20:13:29 +0000 From: Adam Gibbons To: development@lists.ipfire.org, Adolf Belka , Arne Fitzenreiter CC: "IPFire: Development-List" Subject: Re: Kernel 6.18 fist tests... In-Reply-To: <877967ab-d2a1-4109-be5b-1fc42725b6d7@ipfire.org> References: <3420be90-df25-4916-a200-2f05e24320ab@ipfire.org> <348B531B-2DD7-4069-9445-F164B2E40541@ipfire.org> <413858e7-9337-4005-a6d7-98696f615520@ipfire.org> <065b43e5-2054-444a-b9d9-ace745ee29f6@ipfire.org> <877967ab-d2a1-4109-be5b-1fc42725b6d7@ipfire.org> Message-ID: Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----FW8BCWT9H1DXWI302SJLM3ROBOF4HF Content-Transfer-Encoding: 7bit ------FW8BCWT9H1DXWI302SJLM3ROBOF4HF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Arne, Adolf, all, Just chiming in with my own testing experience=2E I updated to the latest nightly (which has the dracut-ng initqueue fix) an= d then applied the 6=2E18 kernel=2E Small things I hit: the readme had "-C = " instead of "-C /" for the tar command, and there was a typo in the dracut= command ("regenrate" instead of "regenerate")=2E Easy fixes, though=2E :) Since then it's been running solidly for over 24 hours now=2E No odd behav= iour at all =E2=80=93 everything feels normal, and Observium (which monitor= s the box) isn't showing anything unusual either=2E I've noticed that Linux 6=2E18=2E1 was released recently too, so I'll grab= Arne's build of that next and give it a go soon=2E For reference, my current test box is an older i5-4200U with four Intel I2= 11 NICs=2E I also have a newer Intel N305 (with I226-V NICs) ready, so I'll= move the test over to that soon =E2=80=93 mainly curious to see how p-stat= es and power management are behaving in 6=2E18=2E Thanks Arne for building these, really helpful to get it tested early=2E Cheers, Adam On 15 December 2025 11:46:18 GMT, Adolf Belka = wrote: >Hi Arne, > >With the patch fix for the initqueue issue in place I have been running I= PFire with that new kernel and testing out various things=2E > >I am not sure what aspects of IPfire would be most likely to be affected = by the change to the kernel, so I have just been testing various elements o= f IPFire=2E Everything I have tried has worked without any issues=2E > >OpenVPN, WireGuard and IPSec connections have all worked, both RW and N2N= with the latter being between a system with 6=2E18=2E0 and all other IPFir= e VM's with 6=2E12=2E58 > >Regards, > >Adolf=2E > > >On 12/12/2025 14:57, Adolf Belka wrote: >> Hi all, >>=20 >> On 12/12/2025 12:30, Adolf Belka wrote: >>> Hi Michael & all, >>>=20 >>> On 11/12/2025 23:35, Adolf Belka wrote: >>>> Hi Michael, >>>>=20 >>>> On 11/12/2025 22:01, Michael Tremer wrote: >>>>> Hello Adolf, >>>>>=20 >>>>> The initqueue module is probably quite important=2E As far as I know= it kind of replaces some systemd functionality which we don=E2=80=99t have= =2E >>>>>=20 >>>>> But looking at our root file, it is adding some systemd unit files: >>>>>>> =C2=A0=C2=A0 https://git=2Eipfire=2Eorg/?p=3Dipfire-2=2Ex=2Egit;a= =3Dblob;f=3Dconfig/rootfiles/common/dracut-ng;hb=3Dd656b7af6411d0306513b853= a552f56d6713c174#l484 >>>>>=20 >>>=20 >>> Three of those files are related to systemd but one is the same as use= d to be in the base collection but was moved to this separate set in versio= n 108=2E >>>=20 >>> When I did the package update, I commented out all new entries in the = rootfile that weren't previously in the rootfile=2E Therefore the initqueue= set are all commented out but as it had been moved out from the base it ne= eded to be included=2E >>>=20 >>> I am running a build with all of the initqueue entries uncommented (al= though probably, the ones related to systemd could be left commented) and I= will then do an install with that build and then try the kernel update fol= lowed by the dracut command again and see if it then works for the initqueu= e module=2E >>>=20 >>> Well report back when I have the results=2E >>=20 >> I can report that all required modules are now able to be included, inc= luding initqueue and all modules are now correctly installed including btrf= s, lvm and mdraid that had a problem before=2E >>=20 >> I will submit a patch to correct the dracut-ng rootfile=2E >>=20 >> Regards, >>=20 >> Adolf=2E >>=20 >>>=20 >>> Regards, >>>=20 >>> Adolf=2E >>>=20 >>>=20 >>>>> We might have found a breaking change in dracut-ng if we don=E2=80= =99t properly support mdraid any more=2E >>>>=20 >>>> but that should then be presumably raised as an issue with dracut-ng = as if it worked with the old dracut it should work with dracut-ng as versio= n 100 was said to be a drop-in replacement for the old version=2E >>>>=20 >>>> We are currently on version 108 and I just found in the changelog for= that version the following change=2E >>>>=20 >>>> -------------------------- >>>> feat(initqueue): factor out initqueue into its own module >>>> This PR allows excluding dracut initqueue module, while >>>> including the base or the dracut-systemd module=2E >>>>=20 >>>> Factoring out functionality into its own module >>>> allows to better control to include or exclude the >>>> functionality=2E >>>> -------------------------- >>>>=20 >>>> https://github=2Ecom/dracut-ng/dracut-ng/commit/3daf67830d8db3b12bc45= eef9f8f29f606192db9 >>>>=20 >>>> So it looks like it is a module that has to be explicitly specified n= ow whereas in the past it was part of dracut base=2E >>>>=20 >>>> Regards, >>>>=20 >>>> Adolf=2E >>>>=20 >>>>>=20 >>>>> Lacking support for btrfs in the initramdisk could be less severe, b= ut that also needs to be tested=2E @Stefan, will you do this for c199? >>>>>=20 >>>>> -Michael >>>>>=20 >>>>>> On 11 Dec 2025, at 18:04, Adolf Belka = wrote: >>>>>>=20 >>>>>> Hi Arne, >>>>>>=20 >>>>>> On 11/12/2025 18:28, Adolf Belka wrote: >>>>>>> Hi All, >>>>>>> On 11/12/2025 18:20, Adolf Belka wrote: >>>>>>>> Hi Arne, >>>>>>>>=20 >>>>>>>> I have tried it out on a vm clone running CU199 Testing=2E >>>>>>>>=20 >>>>>>>> In the readme=2Etxt file I think you meant to have >>>>>>>>=20 >>>>>>>> tar xvaf KERNEL-ARCHIV=2Etar=2Exz -C / >>>>>>>>=20 >>>>>>>> instead of >>>>>>>>=20 >>>>>>>> tar xvaf KERNEL-ARCHIV=2Etar=2Exz -C \ >>>>>>>>=20 >>>>>>>> At least it only extracted for me with the / and not the \=2E >>>>>>>>=20 >>>>>>>> I then ran the dracut command and got the following messages=2E >>>>>>>>=20 >>>>>>>> sudo dracut --regenerate-all --force >>>>>>>> dracut[I]: Executing: /usr/bin/dracut --kver=3D6=2E12=2E58-ipfire= --force >>>>>>>> dracut[E]: Module 'btrfs' depends on module 'initqueue', which ca= n't be installed >>>>>>>> dracut[E]: Module 'lvm' depends on module 'initqueue', which can'= t be installed >>>>>>>> dracut[E]: Module 'mdraid' depends on module 'initqueue', which c= an't be installed >>>>>>>> dracut[I]: *** Including module: modsign *** >>>>>>>> dracut[I]: *** Including module: i18n *** >>>>>>>> dracut[I]: *** Including module: btrfs *** >>>>>>>> dracut[I]: *** Including module: dm *** >>>>>>>> dracut[I]: *** Including module: fs-lib *** >>>>>>>> dracut[I]: *** Including module: kernel-modules *** >>>>>>>> dracut[I]: *** Including module: kernel-modules-extra *** >>>>>>>> dracut[I]: *** Including module: lvm *** >>>>>>>> dracut[I]: *** Including module: mdraid *** >>>>>>>> dracut[I]: *** Including module: qemu *** >>>>>>>> dracut[I]: *** Including module: rootfs-block *** >>>>>>>> dracut[I]: *** Including module: terminfo *** >>>>>>>> dracut[I]: *** Including module: udev-rules *** >>>>>>>> dracut[I]: *** Including module: base *** >>>>>>>> dracut[I]: *** Including modules done *** >>>>>>>> dracut[I]: *** Installing kernel module dependencies *** >>>>>>>> dracut[I]: *** Installing kernel module dependencies done *** >>>>>>>> dracut[I]: *** Resolving executable dependencies *** >>>>>>>> dracut[I]: *** Resolving executable dependencies done *** >>>>>>>> dracut[I]: *** Generating early-microcode cpio image *** >>>>>>>> dracut[I]: *** Constructing AuthenticAMD=2Ebin *** >>>>>>>> dracut[I]: *** Constructing GenuineIntel=2Ebin *** >>>>>>>> dracut[I]: *** Store current command line parameters *** >>>>>>>> dracut[I]: *** Creating image file '/boot/initramfs-6=2E12=2E58-i= pfire=2Eimg=2Etmp' *** >>>>>>>> dracut[I]: *** Hardlinking files *** >>>>>>>> dracut[I]: *** Hardlinking files done *** >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Not sure about the "module 'initqueue', which can't be installed"= bits=2E >>>>>>>>=20 >>>>>>>> After the above last line I then got >>>>>>>>=20 >>>>>>>> cp: error writing '/boot/initramfs-6=2E12=2E58-ipfire=2Eimg=2Etmp= ': No space left on device >>>>>>>>=20 >>>>>>>> So I suspect I need to make the IPFire vm disk larger=2E >>>>>>> The problem was that I made a clone of a system that I had tested = out upgrading from CU150 to CU198 and the boot size was obviously smaller b= ack in CU150 as I only have 110MB but the more current systems have 488MB s= o I will create a clone of one of my newer systems and repeat the test=2E >>>>>>=20 >>>>>> Repeated with a newer IPFire vm which had a 488MB boot partition an= d the dracut section went fine with no problems beside the initqueue module= not being able to be installed=2E However that did not seem to cause a pro= blem with the grub-mkconfig command or the subsequent reboot=2E >>>>>>=20 >>>>>> I will evaluate the install tomorrow to check if anything has a pro= blem=2E >>>>>>=20 >>>>>> Regards, >>>>>>=20 >>>>>> Adolf=2E >>>>>>=20 >>>>>>=20 >>>>>>> Regards, >>>>>>> Adolf=2E >>>>>>>>=20 >>>>>>>> Will give that a try later but would like to know if there is any= thing I need to do with regard to the initqueue module that is mentioned in= the dracut output=2E >>>>>>>>=20 >>>>>>>> Regards, >>>>>>>>=20 >>>>>>>> Adolf=2E >>>>>>>>=20 >>>>>>>> On 11/12/2025 14:57, Adam Gibbons wrote: >>>>>>>>> Nice! >>>>>>>>>=20 >>>>>>>>> I will test this over the weekend=2E >>>>>>>>>=20 >>>>>>>>> Thanks, >>>>>>>>> Adam >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> On 11 December 2025 12:00:23 GMT, Arne Fitzenreiter wrote: >>>>>>>>>=20 >>>>>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Hi, >>>>>>>>>=20 >>>>>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 i have compiled a first test kernel 6= =2E18 for x86_64=2E >>>>>>>>>=20 >>>>>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 https://people=2Eipfire=2Eorg/~arne_f/h= ighly-experimental/kernel/ >>>>>>>>>=20 >>>>>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 please help testing and report your fin= dings=2E=2E=2E >>>>>>>>>=20 >>>>>>>>> =C2=A0=C2=A0=C2=A0=C2=A0 Arne >>>>>=20 >>>>>=20 >>>>=20 >>>=20 >>=20 > > ------FW8BCWT9H1DXWI302SJLM3ROBOF4HF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Arne, Adolf, all,
Just chi= ming in with my own testing experience=2E

I updated to the latest ni= ghtly (which has the dracut-ng initqueue fix) and then applied the 6=2E18 k= ernel=2E Small things I hit: the readme had "-C " instead of "-C /" for the= tar command, and there was a typo in the dracut command ("regenrate" inste= ad of "regenerate")=2E Easy fixes, though=2E :)

Since then it's been= running solidly for over 24 hours now=2E No odd behaviour at all =E2=80=93= everything feels normal, and Observium (which monitors the box) isn't show= ing anything unusual either=2E

I've noticed that Linux 6=2E18=2E1 wa= s released recently too, so I'll grab Arne's build of that next and give it= a go soon=2E

For reference, my current test box is an older i5-4200= U with four Intel I211 NICs=2E I also have a newer Intel N305 (with I226-V = NICs) ready, so I'll move the test over to that soon =E2=80=93 mainly curio= us to see how p-states and power management are behaving in 6=2E18=2E
Thanks Arne for building these, really helpful to get it tested early=2E<= br>
Cheers,
Adam


On 15 December 2025 11:46:18 GMT, Adolf Belka <adolf=2Ebelka@ipfir= e=2Eorg> wrote:
Hi Arne,

With the patch fix=
 for the initqueue issue in place I have been running IPFire with that new =
kernel and testing out various things=2E

I am not sure what aspects =
of IPfire would be most likely to be affected by the change to the kernel, =
so I have just been testing various elements of IPFire=2E Everything I have=
 tried has worked without any issues=2E

OpenVPN, WireGuard and IPSec=
 connections have all worked, both RW and N2N with the latter being between=
 a system with 6=2E18=2E0 and all other IPFire VM's with 6=2E12=2E58
Regards,

Adolf=2E


On 12/12/2025 14:57, Adolf Belka wrote=
:
Hi all,

On 12/12/2025 12:30, Adolf Belka wrote:
Hi Michael &=
 all,

On 11/12/2025 23:35, Adolf Belka wrote:
Hi Michael,

On=
 11/12/2025 22:01, Michael Tremer wrote:
Hello Adolf,

The initqueue=
 module is probably quite important=2E As far as I know it kind of replaces=
 some systemd functionality which we don=E2=80=99t have=2E

But looki=
ng at our root file, it is adding some systemd unit files:


Three of those files are related to systemd but one is t=
he same as used to be in the base collection but was moved to this separate=
 set in version 108=2E

When I did the package update, I commented ou=
t all new entries in the rootfile that weren't previously in the rootfile=
=2E Therefore the initqueue set are all commented out but as it had been mo=
ved out from the base it needed to be included=2E

I am running a bui=
ld with all of the initqueue entries uncommented (although probably, the on=
es related to systemd could be left commented) and I will then do an instal=
l with that build and then try the kernel update followed by the dracut com=
mand again and see if it then works for the initqueue module=2E

Well=
 report back when I have the results=2E

I can report that all required modules are now able to be included= , including initqueue and all modules are now correctly installed including= btrfs, lvm and mdraid that had a problem before=2E

I will submit a = patch to correct the dracut-ng rootfile=2E

Regards,

Adolf=2E<= br>

Regards,

Adolf=2E


<= div dir=3D"auto">We might have found a breaking change in dracut-ng if we d= on=E2=80=99t properly support mdraid any more=2E

but that should then be presumably raised as an issue wit= h dracut-ng as if it worked with the old dracut it should work with dracut-= ng as version 100 was said to be a drop-in replacement for the old version= =2E

We are currently on version 108 and I just found in the changelo= g for that version the following change=2E
feat(initqueue): factor out i= nitqueue into its own module
This PR allows excluding dracut initqueue m= odule, while
including the base or the dracut-systemd module=2E

F= actoring out functionality into its own module
allows to better control = to include or exclude the
functionality=2E
https://github=2Ecom/dracut-ng/dracut-ng/commit/3daf67830d8db3b12bc45eef9f= 8f29f606192db9

So it looks like it is a module that has to be ex= plicitly specified now whereas in the past it was part of dracut base=2E
Regards,

Adolf=2E


Lacking support for btrfs in the ini= tramdisk could be less severe, but that also needs to be tested=2E @Stefan,= will you do this for c199?

-Michael

On 11 Dec 2025, at 18:04,= Adolf Belka <adolf=2Ebelka@ipfire=2Eorg> wrote:

Hi Arne,
<= br>On 11/12/2025 18:28, Adolf Belka wrote:
Hi All,
On 11/12/2025 18:20, Ad= olf Belka wrote:
Hi Arne,

I have tried it out on a vm clone running CU= 199 Testing=2E

In the readme=2Etxt file I think you meant to have
tar xvaf KERNEL-ARCHIV=2Etar=2Exz -C /

instead of

tar xv= af KERNEL-ARCHIV=2Etar=2Exz -C \

At least it only extracted for me w= ith the / and not the \=2E

I then ran the dracut command and got the= following messages=2E

sudo dracut --regenerate-all --force
dracu= t[I]: Executing: /usr/bin/dracut --kver=3D6=2E12=2E58-ipfire --force
dra= cut[E]: Module 'btrfs' depends on module 'initqueue', which can't be instal= led
dracut[E]: Module 'lvm' depends on module 'initqueue', which can't b= e installed
dracut[E]: Module 'mdraid' depends on module 'initqueue', wh= ich can't be installed
dracut[I]: *** Including module: modsign ***
d= racut[I]: *** Including module: i18n ***
dracut[I]: *** Including module= : btrfs ***
dracut[I]: *** Including module: dm ***
dracut[I]: *** In= cluding module: fs-lib ***
dracut[I]: *** Including module: kernel-modul= es ***
dracut[I]: *** Including module: kernel-modules-extra ***
drac= ut[I]: *** Including module: lvm ***
dracut[I]: *** Including module: md= raid ***
dracut[I]: *** Including module: qemu ***
dracut[I]: *** Inc= luding module: rootfs-block ***
dracut[I]: *** Including module: terminf= o ***
dracut[I]: *** Including module: udev-rules ***
dracut[I]: *** = Including module: base ***
dracut[I]: *** Including modules done ***
= dracut[I]: *** Installing kernel module dependencies ***
dracut[I]: *** = Installing kernel module dependencies done ***
dracut[I]: *** Resolving = executable dependencies ***
dracut[I]: *** Resolving executable dependen= cies done ***
dracut[I]: *** Generating early-microcode cpio image ***dracut[I]: *** Constructing AuthenticAMD=2Ebin ***
dracut[I]: *** Cons= tructing GenuineIntel=2Ebin ***
dracut[I]: *** Store current command lin= e parameters ***
dracut[I]: *** Creating image file '/boot/initramfs-6= =2E12=2E58-ipfire=2Eimg=2Etmp' ***
dracut[I]: *** Hardlinking files ***<= br>dracut[I]: *** Hardlinking files done ***


Not sure about the = "module 'initqueue', which can't be installed" bits=2E

After the abo= ve last line I then got

cp: error writing '/boot/initramfs-6=2E12=2E= 58-ipfire=2Eimg=2Etmp': No space left on device

So I suspect I need = to make the IPFire vm disk larger=2E
The problem was that I made a clone of a system that I had tested out upg= rading from CU150 to CU198 and the boot size was obviously smaller back in = CU150 as I only have 110MB but the more current systems have 488MB so I wil= l create a clone of one of my newer systems and repeat the test=2E

Repeated with a newer IPFire vm which h= ad a 488MB boot partition and the dracut section went fine with no problems= beside the initqueue module not being able to be installed=2E However that= did not seem to cause a problem with the grub-mkconfig command or the subs= equent reboot=2E

I will evaluate the install tomorrow to check if an= ything has a problem=2E

Regards,

Adolf=2E


Regards,
A= dolf=2E

Will give that a try later but would like to know if there is any= thing I need to do with regard to the initqueue module that is mentioned in= the dracut output=2E

Regards,

Adolf=2E

On 11/12/2025 = 14:57, Adam Gibbons wrote:
Nice!

I will test this over the weekend=2E<= br>
Thanks,
Adam


On 11 December 2025 12:00:23 GMT, Arne Fi= tzenreiter <arne_f@ipfire=2Eorg> wrote:

   &nbs= p; Hi,

     i have compiled a first test kernel = 6=2E18 for x86_64=2E

     https://people=2Eip= fire=2Eorg/~arne_f/highly-experimental/kernel/ <https://people=2E= ipfire=2Eorg/~arne_f/highly-experimental/kernel/>

  = ;   please help testing and report your findings=2E=2E=2E

=      Arne







------FW8BCWT9H1DXWI302SJLM3ROBOF4HF--