diff mbox series

[1/5] poky: bump default kernel reference to 6.16

Message ID 0074b1cd80c242493c1e50d9ff58cc4427272a50.1757088383.git.bruce.ashfield@gmail.com
State New
Headers show
Series [1/5] poky: bump default kernel reference to 6.16 | expand

Commit Message

Bruce Ashfield Sept. 5, 2025, 4:09 p.m. UTC
From: Bruce Ashfield <bruce.ashfield@gmail.com>

Bumping the reference kernel to 6.16. We keep the alt distro
on 6.12 for better coverage.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta-poky/conf/distro/poky-tiny.conf | 2 +-
 meta-poky/conf/distro/poky.conf      | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

Comments

patchtest@automation.yoctoproject.org Sept. 5, 2025, 4:17 p.m. UTC | #1
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:

---
Testing patch /home/patchtest/share/mboxes/1-5-poky-bump-default-kernel-reference-to-6.16.patch

FAIL: test target mailing list: Series sent to the wrong mailing list or some patches from the series correspond to different mailing lists (test_mbox.TestMbox.test_target_mailing_list)

PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence)
PASS: test commit message user tags (test_mbox.TestMbox.test_commit_message_user_tags)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)

SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint)
SKIP: pretest src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.pretest_src_uri_left_files)
SKIP: test CVE check ignore: No modified recipes or older target branch, skipping test (test_metadata.TestMetadata.test_cve_check_ignore)
SKIP: test CVE tag format: No new CVE patches introduced (test_patch.TestPatch.test_cve_tag_format)
SKIP: test Signed-off-by presence: No new CVE patches introduced (test_patch.TestPatch.test_signed_off_by_presence)
SKIP: test Upstream-Status presence: No new CVE patches introduced (test_patch.TestPatch.test_upstream_status_presence_format)
SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum modified not mentioned: No modified recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.test_src_uri_left_files)
SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence)

---

Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this
email with an explanation of why the patch should be accepted. If you
believe these results are due to an error in patchtest, please submit a
bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
under 'Yocto Project Subprojects'). For more information on specific
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
you!
Marko, Peter Sept. 19, 2025, 12:34 p.m. UTC | #2
Hello Bruce,

This upgrade broke build of external kernel modules for powerpc.
Yocto test devtool.DevtoolTest.test_devtool_kernelmodule is failing.

We have prepared a patch for upstream kernel.
https://lore.kernel.org/all/20250919121417.1601020-1-alexander.sverdlin@siemens.com/
But I guess it will take lot of time to get picked there, then backported to 6.16, tagged and finally this tag picked by yocto.
Is there a process to pick this patch already now to keep the pipeline green?

Peter

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Bruce Ashfield via
> lists.openembedded.org
> Sent: Friday, September 5, 2025 18:09
> To: richard.purdie@linuxfoundation.org
> Cc: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 1/5] poky: bump default kernel reference to 6.16
> 
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Bumping the reference kernel to 6.16. We keep the alt distro
> on 6.12 for better coverage.
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
>  meta-poky/conf/distro/poky-tiny.conf | 2 +-
>  meta-poky/conf/distro/poky.conf      | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-poky/conf/distro/poky-tiny.conf b/meta-poky/conf/distro/poky-
> tiny.conf
> index 81153b3b36..84baef347c 100644
> --- a/meta-poky/conf/distro/poky-tiny.conf
> +++ b/meta-poky/conf/distro/poky-tiny.conf
> @@ -41,7 +41,7 @@ FULL_OPTIMIZATION = "-Os"
>  # Distro config is evaluated after the machine config, so we have to explicitly
>  # set the kernel provider to override a machine config.
>  PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
> -PREFERRED_VERSION_linux-yocto-tiny ?= "6.12%"
> +PREFERRED_VERSION_linux-yocto-tiny ?= "6.16%"
> 
>  # We can use packagegroup-core-boot, but in the future we may need a new
> packagegroup-core-tiny
>  #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
> index b12df2be70..d86630b153 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -19,8 +19,8 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-
> module-af-packet"
> 
>  DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}
> ${POKY_DEFAULT_DISTRO_FEATURES}"
> 
> -PREFERRED_VERSION_linux-yocto ?= "6.12%"
> -PREFERRED_VERSION_linux-yocto-rt ?= "6.12%"
> +PREFERRED_VERSION_linux-yocto ?= "6.16%"
> +PREFERRED_VERSION_linux-yocto-rt ?= "6.16%"
> 
>  SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-
> ${TUNE_PKGARCH}-${MACHINE}"
>  SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
> --
> 2.39.2
Bruce Ashfield Sept. 19, 2025, 12:41 p.m. UTC | #3
On Fri, Sep 19, 2025 at 8:35 AM Marko, Peter <Peter.Marko@siemens.com>
wrote:

> Hello Bruce,
>
> This upgrade broke build of external kernel modules for powerpc.
> Yocto test devtool.DevtoolTest.test_devtool_kernelmodule is failing.
>
> We have prepared a patch for upstream kernel.
>
> https://lore.kernel.org/all/20250919121417.1601020-1-alexander.sverdlin@siemens.com/
> But I guess it will take lot of time to get picked there, then backported
> to 6.16, tagged and finally this tag picked by yocto.
> Is there a process to pick this patch already now to keep the pipeline
> green?
>

Yes, if you submit it to the linux-yocto mailing list (you need to
subscribe), I can
merge it directly to linux-yocto and send a SRCREV bump to the list.

I'll carry the patch to any newer kernel that I do, until it merges
upstream and
I'll automatically drop it at that point.

Bruce



> Peter
>
> > -----Original Message-----
> > From: openembedded-core@lists.openembedded.org <openembedded-
> > core@lists.openembedded.org> On Behalf Of Bruce Ashfield via
> > lists.openembedded.org
> > Sent: Friday, September 5, 2025 18:09
> > To: richard.purdie@linuxfoundation.org
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH 1/5] poky: bump default kernel reference to
> 6.16
> >
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Bumping the reference kernel to 6.16. We keep the alt distro
> > on 6.12 for better coverage.
> >
> > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> > ---
> >  meta-poky/conf/distro/poky-tiny.conf | 2 +-
> >  meta-poky/conf/distro/poky.conf      | 4 ++--
> >  2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta-poky/conf/distro/poky-tiny.conf
> b/meta-poky/conf/distro/poky-
> > tiny.conf
> > index 81153b3b36..84baef347c 100644
> > --- a/meta-poky/conf/distro/poky-tiny.conf
> > +++ b/meta-poky/conf/distro/poky-tiny.conf
> > @@ -41,7 +41,7 @@ FULL_OPTIMIZATION = "-Os"
> >  # Distro config is evaluated after the machine config, so we have to
> explicitly
> >  # set the kernel provider to override a machine config.
> >  PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
> > -PREFERRED_VERSION_linux-yocto-tiny ?= "6.12%"
> > +PREFERRED_VERSION_linux-yocto-tiny ?= "6.16%"
> >
> >  # We can use packagegroup-core-boot, but in the future we may need a new
> > packagegroup-core-tiny
> >  #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
> > diff --git a/meta-poky/conf/distro/poky.conf
> b/meta-poky/conf/distro/poky.conf
> > index b12df2be70..d86630b153 100644
> > --- a/meta-poky/conf/distro/poky.conf
> > +++ b/meta-poky/conf/distro/poky.conf
> > @@ -19,8 +19,8 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-
> > module-af-packet"
> >
> >  DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}
> > ${POKY_DEFAULT_DISTRO_FEATURES}"
> >
> > -PREFERRED_VERSION_linux-yocto ?= "6.12%"
> > -PREFERRED_VERSION_linux-yocto-rt ?= "6.12%"
> > +PREFERRED_VERSION_linux-yocto ?= "6.16%"
> > +PREFERRED_VERSION_linux-yocto-rt ?= "6.16%"
> >
> >  SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-
> > ${TUNE_PKGARCH}-${MACHINE}"
> >  SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
> > --
> > 2.39.2
>
>
Bruce Ashfield Sept. 19, 2025, 12:48 p.m. UTC | #4
On Fri, Sep 19, 2025 at 8:42 AM Bruce Ashfield via lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:

>
>
> On Fri, Sep 19, 2025 at 8:35 AM Marko, Peter <Peter.Marko@siemens.com>
> wrote:
>
>> Hello Bruce,
>>
>> This upgrade broke build of external kernel modules for powerpc.
>> Yocto test devtool.DevtoolTest.test_devtool_kernelmodule is failing.
>>
>> We have prepared a patch for upstream kernel.
>>
>> https://lore.kernel.org/all/20250919121417.1601020-1-alexander.sverdlin@siemens.com/
>> But I guess it will take lot of time to get picked there, then backported
>> to 6.16, tagged and finally this tag picked by yocto.
>> Is there a process to pick this patch already now to keep the pipeline
>> green?
>>
>
> Yes, if you submit it to the linux-yocto mailing list (you need to
> subscribe), I can
> merge it directly to linux-yocto and send a SRCREV bump to the list.
>
> I'll carry the patch to any newer kernel that I do, until it merges
> upstream and
> I'll automatically drop it at that point.
>

What is interesting is that we had a crtres patch for powerpc for many
years,
but "recently" (2024) dropped it:

https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-6.12&id=3cf758061025b9284ddfb1259f79860666737302

And that dropped patch should have been part of several reference kernels
since
that commit. Just so I know, this is something that has been passing on all
reference kernels and just broke on 6.16 ?

Something must have changed upstream to bring the breakage back! Your
fix is simpler than the old one we had, so that's progress :)

Bruce



>
> Bruce
>
>
>
>> Peter
>>
>> > -----Original Message-----
>> > From: openembedded-core@lists.openembedded.org <openembedded-
>> > core@lists.openembedded.org> On Behalf Of Bruce Ashfield via
>> > lists.openembedded.org
>> > Sent: Friday, September 5, 2025 18:09
>> > To: richard.purdie@linuxfoundation.org
>> > Cc: openembedded-core@lists.openembedded.org
>> > Subject: [OE-core] [PATCH 1/5] poky: bump default kernel reference to
>> 6.16
>> >
>> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
>> >
>> > Bumping the reference kernel to 6.16. We keep the alt distro
>> > on 6.12 for better coverage.
>> >
>> > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
>> > ---
>> >  meta-poky/conf/distro/poky-tiny.conf | 2 +-
>> >  meta-poky/conf/distro/poky.conf      | 4 ++--
>> >  2 files changed, 3 insertions(+), 3 deletions(-)
>> >
>> > diff --git a/meta-poky/conf/distro/poky-tiny.conf
>> b/meta-poky/conf/distro/poky-
>> > tiny.conf
>> > index 81153b3b36..84baef347c 100644
>> > --- a/meta-poky/conf/distro/poky-tiny.conf
>> > +++ b/meta-poky/conf/distro/poky-tiny.conf
>> > @@ -41,7 +41,7 @@ FULL_OPTIMIZATION = "-Os"
>> >  # Distro config is evaluated after the machine config, so we have to
>> explicitly
>> >  # set the kernel provider to override a machine config.
>> >  PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
>> > -PREFERRED_VERSION_linux-yocto-tiny ?= "6.12%"
>> > +PREFERRED_VERSION_linux-yocto-tiny ?= "6.16%"
>> >
>> >  # We can use packagegroup-core-boot, but in the future we may need a
>> new
>> > packagegroup-core-tiny
>> >  #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
>> > diff --git a/meta-poky/conf/distro/poky.conf
>> b/meta-poky/conf/distro/poky.conf
>> > index b12df2be70..d86630b153 100644
>> > --- a/meta-poky/conf/distro/poky.conf
>> > +++ b/meta-poky/conf/distro/poky.conf
>> > @@ -19,8 +19,8 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-
>> > module-af-packet"
>> >
>> >  DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}
>> > ${POKY_DEFAULT_DISTRO_FEATURES}"
>> >
>> > -PREFERRED_VERSION_linux-yocto ?= "6.12%"
>> > -PREFERRED_VERSION_linux-yocto-rt ?= "6.12%"
>> > +PREFERRED_VERSION_linux-yocto ?= "6.16%"
>> > +PREFERRED_VERSION_linux-yocto-rt ?= "6.16%"
>> >
>> >  SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-
>> > ${TUNE_PKGARCH}-${MACHINE}"
>> >  SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
>> > --
>> > 2.39.2
>>
>>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#223742):
> https://lists.openembedded.org/g/openembedded-core/message/223742
> Mute This Topic: https://lists.openembedded.org/mt/115084892/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
Marko, Peter Sept. 19, 2025, 12:55 p.m. UTC | #5
(damn outlook and html prevents me to properly quote this below, sorry)

The commit description is not ideal and we struggle to fully understand why it was not failing before.

Maybe it was not being built and new config changes trigger it now?


This also seems to be a missed line in 214c0eea43b2ea66bcd6467ea57e47ce8874191b from last year.

As it says "This commit prepares for supporting the building of external modules..." maybe some new commits built on this feature and this broke at that time because not all places were properly prepared.

I’ll probably wait until it gets merged to kernel master before submitting to linux-yocto.

Peter


From: Bruce Ashfield <bruce.ashfield@gmail.com>
Sent: Friday, September 19, 2025 14:49
To: bruce.ashfield@gmail.com
Cc: Marko, Peter (FT D EU SK BFS1) <Peter.Marko@siemens.com>; openembedded-core@lists.openembedded.org; Sverdlin, Alexander (SI B PRO TI EAC CCP) <alexander.sverdlin@siemens.com>; Freihofer, Adrian (SI B PRO TI EAC CCP) <adrian.freihofer@siemens.com>; richard.purdie@linuxfoundation.org
Subject: Re: [OE-core] [PATCH 1/5] poky: bump default kernel reference to 6.16



On Fri, Sep 19, 2025 at 8:42 AM Bruce Ashfield via lists.openembedded.org<http://lists.openembedded.org> <bruce.ashfield=gmail.com@lists.openembedded.org<mailto:gmail.com@lists.openembedded.org>> wrote:


On Fri, Sep 19, 2025 at 8:35 AM Marko, Peter <Peter.Marko@siemens.com<mailto:Peter.Marko@siemens.com>> wrote:
Hello Bruce,

This upgrade broke build of external kernel modules for powerpc.
Yocto test devtool.DevtoolTest.test_devtool_kernelmodule is failing.

We have prepared a patch for upstream kernel.
https://lore.kernel.org/all/20250919121417.1601020-1-alexander.sverdlin@siemens.com/
But I guess it will take lot of time to get picked there, then backported to 6.16, tagged and finally this tag picked by yocto.
Is there a process to pick this patch already now to keep the pipeline green?

Yes, if you submit it to the linux-yocto mailing list (you need to subscribe), I can
merge it directly to linux-yocto and send a SRCREV bump to the list.

I'll carry the patch to any newer kernel that I do, until it merges upstream and
I'll automatically drop it at that point.

What is interesting is that we had a crtres patch for powerpc for many years,
but "recently" (2024) dropped it:

https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-6.12&id=3cf758061025b9284ddfb1259f79860666737302

And that dropped patch should have been part of several reference kernels since
that commit. Just so I know, this is something that has been passing on all
reference kernels and just broke on 6.16 ?

Something must have changed upstream to bring the breakage back! Your
fix is simpler than the old one we had, so that's progress :)

Bruce



Bruce



Peter

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org<mailto:openembedded-core@lists.openembedded.org> <openembedded-
> core@lists.openembedded.org<mailto:core@lists.openembedded.org>> On Behalf Of Bruce Ashfield via
> lists.openembedded.org<http://lists.openembedded.org>
> Sent: Friday, September 5, 2025 18:09
> To: richard.purdie@linuxfoundation.org<mailto:richard.purdie@linuxfoundation.org>
> Cc: openembedded-core@lists.openembedded.org<mailto:openembedded-core@lists.openembedded.org>
> Subject: [OE-core] [PATCH 1/5] poky: bump default kernel reference to 6.16
>
> From: Bruce Ashfield <bruce.ashfield@gmail.com<mailto:bruce.ashfield@gmail.com>>
>
> Bumping the reference kernel to 6.16. We keep the alt distro
> on 6.12 for better coverage.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com<mailto:bruce.ashfield@gmail.com>>
> ---
>  meta-poky/conf/distro/poky-tiny.conf | 2 +-
>  meta-poky/conf/distro/poky.conf      | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta-poky/conf/distro/poky-tiny.conf b/meta-poky/conf/distro/poky-
> tiny.conf
> index 81153b3b36..84baef347c 100644
> --- a/meta-poky/conf/distro/poky-tiny.conf
> +++ b/meta-poky/conf/distro/poky-tiny.conf
> @@ -41,7 +41,7 @@ FULL_OPTIMIZATION = "-Os"
>  # Distro config is evaluated after the machine config, so we have to explicitly
>  # set the kernel provider to override a machine config.
>  PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
> -PREFERRED_VERSION_linux-yocto-tiny ?= "6.12%"
> +PREFERRED_VERSION_linux-yocto-tiny ?= "6.16%"
>
>  # We can use packagegroup-core-boot, but in the future we may need a new
> packagegroup-core-tiny
>  #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
> index b12df2be70..d86630b153 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -19,8 +19,8 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-
> module-af-packet"
>
>  DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}
> ${POKY_DEFAULT_DISTRO_FEATURES}"
>
> -PREFERRED_VERSION_linux-yocto ?= "6.12%"
> -PREFERRED_VERSION_linux-yocto-rt ?= "6.12%"
> +PREFERRED_VERSION_linux-yocto ?= "6.16%"
> +PREFERRED_VERSION_linux-yocto-rt ?= "6.16%"
>
>  SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-
> ${TUNE_PKGARCH}-${MACHINE}"
>  SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
> --
> 2.39.2


--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#223742): https://lists.openembedded.org/g/openembedded-core/message/223742
Mute This Topic: https://lists.openembedded.org/mt/115084892/1050810
Group Owner: openembedded-core+owner@lists.openembedded.org<mailto:openembedded-core%2Bowner@lists.openembedded.org>
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com<mailto:bruce.ashfield@gmail.com>]
-=-=-=-=-=-=-=-=-=-=-=-


--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
Bruce Ashfield Sept. 19, 2025, 1:05 p.m. UTC | #6
On Fri, Sep 19, 2025 at 8:55 AM Marko, Peter <Peter.Marko@siemens.com>
wrote:

> (damn outlook and html prevents me to properly quote this below, sorry)
>

No worries. It's the message not the format that matters :)



>
> The commit description is not ideal and we struggle to fully understand
> why it was not failing before.
>
>
>
> Maybe it was not being built and new config changes trigger it now?
>

When I was tracking it down many years ago (it could almost be 10 years
now),
there were some situations where the .o was built before it was needed or
another
dependency triggered it to be built (a non-race way to get it in place), so
the linking
worked. We may have just been hitting good timing up until now.


>
> This also seems to be a missed line in
> 214c0eea43b2ea66bcd6467ea57e47ce8874191b from last year.
>
> As it says "This commit prepares for supporting the building of external
> modules..." maybe some new commits built on this feature and this broke at
> that time because not all places were properly prepared.
>
>
>
> I’ll probably wait until it gets merged to kernel master before submitting
> to linux-yocto.
>

That's up to you, or I can always go track it down on the upstream mailing
list.
Whatever is easiest on your end.

I don't mind taking in-progress patches, as my workflow can handle it
without
much fuss.

Bruce


>
>
> Peter
>
>
>
>
>
> *From:* Bruce Ashfield <bruce.ashfield@gmail.com>
> *Sent:* Friday, September 19, 2025 14:49
> *To:* bruce.ashfield@gmail.com
> *Cc:* Marko, Peter (FT D EU SK BFS1) <Peter.Marko@siemens.com>;
> openembedded-core@lists.openembedded.org; Sverdlin, Alexander (SI B PRO
> TI EAC CCP) <alexander.sverdlin@siemens.com>; Freihofer, Adrian (SI B PRO
> TI EAC CCP) <adrian.freihofer@siemens.com>;
> richard.purdie@linuxfoundation.org
> *Subject:* Re: [OE-core] [PATCH 1/5] poky: bump default kernel reference
> to 6.16
>
>
>
>
>
>
>
> On Fri, Sep 19, 2025 at 8:42 AM Bruce Ashfield via lists.openembedded.org
> <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
>
>
>
>
> On Fri, Sep 19, 2025 at 8:35 AM Marko, Peter <Peter.Marko@siemens.com>
> wrote:
>
> Hello Bruce,
>
> This upgrade broke build of external kernel modules for powerpc.
> Yocto test devtool.DevtoolTest.test_devtool_kernelmodule is failing.
>
> We have prepared a patch for upstream kernel.
>
> https://lore.kernel.org/all/20250919121417.1601020-1-alexander.sverdlin@siemens.com/
> But I guess it will take lot of time to get picked there, then backported
> to 6.16, tagged and finally this tag picked by yocto.
> Is there a process to pick this patch already now to keep the pipeline
> green?
>
>
>
> Yes, if you submit it to the linux-yocto mailing list (you need to
> subscribe), I can
>
> merge it directly to linux-yocto and send a SRCREV bump to the list.
>
>
>
> I'll carry the patch to any newer kernel that I do, until it merges
> upstream and
>
> I'll automatically drop it at that point.
>
>
>
> What is interesting is that we had a crtres patch for powerpc for many
> years,
>
> but "recently" (2024) dropped it:
>
>
>
>
> https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-6.12&id=3cf758061025b9284ddfb1259f79860666737302
>
>
>
> And that dropped patch should have been part of several reference kernels
> since
>
> that commit. Just so I know, this is something that has been passing on all
>
> reference kernels and just broke on 6.16 ?
>
>
>
> Something must have changed upstream to bring the breakage back! Your
>
> fix is simpler than the old one we had, so that's progress :)
>
>
>
> Bruce
>
>
>
>
>
>
>
> Bruce
>
>
>
>
>
>
> Peter
>
> > -----Original Message-----
> > From: openembedded-core@lists.openembedded.org <openembedded-
> > core@lists.openembedded.org> On Behalf Of Bruce Ashfield via
> > lists.openembedded.org
> > Sent: Friday, September 5, 2025 18:09
> > To: richard.purdie@linuxfoundation.org
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH 1/5] poky: bump default kernel reference to
> 6.16
> >
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Bumping the reference kernel to 6.16. We keep the alt distro
> > on 6.12 for better coverage.
> >
> > Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> > ---
> >  meta-poky/conf/distro/poky-tiny.conf | 2 +-
> >  meta-poky/conf/distro/poky.conf      | 4 ++--
> >  2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta-poky/conf/distro/poky-tiny.conf
> b/meta-poky/conf/distro/poky-
> > tiny.conf
> > index 81153b3b36..84baef347c 100644
> > --- a/meta-poky/conf/distro/poky-tiny.conf
> > +++ b/meta-poky/conf/distro/poky-tiny.conf
> > @@ -41,7 +41,7 @@ FULL_OPTIMIZATION = "-Os"
> >  # Distro config is evaluated after the machine config, so we have to
> explicitly
> >  # set the kernel provider to override a machine config.
> >  PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
> > -PREFERRED_VERSION_linux-yocto-tiny ?= "6.12%"
> > +PREFERRED_VERSION_linux-yocto-tiny ?= "6.16%"
> >
> >  # We can use packagegroup-core-boot, but in the future we may need a new
> > packagegroup-core-tiny
> >  #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
> > diff --git a/meta-poky/conf/distro/poky.conf
> b/meta-poky/conf/distro/poky.conf
> > index b12df2be70..d86630b153 100644
> > --- a/meta-poky/conf/distro/poky.conf
> > +++ b/meta-poky/conf/distro/poky.conf
> > @@ -19,8 +19,8 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-
> > module-af-packet"
> >
> >  DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}
> > ${POKY_DEFAULT_DISTRO_FEATURES}"
> >
> > -PREFERRED_VERSION_linux-yocto ?= "6.12%"
> > -PREFERRED_VERSION_linux-yocto-rt ?= "6.12%"
> > +PREFERRED_VERSION_linux-yocto ?= "6.16%"
> > +PREFERRED_VERSION_linux-yocto-rt ?= "6.16%"
> >
> >  SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-
> > ${TUNE_PKGARCH}-${MACHINE}"
> >  SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
> > --
> > 2.39.2
>
>
>
>
> --
>
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#223742):
> https://lists.openembedded.org/g/openembedded-core/message/223742
> Mute This Topic: https://lists.openembedded.org/mt/115084892/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>
>
> --
>
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
Sverdlin, Alexander Sept. 19, 2025, 1:10 p.m. UTC | #7
Hi all,

On Fri, 2025-09-19 at 08:48 -0400, Bruce Ashfield wrote:
> What is interesting is that we had a crtres patch for powerpc for many years,
> but "recently" (2024) dropped it:
> 
> https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-6.12&id=3cf758061025b9284ddfb1259f79860666737302
> 
> And that dropped patch should have been part of several reference kernels since 
> that commit. Just so I know, this is something that has been passing on all
> reference kernels and just broke on 6.16 ?
> 
> Something must have changed upstream to bring the breakage back! Your
> fix is simpler than the old one we had, so that's progress :)

I believe, the removed patches were rather backports from the upstream kernel
solving the dependency issues for in-tree modules. The current issue looks a bit
different and is, I believe, an issue for external modules only.

But the above unfortunately makes it harder to explain why the external modules
were buildable before ;-)

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com
Bruce Ashfield Sept. 19, 2025, 1:22 p.m. UTC | #8
On Fri, Sep 19, 2025 at 9:10 AM Sverdlin, Alexander <
alexander.sverdlin@siemens.com> wrote:

> Hi all,
>
> On Fri, 2025-09-19 at 08:48 -0400, Bruce Ashfield wrote:
> > What is interesting is that we had a crtres patch for powerpc for many
> years,
> > but "recently" (2024) dropped it:
> >
> >
> https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-6.12&id=3cf758061025b9284ddfb1259f79860666737302
> >
> > And that dropped patch should have been part of several reference
> kernels since
> > that commit. Just so I know, this is something that has been passing on
> all
> > reference kernels and just broke on 6.16 ?
> >
> > Something must have changed upstream to bring the breakage back! Your
> > fix is simpler than the old one we had, so that's progress :)
>
> I believe, the removed patches were rather backports from the upstream
> kernel
> solving the dependency issues for in-tree modules. The current issue looks
> a bit
> different and is, I believe, an issue for external modules only.
>

They weren't backports, there's been a series of fixes around this for a
long time
to deal with it as a dependency for modules, here's one of my commits for
5.4:

------------------------
From f13fd6af4120b8b42d77377c9989457cda41899f Mon Sep 17 00:00:00 2001
From: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Sun, 15 Feb 2009 16:57:14 -0500
Subject: [PATCH 3/3] powerpc: add crtsavres.o to archprepare for kbuild

upstream commit da3de6df33f5f42ff9dc40093fbc884f524c9a49 adds
a dependency to all kernel modules to crtsavres. This
ensures that out-of-line register saves/restores work when
CONFIG_CC_OPTIMIZE_FOR_SIZE is enabled.

What it didn't do was ensure that it was built when
modules_prepare was run and hence out of tree powerpc kernel
modules can't properly link.

The fix is to add crtsavres.o to the archprepare rule in
the arch/powerpc/Makefile

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>


----------

Cheers,

Bruce



>
> But the above unfortunately makes it harder to explain why the external
> modules
> were buildable before ;-)
>
> --
> Alexander Sverdlin
> Siemens AG
> www.siemens.com
>
Sverdlin, Alexander Sept. 22, 2025, 1:54 p.m. UTC | #9
Hi all,

On Fri, 2025-09-19 at 09:05 -0400, Bruce Ashfield wrote:
> > I’ll probably wait until it gets merged to kernel master before submitting to linux-yocto.
> 
> That's up to you, or I can always go track it down on the upstream mailing list.
> Whatever is easiest on your end.
> 
> I don't mind taking in-progress patches, as my workflow can handle it without
> much fuss.

it turns out, it has been fixed (by the very same change) already in February!
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20250218-buildfix-extmod-powerpc-v2-1-1e78fcf12b56@efficios.com/

But remained in linux-next until now (and I didn't check that).
It's 46104a7d3ccd ("kbuild: Add missing $(objtree) prefix to powerpc crtsavres.o artifact").

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com
Bruce Ashfield Sept. 22, 2025, 2:01 p.m. UTC | #10
On Mon, Sep 22, 2025 at 9:54 AM Sverdlin, Alexander <
alexander.sverdlin@siemens.com> wrote:

> Hi all,
>
> On Fri, 2025-09-19 at 09:05 -0400, Bruce Ashfield wrote:
> > > I’ll probably wait until it gets merged to kernel master before
> submitting to linux-yocto.
> >
> > That's up to you, or I can always go track it down on the upstream
> mailing list.
> > Whatever is easiest on your end.
> >
> > I don't mind taking in-progress patches, as my workflow can handle it
> without
> > much fuss.
>
> it turns out, it has been fixed (by the very same change) already in
> February!
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20250218-buildfix-extmod-powerpc-v2-1-1e78fcf12b56@efficios.com/
>
> But remained in linux-next until now (and I didn't check that).
> It's 46104a7d3ccd ("kbuild: Add missing $(objtree) prefix to powerpc
> crtsavres.o artifact").
>

Aha!

Thanks for the follow up. I merged the latest -stable last night, so there
will be more bumps
to 6.16 today. (I didn't check if it is only in the latest stable or
somewhere else, but will have
a look later).

Bruce



>
> --
> Alexander Sverdlin
> Siemens AG
> www.siemens.com
>
diff mbox series

Patch

diff --git a/meta-poky/conf/distro/poky-tiny.conf b/meta-poky/conf/distro/poky-tiny.conf
index 81153b3b36..84baef347c 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/conf/distro/poky-tiny.conf
@@ -41,7 +41,7 @@  FULL_OPTIMIZATION = "-Os"
 # Distro config is evaluated after the machine config, so we have to explicitly
 # set the kernel provider to override a machine config.
 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
-PREFERRED_VERSION_linux-yocto-tiny ?= "6.12%"
+PREFERRED_VERSION_linux-yocto-tiny ?= "6.16%"
 
 # We can use packagegroup-core-boot, but in the future we may need a new packagegroup-core-tiny
 #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index b12df2be70..d86630b153 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -19,8 +19,8 @@  POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-module-af-packet"
 
 DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${POKY_DEFAULT_DISTRO_FEATURES}"
 
-PREFERRED_VERSION_linux-yocto ?= "6.12%"
-PREFERRED_VERSION_linux-yocto-rt ?= "6.12%"
+PREFERRED_VERSION_linux-yocto ?= "6.16%"
+PREFERRED_VERSION_linux-yocto-rt ?= "6.16%"
 
 SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-${TUNE_PKGARCH}-${MACHINE}"
 SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"