Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Bruce Ashfield" <bruce.ashfield@gmail.com>
Cc: richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [OE-core] [PATCH 0/8] kernel: consolidated pull request
Date: Wed, 13 Apr 2022 17:19:26 +0200	[thread overview]
Message-ID: <20220413171926.771b4b06@melee> (raw)
In-Reply-To: <cover.1649799823.git.bruce.ashfield@gmail.com>

Hello Bruce,

Il giorno Tue, 12 Apr 2022 17:45:55 -0400
"Bruce Ashfield" <bruce.ashfield@gmail.com> ha scritto:

> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> 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?

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:

  ===== 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

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

Best regards.
-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2022-04-13 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 21:45 [PATCH 0/8] kernel: consolidated pull request bruce.ashfield
2022-04-12 21:45 ` [PATCH 1/8] linux-yocto/5.15: arm: poky-tiny cleanup and fixes bruce.ashfield
2022-04-12 21:45 ` [PATCH 2/8] linux-yocto/5.15: update to v5.15.33 bruce.ashfield
2022-04-12 21:45 ` [PATCH 3/8] linux-yocto/5.10: update to v5.10.110 bruce.ashfield
2022-04-12 21:45 ` [PATCH 4/8] linux-yocto/5.10: base: enable kernel crypto userspace API bruce.ashfield
2022-04-12 21:46 ` [PATCH 5/8] linux-yocto/5.15: " bruce.ashfield
2022-04-12 21:46 ` [PATCH 6/8] linux-yocto/5.15: kasan: fix BUG: sleeping function called from invalid context bruce.ashfield
2022-04-12 21:46 ` [PATCH 7/8] lttng-modules: support kernel 5.18+ bruce.ashfield
2022-04-12 21:46 ` [PATCH 8/8] linux-yocto-dev: update to v5.18+ bruce.ashfield
2022-04-13 15:19 ` Luca Ceresoli [this message]
2022-04-13 15:42   ` [OE-core] [PATCH 0/8] kernel: consolidated pull request Bruce Ashfield
     [not found]   ` <16E57F14B019C5B6.11417@lists.openembedded.org>
2022-04-14  2: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=20220413171926.771b4b06@melee \
    --to=luca.ceresoli@bootlin.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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