Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] Latest AB-INT unexplained mystery failure
Date: Tue, 22 Oct 2024 10:58:33 +0100	[thread overview]
Message-ID: <f1b97191136f649bac813f2159e3a40345f387c8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8ZrpWyObbQJReS-dLfjxY3QpyggqB53r_jcqFhTUvXdw@mail.gmail.com>

On Mon, 2024-10-21 at 12:55 +0200, Alexander Kanavin wrote:
> On Sat, 19 Oct 2024 at 23:48, Richard Purdie via
> lists.openembedded.org
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
> 
> > Creative ideas on further debugging welcome, I'm not sure where
> > from
> > here. I think it narrows down the issue to the host kernel or qemu
> > and
> > these qemu binaries are working on the other builders. The host is
> > a
> > 5.10.223 kernel:
> > 
> > $ cat /proc/version
> > Linux version 5.10.0-32-amd64 (debian-kernel@lists.debian.org)
> > (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for
> > Debian) 2.35.2) #1 SMP Debian 5.10.223-1 (2024-08-10)
> 
> There's an option to use 6.1 kernel on bullseye:
> https://packages.debian.org/bullseye-backports/linux-image-amd64
> 
> so I'd give that a shot, if only to confirm (or refute) it's
> definitely 5.10 on the host.

Michael was able to switch debian11-vk-1 to the 6.1 kernel (thanks!)
and I've run  5 builds successfully on it, the single build I tried on
debian11-vk3 at the same time failed.

I'm therefore willing to say this is some bug in the 5.10 kernel,
switch our other two workers to 6.1 and call things "resolved".

Yes, ideally we'd track it down and get it fixed properly but we're not
really setup to debug Debian bugs in old releases and we have other
more pressing problems.

Cheers,

Richard


  reply	other threads:[~2024-10-22  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17FE0CA1425F2338.24631@lists.openembedded.org>
2024-10-14 13:46 ` [OE-core] Latest AB-INT unexplained mystery failure Richard Purdie
2024-10-22 13:30   ` Ross Burton
2024-10-15  8:18 ` Richard Purdie
     [not found] ` <17FE55BCAF4D83DD.4702@lists.openembedded.org>
2024-10-14 16:11   ` Richard Purdie
2024-10-14 20:40   ` Richard Purdie
2024-10-15  8:23   ` Richard Purdie
2024-10-15 10:09   ` Richard Purdie
2024-10-19 11:05 ` Richard Purdie
     [not found] ` <17FFD5DF016C394D.24795@lists.openembedded.org>
2024-10-19 21:48   ` Richard Purdie
2024-10-21 10:55     ` Alexander Kanavin
2024-10-22  9:58       ` Richard Purdie [this message]
2024-10-22 19:48         ` Michael Halstead
2024-10-23 15:28         ` Khem Raj
2024-10-23 15:33           ` Alexander Kanavin
2024-10-23 15:35             ` Richard Purdie

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=f1b97191136f649bac813f2159e3a40345f387c8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=mhalstead@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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