From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-vk1-f175.google.com (mail-vk1-f175.google.com [209.85.221.175]) by mx.groups.io with SMTP id smtpd.web09.272.1623449902211758048 for ; Fri, 11 Jun 2021 15:18:22 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ewZ4LGz0; spf=pass (domain: gmail.com, ip: 209.85.221.175, mailfrom: alex.kanavin@gmail.com) Received: by mail-vk1-f175.google.com with SMTP id j19so2858996vkj.0 for ; Fri, 11 Jun 2021 15:18:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zXWEtcZKjPtuz79yyccNcG19ldWMPEXgZVExj+3aN3k=; b=ewZ4LGz0IZ9TU8Q7wiYb7ku60Y/6ErVID4o83mzwuEA7aYDBO5Gm0tY0T0KCuMVBrh EJK09RhRoI8EcSgMdyVZAlWuY63zEm6Pd44i9FYpW8Hc+lkQh9G3fm91Er4bbAQarg0/ 1WIeKNfFvAjKBKC0QagQ2JW+1Cl6HtMfwC+l9F4ciAw5vyiwqXAotCV+HF1a3tCJs3NO poCkMzsBdouP/bxAJyue6KMjHnN+S+ND2yZF2/xscvq7qXXhR/YqIi2MSxiWva7Lp3pj xO+TOnYd4V5SvGRvxiHi0uIqsSYeauUvL+zLTXt0gZ1+F+A/wUpE2O0gkQy8n5WNa38y 6rxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zXWEtcZKjPtuz79yyccNcG19ldWMPEXgZVExj+3aN3k=; b=Ik4wZBqjLKlXdJofM6Sq1Q7BKgukITEaOJ50yCdyvaPF9DPMUdGSSKQYd8fKxhyoo2 D+0Ic0A3XmyhmAZglpiQuVOTMmRcPXxfmngCEMjvLqhduY/2pKjFQ0RI2Y6FU9BZFmsV E9VC9uL63LYqR0kqZfQ9FxY49+3rWj4cC+UTst54q7VQXRf5PZfQQaeWN1WKfaSiBcNv uahPi3vX8gaMg/NO3ZVAzJ/UNPhUVpDK49tbrCQS4TIzm7/C8qHcvM8GlL8UBurA7Rbm EjayfM9Cb1rNUK7Xieq0+XTgyFmLjPQ1y8xw0tAHQLGL2+vw56Yxyc8WXdK/kueWADpu xeuA== X-Gm-Message-State: AOAM531l2He6FoxCnRQ0+9iC7U7Ac8QA2tqAYeYpRb1WxvJ4x4bSLX6d scLMXTap8wRiwCB6HdnJGNPt9bBJoJGD6WhAdWQ= X-Google-Smtp-Source: ABdhPJxV/z0qlzAy3BWw4fwdFIHsqXrDSpwDoz2rqChmLkg1csNO6EmlVPmdvTBcG561XyPzo8nGicdespOMbn3KZrc= X-Received: by 2002:a1f:1d4a:: with SMTP id d71mr11219925vkd.0.1623449901306; Fri, 11 Jun 2021 15:18:21 -0700 (PDT) MIME-Version: 1.0 References: <20210604091458.1381144-1-alex.kanavin@gmail.com> <20210604091458.1381144-4-alex.kanavin@gmail.com> <1685B658849E960A.4717@lists.openembedded.org> <50a73766-dc52-0600-a6cd-7ab422030782@gmail.com> <7e56d093ba6c1390cec71ef3a362abe84ce735bb.camel@linuxfoundation.org> <2ac70a7b01743192ae4ec42b2b1eee18becde25d.camel@linuxfoundation.org> In-Reply-To: From: "Alexander Kanavin" Date: Sat, 12 Jun 2021 00:18:09 +0200 Message-ID: Subject: Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3 To: Michael Halstead Cc: Richard Purdie , Khem Raj , Bruce Ashfield , OE-core Content-Type: multipart/alternative; boundary="000000000000ad988405c484e266" --000000000000ad988405c484e266 Content-Type: text/plain; charset="UTF-8" I think the easiest is to run the genericx86 job on the worker. If the problem exists, you'll see a failure like this one: https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/3523/steps/12/logs/stdio Alex On Fri, 11 Jun 2021 at 23:56, Michael Halstead < mhalstead@linuxfoundation.org> wrote: > I've switched centos8-ty-2.yocto.io over to Stream and it's now running > kernel 4.18.0-310.el8.x86_64. I'm not sure how to test if the problem > still exists but I don't see a related entry in the changelog so I expect > it does. > > Alex, can you check or send me a bit more info about how to check myself? > > On Wed, Jun 9, 2021 at 7:07 AM Alexander Kanavin > wrote: > >> On Wed, 9 Jun 2021 at 13:37, Richard Purdie < >> richard.purdie@linuxfoundation.org> wrote: >> >>> Thanks Michael and Alex. We can therefore pretty safely say that >>> something was >>> broken between the 240 and 305 of the centos8 kernel for the 32 bit >>> syscall >>> utimensat syscalls. >>> >>> I did poke around https://github.com/kernelim/linux/tree/centos8 which >>> does >>> have a kernel diff but it is huge and you have to clone the repo to get >>> it. >>> >>> git show a3342908613ba72a84f652ca7a56c3e2113bda12 | grep sys_utimensat >>> -C 40 >>> >>> shows they did add the syscalls in that kernel. >>> >>> So this does look to be a RedHat issue. Not sure if we want to report it >>> to them? Can we run the autobuilders on the older kernel for now until >>> they hopefully fix it? >>> >> >> Centos 8 will be discontinued in just over 6 months ( >> https://www.centos.org/centos-linux/) >> so I think at least one of the centos 8 workers should be updated to >> centos stream 8 >> (https://www.centos.org/centos-stream/ - includes instructions) and take >> it from there. >> >> Alex >> > > > -- > Michael Halstead > Linux Foundation / Yocto Project > Systems Operations Engineer > --000000000000ad988405c484e266 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I thi= nk the easiest is to run the genericx86 job on the worker. If the problem e= xists, you'll see a failure like this one:

https://= autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/3523/steps/12/log= s/stdio

Alex

On Fri, 11 Jun 2021 at 23:56, Michael Halstea= d <mhalstead@linuxfound= ation.org> wrote:
I've switched centos8-ty-2.yocto.io over to Stream and = it's now running kernel 4.18.0-310.el8.x86_64. I'm not sure how to = test if the problem still=C2=A0exists but I don't see a related entry i= n the changelog so I expect it does.

Alex, can you c= heck or send me a bit more info about how to check myself?

<= div class=3D"gmail_quote">
On Wed, Jun= 9, 2021 at 7:07 AM Alexander Kanavin <alex.kanavin@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
On Wed, 9 Jun 2021 = at 13:37, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:=
Thanks Michael = and Alex. We can therefore pretty safely say that something was=C2=A0
broken between the 240 and 305 of the centos8 kernel for the 32 bit syscall=
utimensat syscalls.

I did poke around https://github.com/kernelim/linux/tr= ee/centos8 which does
have a kernel diff but it is huge and you have to clone the repo to get it.=

git show a3342908613ba72a84f652ca7a56c3e2113bda12 | grep sys_utimensat -C 4= 0

shows they did add the syscalls in that kernel.

So this does look to be a RedHat issue. Not sure if we want to report it to them? Can we run the autobuilders on the older kernel for now until
they hopefully fix it?

Centos 8 will be discontinued in just over= 6 months=C2=A0 (https://www.centos.org/centos-linux/)
so I think at = least one of the centos 8 workers should be updated to centos stream 8
=
(https://www.centos.org/centos-stream/ - includes instructions) and= take it from there.

Alex


--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
--000000000000ad988405c484e266--