From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Moessbauer,
Felix Jonathan (T CED INW-CN)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Schmidt, Adriaan (T CED SES-DE)" <adriaan.schmidt@siemens.com>
Cc: "Schild, Henning (T CED SES-DE)" <henning.schild@siemens.com>
Subject: Re: sstate can result in inconsistent kernel and modules
Date: Mon, 17 Oct 2022 07:59:37 +0200 [thread overview]
Message-ID: <7c301a59-7be2-2664-fc72-f5936276a43e@siemens.com> (raw)
In-Reply-To: <HE1PR1001MB1098EB58BCE827CB242A8CD789269@HE1PR1001MB1098.EURPRD10.PROD.OUTLOOK.COM>
On 16.10.22 07:48, Moessbauer, Felix Jonathan (T CED INW-CN) wrote:
> Dear ISAR users,
>
> I just discovered the following bug on a re-build using the sstate cache:
>
> The installed kernel version in the image is 5.19.6-1, while the kernel modules are built for 5.19.0-2.
> The reason is that the modules are extracted from the sstate cache, but bitbake does not know about the "exact" kernel revision used for building.
>
> Actually, I don't know how to easily solve that issue, as bitbake does not know about the exact Debian package versions.
> But what could be done is to check for version incompatibilities in the final rootfs.
> Or we disable the sstate cache for module builds (but I don't know how to do that).
How was this inconsistency created? Did you select a different kernel
version from the same isar-bootstrap generated apt database? Because if
the latter changes, all recipes and cached artifacts downstream should
change as well.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-10-17 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 5:48 MOESSBAUER, FELIX JONATHAN
2022-10-17 5:59 ` Jan Kiszka [this message]
2022-10-17 6:20 ` MOESSBAUER, FELIX JONATHAN
2022-10-17 6:40 ` Jan Kiszka
2022-10-19 5:36 ` Uladzimir Bely
2022-10-20 3:10 ` MOESSBAUER, FELIX JONATHAN
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=7c301a59-7be2-2664-fc72-f5936276a43e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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