Mark Brown broonie@kernel.org writes:
On Thu, Jul 18, 2019 at 04:28:08AM -0700, kernelci.org bot wrote:
Today's -next started failing to boot defconfig on rk3399-firefly:
arm64:
defconfig: gcc-8: rk3399-firefly: 1 failed labIt hits a BUG() trying to set up cpufreq:
[ 87.381606] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 200000 KHz [ 87.393244] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 408000 KHz [ 87.469777] cpufreq: cpufreq_online: CPU4: Running at unlisted freq: 12000 KHz [ 87.488595] cpu cpu4: _generic_set_opp_clk_only: failed to set clock rate: -22 [ 87.491881] cpufreq: __target_index: Failed to change cpu frequency: -22 [ 87.495335] ------------[ cut here ]------------ [ 87.496821] kernel BUG at drivers/cpufreq/cpufreq.c:1438! [ 87.498462] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
I'm struggling to see anything relevant in the diff from yesterday, the unlisted frequency warnings were there in the logs yesterday but no oops and I'm not seeing any changes in cpufreq, clk or anything relevant looking.
Full bootlog and other info can be found here:
I confirm that disabling CPUfreq in the defconfig (CONFIG_CPU_FREQ=n) makes the firefly board start working again.
Note that the default defconfig enables the "performance" CPUfreq governor as the default governor, so during kernel boot, it will always switch to the max frequency.
For fun, I set the default governor to "userspace" so the kernel wouldn't make any OPP changes, and that leads to a slightly more informative splat[1]
There is still an OPP change happening because the detected OPP is not one that's listed in the table, so it tries to change to a listed OPP and fails in the bowels of clk_set_rate()
Kevin