From: adrian.freihofer@gmail.com
To: mathieu.dubois-briand@bootlin.com, adrian.freihofer@siemens.com,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] kernel.bbclass: remove dependency on initramfs when not bundled
Date: Sun, 22 Feb 2026 13:11:39 +0100 [thread overview]
Message-ID: <98d2f7fa5179720e9579af4e55af7af49abe2a5e.camel@gmail.com> (raw)
In-Reply-To: <DGIA36GNR4J5.1T52ZELIA28Y9@bootlin.com>
On Wed, 2026-02-18 at 18:53 +0100, Mathieu Dubois-Briand via
lists.openembedded.org wrote:
> On Tue Feb 17, 2026 at 6:32 PM CET, Adrian Freihofer via
> lists.openembedded.org wrote:
> > From: Adrian Freihofer <adrian.freihofer@siemens.com>
> >
> > Previously, the kernel recipe depended on the initramfs image even
> > when
> > INITRAMFS_IMAGE_BUNDLE was not enabled. This caused the kernel to
> > be
> > rebuilt whenever the initramfs image changed, regardless of whether
> > the
> > kernel actually included the initramfs.
> >
> > The problematic chain was:
> > linux:do_deploy ->
> > linux:do_bundle_initramfs ->
> > image-initramfs:do_image_complete
> >
> > The original intent (acc. to the comment) was to ensure the
> > initramfs
> > image was available for tools like wic. However, apart from
> > bundling the
> > initramfs in the kernel, there is probably no reason why the kernel
> > should depend on the initramfs. And it is therefore simply wrong if
> > it
> > does so anyway. Thus, use cases that may be broken by these change
> > are
> > based on a bug, not a feature. This needs to be fixed by adding a
> > dependency on the initramfs in the right place, not in the kernel
> > where
> > this destroys the kernel's sstate-caching.
> >
> > Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> > ---
>
> Hi Adrian,
>
> It looks like this is causing some build issues. I only saw them on
> ARM64 so far:
>
> ERROR: core-image-full-cmdline-1.0-r0 do_image_wic: Execution of
> '/srv/pokybuild/yocto-worker/genericarm64-
> alt/build/build/tmp/work/genericarm64-poky-linux/core-image-full-
> cmdline/1.0/temp/run.do_image_wic.2336354' failed with exit code 1
> ...
> > INFO: Creating image(s)...
> ...
> > ERROR: _exec_cmd: cp -v -p /srv/pokybuild/yocto-
> > worker/genericarm64-
> > alt/build/build/tmp/deploy/images/genericarm64/core-image-
> > initramfs-boot-genericarm64.cpio.gz /srv/pokybuild/yocto-
> > worker/genericarm64-alt/build/build/tmp/work/genericarm64-poky-
> > linux/core-image-full-cmdline/1.0/tmp-wic/hdd/boot returned '1'
> > instead of 0
> > output: cp: cannot stat '/srv/pokybuild/yocto-worker/genericarm64-
> > alt/build/build/tmp/deploy/images/genericarm64/core-image-
> > initramfs-boot-genericarm64.cpio.gz': No such file or directory
> >
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/3228
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/60/builds/3202
>
> Can you have a look at what is going wrong?
Thank you!
Here is a v2 which should address this issue:
https://lists.openembedded.org/g/openembedded-core/message/231629
Adrian
>
> Thanks,
> Mathieu
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#231315):
> https://lists.openembedded.org/g/openembedded-core/message/231315
> Mute This Topic: https://lists.openembedded.org/mt/117860606/4454582
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-core/unsub [
> adrian.freihofer@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2026-02-22 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 17:32 [PATCH] kernel.bbclass: remove dependency on initramfs when not bundled AdrianF
2026-02-18 17:53 ` [OE-core] " Mathieu Dubois-Briand
2026-02-22 12:11 ` adrian.freihofer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98d2f7fa5179720e9579af4e55af7af49abe2a5e.camel@gmail.com \
--to=adrian.freihofer@gmail.com \
--cc=adrian.freihofer@siemens.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox