Hi, On 08/12/2021 22:04, Andreas Kemnade wrote: > Hi, > > On Wed, 8 Dec 2021 21:57:00 +0100 > Pavel Machek <pavel@xxxxxx> wrote: > >> Hi! >> >> You may want to cc: linux-kernel@xxxxxxxxxxxxxxx and >> phone-devel@xxxxxxxxxxxxxxx, since this is kernel issue. >> >>>> I am back with a bit more news, but no solution. >>> >>> It looks like commit fb2c599f056640d289b2147fbe6d9eaee689f1b2 ("ARM: >>> omap3: enable off mode automatically") is causing these failures on the >>> Nokia N900. Reverting this commit on top of v5.10 (with >>> 21b2cec61c04bd175f0860d9411a472d5a0e7ba1 also reverted), makes the >>> problem go away (I tried 10 times). >>> >>> The same holds for 5.15.y, just reverting >>> fb2c599f056640d289b2147fbe6d9eaee689f1b2 makes the system "stable" (at >>> least the problem reported in the first email is gone). >>> >>> Perhaps the "pwrst->next_state" change is causing these problems, since >>> I can enter OFF mode just fine with init=/bin/sh and a custom >>> script? >> >> fb2c599f056640d28 has some hints in it. Perhaps Andreas can mention >> what boards he tested it on? >> > well, I tested it on gta04a4 and gta04a5 (both dm3730). > There is one 1Ghz issue at least on the a5, so I disabled that opp. > >> And rather than reverting it, we may want to delete ti,twl4030-idle* >> hints from n900 device tree for now? >> > well, it has side effects on power consumption, power consumption > should be worse without ti,twl4030-idle-*. So the real solution would > be to understand what is causing the trouble here. What I have seen is that if off mode is enabled from userspace (debugfs), it does not cause a problem (or I don't hit the problem at least). That said, my off mode tests are pretty minimal with init=/bin/sh, and I haven't gotten a fully booted (with lots of modules loaded, gui and daemons) system to enter off mode yet. But as noted before, sometimes this problem would occur not on boot, but far into the boot process (~4 minutes after power up), and that problem is also gone now with the revert, so there's something going on... I can't really comment on what would be causing the trouble specifically (I'm not really familiar with omap pm), just noticed the regression for the N900, where off mode does appear to work, but this commit/method doesn't at least. I'm also not sure if removing the hint from the device tree is the right way to go - I'm happy to see off mode getting some more testing by turning it on by default. Regards, Merlijn