popcornmix

I can reproduce this. The backtraces in kernel seemed pretty random to me, so probably a clock/voltage issue, rather than a kernel bug.

I can see the crash on a Pi3+. I couldn't provoke it on a Pi4. I added logging and last thing that occurred was a switch from ~300MHz to 1400MHz....

We have a workaround in latest rpi-update firmware that will disallow arm_freq_min below 600. A fuller fix is being worked on but will need more work/testing so will wait until...

There is a proper fix for this as in internal PR. I'll let you know when it reached rpi-update.

Latest rpi-update firmware contains a fix for this issue that doesn't involve limiting arm_freq_min. Please update and test.

It will come to apt but will take a while as we've just finalised a stable apt version and a commit like this (which affects clocks/plls) could do with some...

I don't see any connection with that backtrace and this issue. You'll need to find a way of provoking this reliably. Then confirm if issue still occurs without arm_freq_min. Also...

@MichaIng is all your testing with a Pi2? https://github.com/raspberrypi/linux/pull/3815 does enable additional arm frequency points on all Pi models. I suspect prior to 3815 300MHz wasn't being used when idle...

I agree the board revision is unlikely to be significant. Can you confirm that you are testing the same sdcard on each of the four Pi4's (just in case there...

Are you able to swap sdcard between a working and non-working board and confirm the problem remains with the board (and not the sdcard)?