* Ard Biesheuvel <ardb@xxxxxxxxxx> [211117 08:29]: > On Wed, 17 Nov 2021 at 08:59, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > * Ard Biesheuvel <ardb@xxxxxxxxxx> [211116 22:03]: > > > Of course, I may have missed something, but I wouldn't expect a > > > fundamental flaw in this logic to affect only OMAP3/4 based platforms > > > in such a weird way. Perhaps there is something I missed in terms of > > > TLB maintenance, although I would expect the existing fault handler to > > > take care of that. > > > > Looks like disabling the deeper idle states for cpuidle where the CPUSs > > get shut down and restored seems to work around the issue at least for > > omap4. The assembly code is in arch/arm/mach-omap2/sleep44xx.S, and in > > sleep34xx.S for omap3. No idea so far what might be causing this.. > > > > Thanks Tony, that is very helpful. I have a Beaglebone white somewhere > so I'll try and reproduce it locally as well. I think with Beaglebone you may hit this only with suspend/resume if at all. On am335x cpuidle is not shutting down the CPU. And only some models will suspend to deeper idle states as it depends on the PMIC. If you have some test patch to try, just let me know. Regards, Tony
