On Wed, Apr 13, 2022 at 11:42 AM Bruce Ashfield via lists.openembedded.org <[email protected]> wrote: > > > > On Wed, Apr 13, 2022 at 11:19 AM Luca Ceresoli <[email protected]> > wrote: >> >> Hello Bruce, >> >> Il giorno Tue, 12 Apr 2022 17:45:55 -0400 >> "Bruce Ashfield" <[email protected]> ha scritto: >> >> > From: Bruce Ashfield <[email protected]> >> > >> > Richard, >> > >> > Here's the collection of -stable, fixes and tweaks that I was talking >> > about during the engineering sync on Tuesday. >> > >> > Feel free to take what you want, or just wait on them all until the >> > release is over. >> > >> > It is worth taking the 5.18 -dev and lttng fixes IMHO, since they do >> > make the release a bit more future proof. Likewise with Jon's -tiny >> > changes. >> > >> > Cheers, >> > >> > Bruce >> > >> > The following changes since commit >> > 632c83ab787211ef927a999f4ecde1d3ce40621d: >> > >> > license_image.bbclass: close package.manifest file (2022-04-10 >> > 08:31:17 +0100) >> > >> > are available in the Git repository at: >> > >> > git://git.yoctoproject.org/poky-contrib zedd/kernel >> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel >> > >> > Bruce Ashfield (8): >> > linux-yocto/5.15: arm: poky-tiny cleanup and fixes >> > linux-yocto/5.15: update to v5.15.33 >> > linux-yocto/5.10: update to v5.10.110 >> > linux-yocto/5.10: base: enable kernel crypto userspace API >> > linux-yocto/5.15: base: enable kernel crypto userspace API >> > linux-yocto/5.15: kasan: fix BUG: sleeping function called from >> > invalid context >> > lttng-modules: support kernel 5.18+ >> > linux-yocto-dev: update to v5.18+ >> >> Sending this series to the autobuilders triggered some errors and >> warnings (see below). Can you check that? >> > > unfortunately not. I'll wait out the release and re-submit these later. > > That being said, I've run similar tests to the errors found on the AB, and > can't reproduce locally, so I have no way to debug. > > Cheers, > > Bruce > > >> >> 1. kernel not booting on qemuppc >> >> >> OpenBIOS 1.1 [Nov 1 2021 20:36] >> >> Configuration device id QEMU version 1 machine id 1 >> >> CPUs: 1 >> >> Memory: 256M >> >> UUID: 00000000-0000-0000-0000-000000000000 >> >> CPU type PowerPC,G4 >> milliseconds isn't unique. >> >> [ppc] Kernel already loaded (0x01000000 + 0x01394760) (initrd >> >> 0x00000000 + 0x00000000) [ppc] Kernel command line: root=/dev/vda rw >> mem=256M >> >> ip=192.168.7.4::192.168.7.3:255.255.255.0::eth0:off:8.8.8.8 >> console=ttyS0 console=ttyS1 console=tty console=ttyS0 printk.time=1 >> >> switching to new context: >>
I was able to steal a bit of time and did a git bisect on this one. i have a suspected commit: commit c894ac44786cfed383a6c6b20c1bfb12eb96018a Author: Thomas Zimmermann <[email protected]> Date: Tue Jan 25 10:12:18 2022 +0100 fbdev: Hot-unplug firmware fb devices on forced removal commit 27599aacbaefcbf2af7b06b0029459bbf682000d upstream. Which seems to line up with the messages in the panic. I reverted it, and I'm able to boot again. I'll carry that locally and see what the full upstream fix is later .. since this is going to hit us on future kernels as well. >> >> ===== end: snippet ===== >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5012/steps/12/logs/stdio >> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5013/steps/12/logs/stdio >> >> 2. X.org not starting on qemuarm >> >> [ 14.037] (EE) No devices detected. >> [ 14.039] (EE) Fatal server error: >> [ 14.040] (EE) no screens found(EE) >> [ 14.041] (EE) >> Please consult the The X.Org Foundation support >> at http://wiki.x.org >> for help. >> [ 14.042] (EE) Please also check the log file at >> "/var/log/Xorg.0.log" for additional information. >> [ 14.046] (EE) Server terminated with error (1). Closing log file. >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/5053/steps/12/logs/stdio >> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/5054/steps/12/logs/stdio >> This was related to Jon Mason's config changes to qemuarm for -tiny, he's got it working again, and a fix should be incoming. >> >> 3. ptest warning >> >> AssertionError: Failed ptests: >> {'strace': ['landlock_create_ruleset-y.gen.test', >> 'landlock_create_ruleset-y.gen']} >> >> This is landlock-related, thus perhaps caused by patch 2/8. >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/3117/steps/12/logs/stdio >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/3369/steps/12/logs/stdio >> No great idea on this one yet. I can't easily run ptests with my aging/ancient builder, so I'll see if I can come up with a simpler way to test it next week. Bruce >> >> Best regards. >> -- >> Luca Ceresoli, 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 > > > > -- - 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 (#164376): https://lists.openembedded.org/g/openembedded-core/message/164376 Mute This Topic: https://lists.openembedded.org/mt/90428400/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
