<alexandre.belloni@...> wrote: thanks, the good thing is that these packages are quite sticky to glibc internals so usually an upgrade if available for them will sort things out, glibc is

Hello, I've been testing multiple versions of Khem's branch for glibc2.34 Everything apart from non-gpl3 builds fine. There is a patch from Khem to solve this issue, I didn't apply/test yet: [yocto]

Hi Alexandre and team, Sure, I can 'swat' next week. lsg

Hello Leonardo, You are the next one on the SWAT Team members list (https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Members) and SWAT duty will rotate to you at EOD

I have some good news. Now that we have merged the rcu stall crash fix: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=1f802cdf857475eefb9f3ae5032a6f1ce3e01d97 I think that the cause of some

I realised there was a potential lock issue in the rcu stall code in the kernel. In looking into it with Paul we found that upstream have a fix queued for the same

I formed a new plan and set the stall detector to 3 seconds instead of  21 seconds with this hack in

Can this be keyed off of DEBUG_BUILD variable? -- Regards, Denys Dmytriyenko <denis@...> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69 1186

<richard.purdie@...> wrote: Richard, As mentioned earlier, we do have the kernel debug fragments available (as well as a 'developer' kernel type). We can't globally enable the

We have info all over the place relating to our "rcu stall" issue on the  autobuilder. This is an attempt to document what we know and what we don't. We see builds fail periodically where there is

Dropped the wider list but as I said to Richard, I wanted to confirm that this bug is really gone. I ran 100 tests overnight and it seems to be dead Jim. $ bitbake core-image-sato && \ for i in

Yes, that's fine. Ross <alexandre.belloni@...> wrote:

Hello Ross, SWAT duty should rotate to you next week. Will you have some time to work on that? Thanks! -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com

As a note for swat, I filed 14438 for: https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1484 since I could see why it failed. Not sure why swatbot has failed but the web interface

Awesome work in tracking that down, much appreciated, thanks! Curious what upstream will make of it now... Cheers, Richard

[Re: [swat] ltp failures on autobuilder] On 11/06/2021 (Fri 14:19) Richard Purdie wrote: For the mail archive trail, and for those not follwing the ongoing research on IRC, we are hopeful that this

Isolated down to CONFIG_SCHED_DEBUG=y being the line which somehow "fixes" the crash. I can enable all the above apart from that and we can reproduce it. Also, I changed gatesgarth to use qemu 5.2.0

also: IMAGE_CLASSES += "testimage" QEMU_USE_KVM_qemux86-64 = "True" Good news (for me) is that Randy and Paul can now reproduce this with the above  additional key pieces of config. We have

It became clear there is also an: IMAGE_CLASSES += "testimage" but the INHERIT people are using shouldn't make any real difference to  the test. I've never seen that hrtimer message... but I do

I tried to reproduce this on a Ubuntu-18.04.3 system with: Linux ala-lpggp3 5.4.0-72-generic #80~18.04.1-Ubuntu SMP Mon Apr 12 23:26:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Using