From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] systemd: no need to use qemu for hwdb update
Date: Wed, 22 Jul 2026 07:41:15 +0200 [thread overview]
Message-ID: <DK4UY8M71S6S.4ER6FHTQXGJD@bootlin.com> (raw)
In-Reply-To: <20260721161511.2946619-3-ross.burton@arm.com>
On Tue Jul 21, 2026 at 6:15 PM CEST, Ross Burton via lists.openembedded.org wrote:
> Now that systemd-tools-native gives us a native systemd-hwdb, and the
> database format is known to be hardware-agnostic, we can simply run
> systemd-hwdb directly instead of running it inside qemu-user if we're
> using systemd instead of eudev.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
Hi Ross,
Thanks for your patch.
It looks like we have postinstall failures:
ERROR: core-image-full-cmdline-1.0-r0 do_rootfs: The postinstall intercept hook 'update_udev_hwdb' failed, details in /srv/pokybuild/yocto-worker/genericarm64-alt/build/build/tmp/work/genericarm64-poky-linux/core-image-full-cmdline/1.0/temp/log.do_rootfs
I don't see more logs so far, but it does seem to happen on most build
configurations.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/4148
https://autobuilder.yoctoproject.org/valkyrie/#/builders/10/builds/4165
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/4190
...
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-22 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 16:15 [PATCH 0/2] Use native systemd-hwdb at rootfs time Ross Burton
2026-07-21 16:15 ` [PATCH 1/2] systemd-tools-native: add systemd-hwdb Ross Burton
2026-07-21 16:15 ` [PATCH 2/2] systemd: no need to use qemu for hwdb update Ross Burton
2026-07-22 5:41 ` Mathieu Dubois-Briand [this message]
2026-07-22 9:04 ` [OE-core] " Ross Burton
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=DK4UY8M71S6S.4ER6FHTQXGJD@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/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