| Message ID | cover.1704169585.git.bruce.ashfield@gmail.com |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
Hello, This breaks meta-virt: https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/2705/steps/12/logs/stdio and I believe this also causes: AssertionError: 2 != 0 : Log: /home/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/target_logs/dmesg ----------------------- Central error: [ 0.455917] ACPI: _OSC evaluation for CPUs failed, trying _PDC *********************** [ 0.413863] raid6: sse2x2 gen() 14704 MB/s [ 0.430863] raid6: sse2x1 gen() 11500 MB/s [ 0.431830] raid6: using algorithm sse2x4 gen() 15109 MB/s [ 0.448863] raid6: .... xor() 8116 MB/s, rmw enabled [ 0.449864] raid6: using ssse3x2 recovery algorithm [ 0.450948] ACPI: Added _OSI(Module Device) [ 0.451846] ACPI: Added _OSI(Processor Device) [ 0.451865] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.452865] ACPI: Added _OSI(Processor Aggregator Device) [ 0.454666] ACPI: 1 ACPI AML tables successfully acquired and loaded [ 0.455917] ACPI: _OSC evaluation for CPUs failed, trying _PDC [ 0.457035] ACPI: Interpreter enabled [ 0.457889] ACPI: PM: (supports S0 S3 S5) [ 0.458874] ACPI: Using IOAPIC for interrupt routing [ 0.459924] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.460865] PCI: Using E820 reservations for host bridge windows [ 0.461998] ACPI: Enabled 2 GPEs in block 00 to 3F [ 0.465281] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.465869] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [ 0.466904] acpi PNP0A08:00: _OSC: platform does not support [LTR] [ 0.467913] acpi PNP0A08:00: _OSC: OS now controls [PME PCIeCapability] On 01/01/2024 23:31:02-0500, Bruce Ashfield wrote: > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > Richard, > > As promised, I waited until the new year to send this update > to introduce the 6.6 kernel and libc-headers. > > I'll be sending patches to the appropriate lists to remove > 6.5 shortly and make 6.6 the default. Once we have the reference > boards updated to 6.6, the 6.1 kernel will also be removed. > > I've built 6.6 for all supported arches, core-image-* and have > also tested against musl. > > Patches to meta-oe have been sent, and the work done with > 6.6 as the -dev kernel means that the tightly coupled packages > already build against 6.6. > > I'm sure there will be issues .. as there always are, but at > this point, I need more eyes and test cycles to find those > issues. > > Bruce > > > The following changes since commit fe5d2f0b666c83e3336ea9962c8e2e4c39816e21: > > bitbake: lib/bb: Add workaround for libgcc issues with python 3.8 and 3.9 (2023-12-30 11:03:25 +0000) > > are available in the Git repository at: > > https://git.yoctoproject.org/poky-contrib zedd/kernel > https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel > > Bruce Ashfield (7): > linux-libc-headers: update to v6.6-lts > linux-yocto: introduce 6.6 reference kernel > linux-yocto/6.6: fix AB-INT: QEMU kernel panic: No irq handler for > vector > linux-yocto-rt/6.6: fix CVE exclusion include > linux-yocto/6.6: update CVE exclusions > linux-yocto/6.6: update to v6.6.8 > linux-yocto/6.1: update to v6.1.69 > > meta/conf/distro/include/tcmode-default.inc | 2 +- > ...aders_6.5.bb => linux-libc-headers_6.6.bb} | 2 +- > .../linux/cve-exclusion_6.6.inc | 5172 +++++++++++++++++ > .../linux/linux-yocto-rt_6.1.bb | 6 +- > .../linux/linux-yocto-rt_6.6.bb | 48 + > .../linux/linux-yocto-tiny_6.1.bb | 6 +- > .../linux/linux-yocto-tiny_6.6.bb | 33 + > meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +- > meta/recipes-kernel/linux/linux-yocto_6.6.bb | 72 + > 9 files changed, 5347 insertions(+), 22 deletions(-) > rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.5.bb => linux-libc-headers_6.6.bb} (83%) > create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.6.inc > create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb > create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb > create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.6.bb > > -- > 2.39.2 > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#193196): https://lists.openembedded.org/g/openembedded-core/message/193196 > Mute This Topic: https://lists.openembedded.org/mt/103476582/3617179 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com] > -=-=-=-=-=-=-=-=-=-=-=- >
On Tue, Jan 2, 2024 at 9:24 AM Alexandre Belloni <alexandre.belloni@bootlin.com> wrote: > > Hello, > > This breaks meta-virt: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/2705/steps/12/logs/stdio > 6.6 kernel configs for meta-virt are on its master-next. I unfortunately can't push that for a couple days yet, so this will have to sit. > and I believe this also causes: > > AssertionError: 2 != 0 : Log: /home/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/target_logs/dmesg Everything booted and passed my runtime tests, which is all I can do before submitting. Hopefully someone with x86 knowledge/interest can pick that up, otherwise my suggestion is to add it to the allow list. Bruce > ----------------------- > Central error: [ 0.455917] ACPI: _OSC evaluation for CPUs failed, trying _PDC > *********************** > [ 0.413863] raid6: sse2x2 gen() 14704 MB/s > [ 0.430863] raid6: sse2x1 gen() 11500 MB/s > [ 0.431830] raid6: using algorithm sse2x4 gen() 15109 MB/s > [ 0.448863] raid6: .... xor() 8116 MB/s, rmw enabled > [ 0.449864] raid6: using ssse3x2 recovery algorithm > [ 0.450948] ACPI: Added _OSI(Module Device) > [ 0.451846] ACPI: Added _OSI(Processor Device) > [ 0.451865] ACPI: Added _OSI(3.0 _SCP Extensions) > [ 0.452865] ACPI: Added _OSI(Processor Aggregator Device) > [ 0.454666] ACPI: 1 ACPI AML tables successfully acquired and loaded > [ 0.455917] ACPI: _OSC evaluation for CPUs failed, trying _PDC > [ 0.457035] ACPI: Interpreter enabled > [ 0.457889] ACPI: PM: (supports S0 S3 S5) > [ 0.458874] ACPI: Using IOAPIC for interrupt routing > [ 0.459924] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug > [ 0.460865] PCI: Using E820 reservations for host bridge windows > [ 0.461998] ACPI: Enabled 2 GPEs in block 00 to 3F > [ 0.465281] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) > [ 0.465869] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] > [ 0.466904] acpi PNP0A08:00: _OSC: platform does not support [LTR] > [ 0.467913] acpi PNP0A08:00: _OSC: OS now controls [PME PCIeCapability] > > > On 01/01/2024 23:31:02-0500, Bruce Ashfield wrote: > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > Richard, > > > > As promised, I waited until the new year to send this update > > to introduce the 6.6 kernel and libc-headers. > > > > I'll be sending patches to the appropriate lists to remove > > 6.5 shortly and make 6.6 the default. Once we have the reference > > boards updated to 6.6, the 6.1 kernel will also be removed. > > > > I've built 6.6 for all supported arches, core-image-* and have > > also tested against musl. > > > > Patches to meta-oe have been sent, and the work done with > > 6.6 as the -dev kernel means that the tightly coupled packages > > already build against 6.6. > > > > I'm sure there will be issues .. as there always are, but at > > this point, I need more eyes and test cycles to find those > > issues. > > > > Bruce > > > > > > The following changes since commit fe5d2f0b666c83e3336ea9962c8e2e4c39816e21: > > > > bitbake: lib/bb: Add workaround for libgcc issues with python 3.8 and 3.9 (2023-12-30 11:03:25 +0000) > > > > are available in the Git repository at: > > > > https://git.yoctoproject.org/poky-contrib zedd/kernel > > https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel > > > > Bruce Ashfield (7): > > linux-libc-headers: update to v6.6-lts > > linux-yocto: introduce 6.6 reference kernel > > linux-yocto/6.6: fix AB-INT: QEMU kernel panic: No irq handler for > > vector > > linux-yocto-rt/6.6: fix CVE exclusion include > > linux-yocto/6.6: update CVE exclusions > > linux-yocto/6.6: update to v6.6.8 > > linux-yocto/6.1: update to v6.1.69 > > > > meta/conf/distro/include/tcmode-default.inc | 2 +- > > ...aders_6.5.bb => linux-libc-headers_6.6.bb} | 2 +- > > .../linux/cve-exclusion_6.6.inc | 5172 +++++++++++++++++ > > .../linux/linux-yocto-rt_6.1.bb | 6 +- > > .../linux/linux-yocto-rt_6.6.bb | 48 + > > .../linux/linux-yocto-tiny_6.1.bb | 6 +- > > .../linux/linux-yocto-tiny_6.6.bb | 33 + > > meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +- > > meta/recipes-kernel/linux/linux-yocto_6.6.bb | 72 + > > 9 files changed, 5347 insertions(+), 22 deletions(-) > > rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.5.bb => linux-libc-headers_6.6.bb} (83%) > > create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.6.inc > > create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb > > create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb > > create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.6.bb > > > > -- > > 2.39.2 > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- > > Links: You receive all messages sent to this group. > > View/Reply Online (#193196): https://lists.openembedded.org/g/openembedded-core/message/193196 > > Mute This Topic: https://lists.openembedded.org/mt/103476582/3617179 > > Group Owner: openembedded-core+owner@lists.openembedded.org > > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com] > > -=-=-=-=-=-=-=-=-=-=-=- > > > > > -- > Alexandre Belloni, co-owner and COO, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com
On Tue, Jan 2, 2024 at 9:32 AM Bruce Ashfield via lists.openembedded.org <bruce.ashfield=gmail.com@lists.openembedded.org> wrote: > > On Tue, Jan 2, 2024 at 9:24 AM Alexandre Belloni > <alexandre.belloni@bootlin.com> wrote: > > > > Hello, > > > > This breaks meta-virt: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/128/builds/2705/steps/12/logs/stdio > > > > 6.6 kernel configs for meta-virt are on its master-next. I > unfortunately can't push that for a couple days yet, so this will have > to sit. > > > and I believe this also causes: > > > > AssertionError: 2 != 0 : Log: /home/pokybuild/yocto-worker/qa-extras2/build/build/tmp/work/qemux86_64-poky-linux/core-image-sato/1.0/target_logs/dmesg > > Everything booted and passed my runtime tests, which is all I can do before > submitting. > > Hopefully someone with x86 knowledge/interest can pick that up, otherwise > my suggestion is to add it to the allow list. I was able to find the commit that tweaked the message, and I can confirm that it is just information and not an issue/error/warning. I'll try to locate the allow lists, and tweak them appropriately. Bruce > > Bruce > > > ----------------------- > > Central error: [ 0.455917] ACPI: _OSC evaluation for CPUs failed, trying _PDC > > *********************** > > [ 0.413863] raid6: sse2x2 gen() 14704 MB/s > > [ 0.430863] raid6: sse2x1 gen() 11500 MB/s > > [ 0.431830] raid6: using algorithm sse2x4 gen() 15109 MB/s > > [ 0.448863] raid6: .... xor() 8116 MB/s, rmw enabled > > [ 0.449864] raid6: using ssse3x2 recovery algorithm > > [ 0.450948] ACPI: Added _OSI(Module Device) > > [ 0.451846] ACPI: Added _OSI(Processor Device) > > [ 0.451865] ACPI: Added _OSI(3.0 _SCP Extensions) > > [ 0.452865] ACPI: Added _OSI(Processor Aggregator Device) > > [ 0.454666] ACPI: 1 ACPI AML tables successfully acquired and loaded > > [ 0.455917] ACPI: _OSC evaluation for CPUs failed, trying _PDC > > [ 0.457035] ACPI: Interpreter enabled > > [ 0.457889] ACPI: PM: (supports S0 S3 S5) > > [ 0.458874] ACPI: Using IOAPIC for interrupt routing > > [ 0.459924] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug > > [ 0.460865] PCI: Using E820 reservations for host bridge windows > > [ 0.461998] ACPI: Enabled 2 GPEs in block 00 to 3F > > [ 0.465281] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) > > [ 0.465869] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] > > [ 0.466904] acpi PNP0A08:00: _OSC: platform does not support [LTR] > > [ 0.467913] acpi PNP0A08:00: _OSC: OS now controls [PME PCIeCapability] > > > > > > On 01/01/2024 23:31:02-0500, Bruce Ashfield wrote: > > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > > > Richard, > > > > > > As promised, I waited until the new year to send this update > > > to introduce the 6.6 kernel and libc-headers. > > > > > > I'll be sending patches to the appropriate lists to remove > > > 6.5 shortly and make 6.6 the default. Once we have the reference > > > boards updated to 6.6, the 6.1 kernel will also be removed. > > > > > > I've built 6.6 for all supported arches, core-image-* and have > > > also tested against musl. > > > > > > Patches to meta-oe have been sent, and the work done with > > > 6.6 as the -dev kernel means that the tightly coupled packages > > > already build against 6.6. > > > > > > I'm sure there will be issues .. as there always are, but at > > > this point, I need more eyes and test cycles to find those > > > issues. > > > > > > Bruce > > > > > > > > > The following changes since commit fe5d2f0b666c83e3336ea9962c8e2e4c39816e21: > > > > > > bitbake: lib/bb: Add workaround for libgcc issues with python 3.8 and 3.9 (2023-12-30 11:03:25 +0000) > > > > > > are available in the Git repository at: > > > > > > https://git.yoctoproject.org/poky-contrib zedd/kernel > > > https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel > > > > > > Bruce Ashfield (7): > > > linux-libc-headers: update to v6.6-lts > > > linux-yocto: introduce 6.6 reference kernel > > > linux-yocto/6.6: fix AB-INT: QEMU kernel panic: No irq handler for > > > vector > > > linux-yocto-rt/6.6: fix CVE exclusion include > > > linux-yocto/6.6: update CVE exclusions > > > linux-yocto/6.6: update to v6.6.8 > > > linux-yocto/6.1: update to v6.1.69 > > > > > > meta/conf/distro/include/tcmode-default.inc | 2 +- > > > ...aders_6.5.bb => linux-libc-headers_6.6.bb} | 2 +- > > > .../linux/cve-exclusion_6.6.inc | 5172 +++++++++++++++++ > > > .../linux/linux-yocto-rt_6.1.bb | 6 +- > > > .../linux/linux-yocto-rt_6.6.bb | 48 + > > > .../linux/linux-yocto-tiny_6.1.bb | 6 +- > > > .../linux/linux-yocto-tiny_6.6.bb | 33 + > > > meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +- > > > meta/recipes-kernel/linux/linux-yocto_6.6.bb | 72 + > > > 9 files changed, 5347 insertions(+), 22 deletions(-) > > > rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.5.bb => linux-libc-headers_6.6.bb} (83%) > > > create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.6.inc > > > create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb > > > create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb > > > create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.6.bb > > > > > > -- > > > 2.39.2 > > > > > > > > > > > > > > > > > > > > -- > > Alexandre Belloni, co-owner and COO, Bootlin > > Embedded Linux and Kernel engineering > > https://bootlin.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 > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#193234): https://lists.openembedded.org/g/openembedded-core/message/193234 > Mute This Topic: https://lists.openembedded.org/mt/103476582/1050810 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- >
On Mon, 2024-01-01 at 23:31 -0500, bruce.ashfield@gmail.com wrote: > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > Richard, > > As promised, I waited until the new year to send this update > to introduce the 6.6 kernel and libc-headers. > > I'll be sending patches to the appropriate lists to remove > 6.5 shortly and make 6.6 the default. Once we have the reference > boards updated to 6.6, the 6.1 kernel will also be removed. > > I've built 6.6 for all supported arches, core-image-* and have > also tested against musl. > > Patches to meta-oe have been sent, and the work done with > 6.6 as the -dev kernel means that the tightly coupled packages > already build against 6.6. > > I'm sure there will be issues .. as there always are, but at > this point, I need more eyes and test cycles to find those > issues. Thanks for putting this together (and deferring it!). I ran some tests with this series and the QA warning tweak applied. It looks like the remaining issues are: Some issue with 6.6 preempt-rt failing to fetch: https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8393/steps/34/logs/stdio Some issue with qemuarm64 ptest images failing: https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5933 [ 1.664613] jitterentropy: Initialization failed with host not compliant with requirements: 9 which looks familiar but I'm failing to page in the context offhand. There is also a meta-arm config check issue (copying Jon/Ross): https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5059 The build is close to finishing but hasn't quiet at the time of writing. Cheers, Richard
On Wed, Jan 3, 2024 at 6:25 PM Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > > On Mon, 2024-01-01 at 23:31 -0500, bruce.ashfield@gmail.com wrote: > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > Richard, > > > > As promised, I waited until the new year to send this update > > to introduce the 6.6 kernel and libc-headers. > > > > I'll be sending patches to the appropriate lists to remove > > 6.5 shortly and make 6.6 the default. Once we have the reference > > boards updated to 6.6, the 6.1 kernel will also be removed. > > > > I've built 6.6 for all supported arches, core-image-* and have > > also tested against musl. > > > > Patches to meta-oe have been sent, and the work done with > > 6.6 as the -dev kernel means that the tightly coupled packages > > already build against 6.6. > > > > I'm sure there will be issues .. as there always are, but at > > this point, I need more eyes and test cycles to find those > > issues. > > Thanks for putting this together (and deferring it!). I ran some tests > with this series and the QA warning tweak applied. It looks like the > remaining issues are: > > Some issue with 6.6 preempt-rt failing to fetch: > https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8393/steps/34/logs/stdio urk. That's an easy fix. I did a run with my scripts not updated for 6.6, I must have missed -rt. I'll send another patch to apply on the end of the series for it. > > Some issue with qemuarm64 ptest images failing: > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5933 > > [ 1.664613] jitterentropy: Initialization failed with host not compliant with requirements: 9 > > which looks familiar but I'm failing to page in the context offhand. > It does ring a bell, I'm looking into it. Bruce > There is also a meta-arm config check issue (copying Jon/Ross): > > https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5059 > > The build is close to finishing but hasn't quiet at the time of > writing. > > Cheers, > > Richard
On Wed, Jan 3, 2024 at 6:37 PM Bruce Ashfield via lists.openembedded.org <bruce.ashfield=gmail.com@lists.openembedded.org> wrote: > > On Wed, Jan 3, 2024 at 6:25 PM Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: > > > > On Mon, 2024-01-01 at 23:31 -0500, bruce.ashfield@gmail.com wrote: > > > From: Bruce Ashfield <bruce.ashfield@gmail.com> > > > > > > Richard, > > > > > > As promised, I waited until the new year to send this update > > > to introduce the 6.6 kernel and libc-headers. > > > > > > I'll be sending patches to the appropriate lists to remove > > > 6.5 shortly and make 6.6 the default. Once we have the reference > > > boards updated to 6.6, the 6.1 kernel will also be removed. > > > > > > I've built 6.6 for all supported arches, core-image-* and have > > > also tested against musl. > > > > > > Patches to meta-oe have been sent, and the work done with > > > 6.6 as the -dev kernel means that the tightly coupled packages > > > already build against 6.6. > > > > > > I'm sure there will be issues .. as there always are, but at > > > this point, I need more eyes and test cycles to find those > > > issues. > > > > Thanks for putting this together (and deferring it!). I ran some tests > > with this series and the QA warning tweak applied. It looks like the > > remaining issues are: > > > > Some issue with 6.6 preempt-rt failing to fetch: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8393/steps/34/logs/stdio > > urk. That's an easy fix. I did a run with my scripts not updated for 6.6, > I must have missed -rt. I'll send another patch to apply on the end of > the series > for it. > > > > > Some issue with qemuarm64 ptest images failing: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5933 > > > > [ 1.664613] jitterentropy: Initialization failed with host not compliant with requirements: 9 > > > > which looks familiar but I'm failing to page in the context offhand. > > > > It does ring a bell, I'm looking into it. https://patchwork.yoctoproject.org/project/oe-core/patch/20231003122542.764073-1-ross.burton@arm.com/ It looks like we are supposed to ignore it, did the move to the text files drop that ignore entry ? or did it otherwise slip through the cracks ? Bruce > > Bruce > > > There is also a meta-arm config check issue (copying Jon/Ross): > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5059 > > > > The build is close to finishing but hasn't quiet at the time of > > writing. > > > > Cheers, > > > > Richard > > > > -- > - 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 (#193296): https://lists.openembedded.org/g/openembedded-core/message/193296 > Mute This Topic: https://lists.openembedded.org/mt/103476582/1050810 > Group Owner: openembedded-core+owner@lists.openembedded.org > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- >
On 3 Jan 2024, at 23:52, Bruce Ashfield <bruce.ashfield@gmail.com> wrote: >>> Some issue with qemuarm64 ptest images failing: >>> https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5933 >>> >>> [ 1.664613] jitterentropy: Initialization failed with host not compliant with requirements: 9 >>> >>> which looks familiar but I'm failing to page in the context offhand. >>> >> >> It does ring a bell, I'm looking into it. > > https://patchwork.yoctoproject.org/project/oe-core/patch/20231003122542.764073-1-ross.burton@arm.com/ > > It looks like we are supposed to ignore it, did the move to the text files > drop that ignore entry ? or did it otherwise slip through the cracks ? I chased upstream and we backported a few patches from cryptodev instead. These are now part of 6.6, so this is a new and exciting regression. I’ve just pinged upstream again but will send an ignore for the meantime. >>> There is also a meta-arm config check issue (copying Jon/Ross): >>> >>> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5059 Noted, thanks. Ross
From: Bruce Ashfield <bruce.ashfield@gmail.com> Richard, As promised, I waited until the new year to send this update to introduce the 6.6 kernel and libc-headers. I'll be sending patches to the appropriate lists to remove 6.5 shortly and make 6.6 the default. Once we have the reference boards updated to 6.6, the 6.1 kernel will also be removed. I've built 6.6 for all supported arches, core-image-* and have also tested against musl. Patches to meta-oe have been sent, and the work done with 6.6 as the -dev kernel means that the tightly coupled packages already build against 6.6. I'm sure there will be issues .. as there always are, but at this point, I need more eyes and test cycles to find those issues. Bruce The following changes since commit fe5d2f0b666c83e3336ea9962c8e2e4c39816e21: bitbake: lib/bb: Add workaround for libgcc issues with python 3.8 and 3.9 (2023-12-30 11:03:25 +0000) are available in the Git repository at: https://git.yoctoproject.org/poky-contrib zedd/kernel https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (7): linux-libc-headers: update to v6.6-lts linux-yocto: introduce 6.6 reference kernel linux-yocto/6.6: fix AB-INT: QEMU kernel panic: No irq handler for vector linux-yocto-rt/6.6: fix CVE exclusion include linux-yocto/6.6: update CVE exclusions linux-yocto/6.6: update to v6.6.8 linux-yocto/6.1: update to v6.1.69 meta/conf/distro/include/tcmode-default.inc | 2 +- ...aders_6.5.bb => linux-libc-headers_6.6.bb} | 2 +- .../linux/cve-exclusion_6.6.inc | 5172 +++++++++++++++++ .../linux/linux-yocto-rt_6.1.bb | 6 +- .../linux/linux-yocto-rt_6.6.bb | 48 + .../linux/linux-yocto-tiny_6.1.bb | 6 +- .../linux/linux-yocto-tiny_6.6.bb | 33 + meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +- meta/recipes-kernel/linux/linux-yocto_6.6.bb | 72 + 9 files changed, 5347 insertions(+), 22 deletions(-) rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.5.bb => linux-libc-headers_6.6.bb} (83%) create mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.6.inc create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb create mode 100644 meta/recipes-kernel/linux/linux-yocto_6.6.bb