About the time you were writing this, I'd hacked up: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=de3e2253482b6d9df1137128a9fde35dec8fd915 and put it into a build on the

Thanks for the patch, I ran with it for a number of runs. I have not seen .38 break in the way master or master-next with .37 did. I've ran several and 50% of the time .37 would hang in ltp. Can we

<richard.purdie@...> wrote: sent. I cherry picked it from my queue and sent it individually. I'll continue testing the rest of my updates. Bruce -- - Thou shalt not follow the NULL

I switched to Bruce's 5.12 patches. Unfortunately even with

The ubuntu2004-arm-1 worker has been unstable in the past and we reduced the number of simultaneous builds from 3 to 1 to see if that would stop the crashes. It didn't at first but now the crashes

Hi Alexandre, Any update on the list/spreadsheet? Tony is getting going on valgrind and he'll start with:    https://bugzilla.yoctoproject.org/show_bug.cgi?id=14294    [Bug 14294] valgrind

Hi, Ah sorry, I forgot to send it. It is up to date with what was triaged last week: https://docs.google.com/spreadsheets/d/1bviDvW1SRwflofKLx9SwPUTWE3sBkvL3eb1PKnmZJcM/edit?usp=sharing This is

Today's failure for analysis is a qemuarm failure where all the test images  failed at the same time: https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/3493 We have's Randy+team's

Hello 민재, As discussed last week, you are on SWAT duty this week, could you confirm you'll be able to work on the topic? I hope you moved without any issue. Regards, -- Alexandre Belloni,

Hi Paul, Thanks for these. Unfortunately I think there is still a gremlin somewhere as this was included in an autobuilder test build that is showing as

<richard.purdie@...> wrote: (╯°□°）╯︵ ┻━┻ If you're planning to take the day off don't worry about investigating these. I'll take a look at the patches again on

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/3538 failure during execution of dnf --help Traceback from qemu logs fro thre 5.10 kernel (full log attached): qemux86-64 login: [

Not cross posted but mentioned here for info. Seeing if the qemu devs have any ideas. Cheers, Richard

https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1969 died with the following kernel panic: [ 2650.301002] option changes via remount are deprecated (pid=15940 comm=mount) [

Interesting. The last two stalls/traps that you sent were both x86-64. Are we only seeing this on x86 ? I'll have another look at the patches we carry, but there really shouldn't be anything that

Also, a hung qemu build, this one has been hanging for 3 days: https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1963 Top of the kernel boot log for version info: [ 0.000000]

Not sure. We have seen some builds fail but I haven't dived into properly get down to the real cause. We run many more 64 builds than plain x86. They're happening regularly enough to be really

<richard.purdie@...> wrote: I remember about 10 years ago at Wind River, we had similar issues with ltp. Are we running ltp under the root user ? or is it running as a regular user

Attached is v2. This has .41 merged to v5.10/base and sets the appropriate SRCREV. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force

Hi Richard, https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/73 showed up in overnight testing with an issue in meta-aws. Cheers, Richard