linux/poky.git, branch 4.2_M2

build-appliance: Fix merge error

2023-01-26T22:51:00+00:00

Signed-off-by: Richard Purdie

build-appliance-image: Update to master head revision

2023-01-26T22:29:12+00:00

(From OE-Core rev: 493f2d163718d78560a2b3ad5d3c0fb34caae8c0) Signed-off-by: Richard Purdie

poky/poky-tiny: bump preferred version to 6.1

2023-01-26T22:23:07+00:00

5.19 will be removed shortly, bumping the preferred versions for poky/poky-tiny to 6.1. The -alt config remains on 5.15. (From meta-yocto rev: 535ef93ef68af20b06effb0dd899895a192bb412) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

conf/qemu: bump preferred kernel version to 6.1

2023-01-26T22:22:53+00:00

6.1 has been soaking for a while now, so it is time to bump the default qemu version to 6.1 and prepare to remove 5.19. (From OE-Core rev: 91c1f7d4eb9ec5ad683c798812395df3a56747ba) Signed-off-by: Bruce Ashfield Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

qemuppc64: set the qemuppc64 nfs r/wsize mount options to 524288

2023-01-26T22:22:53+00:00

On master oe, build a qemuppc64 with systemd as default init, when we use nfs bootup, the kernel might panic due to missing symbol in dynamic libraries as below: hid-generic 0003:0627:0001.0003: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.0-3/input0 /sbin/init: /lib64/libm.so.6: version `XZ_5.0' not found (required by /usr/lib64/libkmod.so.2) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 CPU: 0 PID: 1 Comm: init Not tainted 5.15.78-yocto-standard #1 Call Trace: [c000000007443ba0] [c0000000009538d0] dump_stack_lvl+0x74/0xa8 (unreliable) [c000000007443be0] [c000000000103524] panic+0x170/0x3cc [c000000007443c80] [c00000000010cf64] do_exit+0xb44/0xb50 [c000000007443d50] [c00000000010d040] do_group_exit+0x60/0xd0 [c000000007443d90] [c00000000010d0d4] sys_exit_group+0x24/0x30 [c000000007443db0] [c00000000002cfd4] system_call_exception+0x194/0x2f0 [c000000007443e10] [c00000000000c2cc] system_call_common+0xec/0x250 --- interrupt: c00 at 0x7fff9ed9e840 NIP: 00007fff9ed9e840 LR: 00007fff9ed7da20 CTR: 0000000000000000 REGS: c000000007443e80 TRAP: 0c00 Not tainted (5.15.78-yocto-standard) MSR: 800000000280f033 CR: 24022442 XER: 00000000 One or more of the libraries systemd depends on failed to load due to unresolved symbols/functions. This was intermittent - with a failure rate estimated between 5% and 30%. After checking the code, this issue happens on gcc 12, kirkstone is using gcc 11 works well, with both using the exact same v5.15.84 kernel commit. There is a kernel fix from upstream [1], they changed the rsize / wsize to a multiple of PAGE_SIZE, when we applied this patch, the qemuppc64's default r/wsize went from 4096 to 524288.But the qemuppc64 doesn't have its own linux-yocto kernel branch, so apply this change might cause regression with other platforms which share branch with qemuppc64. So, we added an extra option for nfs rootfs, and set the qemuppc64 default r/w size to 524288 to line up with the kernel fix[1]. Yocto did a similar thing in the distant past[2] - prior to boot-arg adjustments existing - by allowing a Kconfig to set the defaults on nfsboot, in order to work around hardware limitations. Reference: [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=940261a195080cf [2] https://git.yoctoproject.org/linux-yocto-4.1/commit/?h=standard/base&id=a96cfd98add95 (From OE-Core rev: 14a81556ff1be326647e654424c8f1bf9d0db912) Signed-off-by: Xiangyu Chen Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

runqemu: add process of option QB_NFSROOTFS_EXTRA_OPT

2023-01-26T22:22:53+00:00

This extra options to be appended to the nfs rootfs options in kernel boot arg. Example config with qemuppc64 in machine config: add r/w size in the nfs rootfs extra option: QB_NFSROOTFS_EXTRA_OPT = "wsize=524288,rsize=524288" re-build and runqemu with nfs again, we can observe the kernel command line added our defined value in QB_NFSROOTFS_EXTRA_OPT: Kernel command line: root=/dev/nfs nfsroot=10.0.2.2:/home/xchen5/testing/build/tmp-glibc/deploy/images/qemuppc64/testnfs,nfsvers=3,port=3049,tcp,mountport=3048,wsize=524288,rsize=524288 rw mem=256M ip=dhcp console=hvc0 console=hvc0 nohugevmalloc (From OE-Core rev: 43a97f5bf3f90c5c1fd603f7dca2b3db2c0e3040) Signed-off-by: Xiangyu Chen Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

qemuboot.bbclass: add QB_NFSROOTFS_EXTRA_OPT for nfs rootfs extra option

2023-01-26T22:22:53+00:00

This extra options to be appended to the nfs rootfs options in kernel boot arg. (From OE-Core rev: a255a7f350b558445f4f6c29f60e77c33883b08a) Signed-off-by: Xiangyu Chen Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

classes/fs-uuid: Fix command output decoding issue

2023-01-26T22:22:53+00:00

The default return value from subprocess.check_output is an encoded byte. The applied fix will decode the value to a string. (From OE-Core rev: 046769fa952a511865c416b80d10af6287147fb7) Signed-off-by: Pawel Zalewski Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

kernel/linux-kernel-base: Fix kernel build artefact determinism issues

2023-01-26T22:20:32+00:00

With the 6.1 kernel we've seen reproducibility/determinism issues where the kernel seems to rebuild headers referencing the hostname or local user. kernel-devsrc building after the kernel seemed to trigger it in some cases. Moving the definitions to the bbclass used by all the kernel recipe code including kernel-devsrc seems to be the best way to ensure this doesn't happen. (From OE-Core rev: 60681baa97daf4f3856453c34d6be08b6771a81b) Signed-off-by: Richard Purdie

gtk4: add PACKAGECONFIG for cloudproviders

2023-01-26T21:57:48+00:00

- Add missing cups runtime dependency (From OE-Core rev: b5ab0d1795e68c29a2b69f99a6b46b920e879ec7) Signed-off-by: Markus Volk Signed-off-by: Richard Purdie