public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com,
	"Scott Murray" <scott.murray@konsulko.com>,
	"Jan-Simon Möller" <jsmoeller@linuxfoundation.org>,
	"Jon Mason" <Jon.Mason@arm.com>,
	"Ross Burton" <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/10] kernel-yocto: consolidated pull request
Date: Fri, 02 Aug 2024 10:02:21 +0100	[thread overview]
Message-ID: <8e96d9f2ce3e7f2e35a69ec2d9bec9aa6ea0f2fd.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1722524523.git.bruce.ashfield@gmail.com>

Hi Bruce,

On Thu, 2024-08-01 at 11:08 -0400, bruce.ashfield@gmail.com wrote:
> Here's the next batch of kernel updates. Obviously the -stable
> updates to 6.1 are routine, but the larger changes are the
> introduction of the 6.10 kernel as a new / validated reference
> version.
> 
> Some notes:
> 
>   - I've included the poky/poky-tiny preferred version bumps
>     in this pull request for simplicity. Yes, I know they go
>     to meta-yocto, but it is easier to make this available for
>     AB testing when they are all together.
> 
>   - I'm watching the status of 6.10, if for some reason it
>     EOLs before we release, we'll jump to 6.11, which I have
>     under test and will push as linux-yocto-dev shortly.
> 
>   - There's one known build issue with 6.10, it is zfs in
>     meta-oe. The upstream hasn't updated to support 6.10 yet,
>     so I'm watching and waiting on that .. but there's no
>     reason to hold this request for more testing on that.
> 
>   - I've tested 6.10 for all architectures on core-image-minimal,
>     core-image-sato and core-image-kernel-dev. I've also
>     tested against musl and poky-altconfig (6.1 with the
>     6.10 headers)
> 
> There will surely be AB issues with this, but it is now
> to the point where I need additional coverage and eyes
> on the changes.

Thanks for this, I put it through testing after tweaking it to remove a
rouge inherit. There were some issues:

a) genericarm64 version issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/166/builds/687

Warnings since genericarm64 isn't available as 6.10. Everything else
seemed to miss the preferred_version and build 6.6

b) crypto-dev failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/9329
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/9340
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/9313
https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/9161/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/5141/steps/12/logs/stdio
(the latter taking out the reproducibility build so that wasn't tested)

c) meta-virt xen issues:
https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/3455

d) meta-agl kernel config fragment warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/4556

e) meta-arm kernel config fragment warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5810

f) qemumips64 parselogs issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/9240/steps/14/logs/stdio
"failed when register_sysctl_sz sched_fair_sysctls to kernel"
"failed when register_sysctl_sz sched_core_sysctls to kernel"
"pci 0000:00:00.0: [Firmware Bug]: BAR 5: invalid; can't size"
(and other BARs)

g) qemumips parselogs issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/9256/steps/15/logs/stdio
Similar to qemumips64

h) qemuarmv5 config fragment warning:
https://autobuilder.yoctoproject.org/typhoon/#/builders/160/builds/989

I've copied agl/arm people.

Probably nothing too surprising. I'll drop some of the patches whilst
we resolve these but see if we can keep the headers upgrade and the
point release bumps.

I'll try and test the crypto-dev upgrade on the list as that might help
that issue.

Cheers,

Richard




  parent reply	other threads:[~2024-08-02  9:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 15:08 [PATCH 00/10] kernel-yocto: consolidated pull request bruce.ashfield
2024-08-01 15:08 ` [PATCH 01/10] linux-yocto/6.6: update to v6.6.36 bruce.ashfield
2024-08-01 15:08 ` [PATCH 02/10] linux-yocto/6.6: update to v6.6.38 bruce.ashfield
2024-08-01 15:08 ` [PATCH 03/10] linux-yocto/6.6: update to v6.6.40 bruce.ashfield
2024-08-01 15:08 ` [PATCH 04/10] linux-yocto/6.6: update to v6.6.43 bruce.ashfield
2024-08-01 15:08 ` [PATCH 05/10] linux-yocto: introduce 6.10 reference kernel bruce.ashfield
2024-08-01 15:08 ` [PATCH 06/10] linux-libc-headers: update to v6.10 bruce.ashfield
2024-08-01 15:08 ` [PATCH 07/10] kernel-devsrc: remove 64 bit vdso cmd files bruce.ashfield
2024-08-01 15:08 ` [PATCH 08/10] linux-yocto/6.10: update to v6.10 bruce.ashfield
2024-08-01 15:08 ` [PATCH 09/10] linux-yocto/6.10: update to v6.10.2 bruce.ashfield
2024-08-01 15:08 ` [PATCH 10/10] poky/poky-tiny: bump preferred version to 6.10 bruce.ashfield
2024-08-02  9:02 ` Richard Purdie [this message]
2024-08-02 11:18   ` [PATCH 00/10] kernel-yocto: consolidated pull request Bruce Ashfield
2024-08-06  3:24   ` Bruce Ashfield
2024-08-06  3:56     ` Jon Mason
  -- strict thread matches above, loose matches on Subject: below --
2022-03-22 17:19 bruce.ashfield
2020-08-12 17:03 Bruce Ashfield
2017-02-01 15:30 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=8e96d9f2ce3e7f2e35a69ec2d9bec9aa6ea0f2fd.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Jon.Mason@arm.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=jsmoeller@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    --cc=scott.murray@konsulko.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