On Thu, Jun 3, 2021 at 8:51 AM Richard Purdie
On Thu, 2021-06-03 at 08:34 -0400, Bruce Ashfield wrote:
Interesting.Not sure. We have seen some builds fail but I haven't dived into properly
The last two stalls/traps that you sent were both x86-64. Are we only
seeing this on x86 ?
get down to the real cause. We run many more 64 builds than plain x86.
I'll have another look at the patches we carry, but there reallyThey're happening regularly enough to be really annoying but not
shouldn't be anything that could trigger something like this (famous
If these are happening regularly enough, we could change the
qemux86-64 branch to v5.10/base temporarily. That would be a pure
upstream -stable, and would help rule out the yocto patches if the
issues still occur.
regularly enough to be sure any given fix fixes things :(
I thought we had resolved the ltp hang but see my other email, I think
we just got lucky/unlucky with the kernel uprev and some good builds.
The traceback in mkdir is interesting and worrying.
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 ?
I think these are related and we sometimes crash the kernel sometimes not.
There is something very wrong somewhere. I'm happy to try changing
qemux86-64 and seeing if we continue to see issues or not but it will
take a week or so to be sure.
Attached is the patch to do that, just for qemux86-64 (5.10). It
triggers a config warning (as expected), and I documented that in the
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II