From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <bruce.ashfield@gmail.com>, <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] linux-yocto: introduce 6.17 reference kernels
Date: Mon, 27 Oct 2025 10:28:44 +0100 [thread overview]
Message-ID: <DDSZYF5TWBO9.2Z5Y4SR4SE5D8@bootlin.com> (raw)
In-Reply-To: <65b6f4cb57e6738e48560539cf2c0485e0469b65.1761360245.git.bruce.ashfield@gmail.com>
On Sat Oct 25, 2025 at 4:48 AM CEST, Bruce Ashfield via lists.openembedded.org wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> The 6.17 kernel went through quite a bit of testing via
> linux-yocto-dev, so it is a relatively well understood release.
>
> These recipes introduce it as a fully tested reference with the
> potential to replace the EOL 6.16 refs.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
Hi Bruce,
Thanks for your patch. It looks like we do have some issue with qemu
images failing to boot on ARM:
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/qemuarm-oecore/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/qemuarm-oecore/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/parselogs.py", line 185, in test_parselogs
self.assertEqual(errcount, 0, msg=self.msg)
AssertionError: 2 != 0 : Log: /srv/pokybuild/yocto-worker/qemuarm-oecore/build/build/tmp/work/qemuarm-oe-linux-gnueabi/core-image-sato/1.0/target_logs/dmesg
-----------------------
Central error: [ 2.782604] check access for rdinit=/init failed: -2, ignoring
***********************
[ 2.708951] Key type fscrypt-provisioning registered
[ 2.716922] Btrfs loaded, zoned=no, fsverity=no
[ 2.719780] Key type encrypted registered
[ 2.722461] netconsole: network logging started
[ 2.763480] IP-Config: Complete:
[ 2.764617] device=eth0, hwaddr=52:54:00:12:34:02, ipaddr=192.168.7.2, mask=255.255.255.0, gw=192.168.7.1
[ 2.767176] host=192.168.7.2, domain=, nis-domain=(none)
[ 2.768653] bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
[ 2.768746] nameserver0=8.8.8.8
[ 2.773746] clk: Disabling unused clocks
[ 2.782604] check access for rdinit=/init failed: -2, ignoring
[ 2.784414] md: Waiting for all devices to be available before autodetect
[ 2.786070] md: If you don't use raid, use raid=noautodetect
[ 2.787605] md: Autodetecting RAID arrays.
[ 2.788689] md: autorun ...
[ 2.788965] md: ... autorun DONE.
[ 2.863628] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 2.881074] EXT4-fs (vda): mounted filesystem 49485ab8-9460-46e8-bf1c-423f2c03e0bb r/w with ordered data mode. Quota mode: disabled.
[ 2.887371] VFS: Mounted root (ext4 filesystem) on device 253:0.
[ 2.892345] devtmpfs: mounted
[ 3.045885] input: QEMU QEMU USB Tablet as /devices/platform/3f000000.pcie/pci0000:00/0000:00:02.0/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input0
https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2629
Can you have a look at this?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-10-27 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 2:48 [PATCH 0/2] linux-yocto: 6.17 reference kernel bruce.ashfield
2025-10-25 2:48 ` [PATCH 1/2] linux-yocto: introduce 6.17 reference kernels bruce.ashfield
2025-10-27 9:28 ` Mathieu Dubois-Briand [this message]
2025-10-27 12:17 ` [OE-core] " Bruce Ashfield
2025-10-27 12:31 ` Fabio Estevam
2025-10-27 12:33 ` Bruce Ashfield
2025-10-27 12:36 ` Bruce Ashfield
[not found] ` <1872594C74F7A094.2174@lists.openembedded.org>
2025-10-27 12:49 ` Bruce Ashfield
2025-10-25 2:48 ` [PATCH 2/2] linux-yocto/6.17: update CVE exclusions (6.17.5) bruce.ashfield
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=DDSZYF5TWBO9.2Z5Y4SR4SE5D8@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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