Weird signal issues using yocto's warrior busybox (aarch64) when memory is cached

[Stefan Seyfried]

Am 30.01.20 um 19:23 schrieb Sergio Paracuellos:

>> First things first, do you trust the hardware?  If the system swapped
>> out some pages and then read them back in and the controller or storage
>> device gave back bad data, this could cause all sorts of crashes.  Maybe
>> run a memtest, too, unless you can reproduce the issue on multiple
>> different machines.
> 
> I am able to reproduce the issue using different SOMs with its own RAM
> chip on it, and its own mmc storage device where the system is
> installed so I
> am pretty sure the hardware is not the problem here.

Then look at the kernel.
Use an older / newer one.
Use a different compiler to build everything.

Even nowadays, arm64 is still an exotic architecture (outside of some embedded niches and phones, but they all use their
own, often old and patched-to-hell toolchain).

Try building busybox with another toolchain / distribution (use the crap that came with the board from the vendor
instead of yocto, chances are the vendor has patched the hell out and into the old crap they give you to make it run on
their broken hardware ;-))

BTDT.

>> I just had a USB thumb drive corrupt a file with no warning, so it was
>> fresh on my mind.

-- 
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman