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