On Wed, Mar 13, 2024 at 05:13:33PM +0000, Russell King wrote: > So, I wonder whether what you're seeing is a latent bug which is > being tickled by the presence of the CPU masks being off-stack > changing the kernel timing. > > I would suggest the printk debug approach may help here to see when > the OPPs are begun to be parsed, when they're created etc and their > timing relationship to being used. Given the suspicion, it's possible > that the mere addition of printk() may "fix" the problem, which again > would be another semi-useful data point. It might be an init order problem. Passing "initcall_debug" on the cmdline might help a bit. It would also be useful in dev_pm_opp_set_config(), in the WARN_ON block, to print opp_table->opp_list.next to get an idea whether it looks like a valid pointer or memory corruption. -- Catalin
