On Mon, May 24, 2021 at 11:31 AM Richard Purdie
<richard.purdie@...> wrote:

On Sun, 2021-05-23 at 07:42 -0400, Bruce Ashfield wrote:

On Sun, May 23, 2021 at 6:36 AM Richard Purdie
<richard.purdie@...> wrote:

On Sun, 2021-05-23 at 11:33 +0100, Richard Purdie via lists.yoctoproject.org wrote:

https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1932

Oddly enough,
https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1933
on centos7-ty-4 (master build) is locked up with pretty much exactly
the same issue/ps output/tests/dmesg.

The first one above was debian10-ty-1 with master-next.

Recent kernel version bump?

I can't think of anything specific that would cause those issues, but the
Wind River guys did report some bad iommu patches that were part of
5.10.37

I've merged .38, which has the fixes, but I haven't sent the bumps yet.
It is worth trying the attached SRCREV patch, to see if there's any
change in behaviour.

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 upgrade to .38 ASAP please? :)

sent. I cherry picked it from my queue and sent it individually.

I'll continue testing the rest of my updates.

Bruce

This is obviously a separate issue to the rcu stalls but I also think that
is 5.10 related.

Cheers,

Richard

--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II