public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "Moessbauer, Felix (T CED SES-DE)" <felix.moessbauer@siemens.com>,
	"Arjunan, Srinu (FT FDS CES LX PBU 2)" <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] linux-custom: Pin buster compat level to 10 to fix kernel builds
Date: Fri, 14 Feb 2025 14:40:19 +0100	[thread overview]
Message-ID: <1754ed33-0cc0-4e72-8de2-00a45117832e@siemens.com> (raw)
In-Reply-To: <6c52b13f-0f6a-4749-8b4b-343b801bc431@siemens.com>

On 03.02.25 11:54, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Compat level 12 of buster selects dh_dwz which breaks in that old
> version with certain kernels, e.g. like this:
> 
>  dwz: dwz.c:9255: recompute_abbrevs: Assertion `off == cu_size' failed.
>  dh_dwz: dwz -q -- debian/linux-image-cip-dbg/usr/lib/debug/lib/modules/5.10.233-cip56/vmlinux died with signal 6
> 
> As buster is LTS now, we take the low-risk path and switch back to the
> compat level the recipe was once validated again, rather than trying to
> resolve this and possibly more issues.
> 
> Fixes: ca786c36bca9 ("meta/recipes-kernel: use debhelper-compat to generate compat file")
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  meta/recipes-kernel/linux/linux-custom.inc | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
> index 77700a5d..d2fca3aa 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -14,6 +14,9 @@ DESCRIPTION ?= "Custom kernel"
>  MAINTAINER ?= "isar-users <isar-users@googlegroups.com>"
>  DISTRIBUTOR ?= "ISAR"
>  
> +# pinned due to known or possible issues with compat 12
> +DEBIAN_COMPAT:buster = "10"
> +
>  KBUILD_DEPENDS ?= "build-essential:native, \
>                     libelf-dev:native, \
>                     libncurses-dev:native, \

This regression fix is still not merged - any blockers? Downstream, it
prevents isar updates.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/1754ed33-0cc0-4e72-8de2-00a45117832e%40siemens.com.

  reply	other threads:[~2025-02-14 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 10:54 'Jan Kiszka' via isar-users
2025-02-14 13:40 ` 'Jan Kiszka' via isar-users [this message]
2025-02-16  8:01 ` Uladzimir Bely

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=1754ed33-0cc0-4e72-8de2-00a45117832e@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=srinuvasan.a@siemens.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