Here's the console-ramoops I pulled from my device: https://pastebin.com/ddinyPzz
The first major error relating to the BIG cpu (that I noticed), was at lines 317 and 318 "_cpu_up: attempt to bring up CPU 4 failed"
However, the fatal error seems to occur at lines 439-451. Multiple errors about pll_clk_enable occur, here's some lines that I noticed.
Line 440: "variable_rate_pll_clk_enable: PLL a57_pll1 didn't lock after enabling for L value 0x50!"
And then at line 451: "Kernel panic - not syncing: failed to lock a57_pll1 PLL" From that point on, the kernel appears to go through the shutdown process.
For those who don't know, the cortex-a57 cores are the ones that make up the BIG cpu.
I tried to do some research on what PLL was (disclaimer, I am no expert whatsoever, so what I say may be wrong)
From what I could find, the PLL stands for phase-locked loop, and it's purpose is to control the frequencies of a CPU.
Intel has a post on possible causes for PLL losing lock: https://www.altera.com/support/suppo...loss-lock.html
I did some digging around in the kernel source code, and there are entries for "pll_clk_disable" in the PLL driver https://android.googlesource.com/ker...om/clock-pll.c
So maybe this means there's a way to somehow disable PLL?
So if any Devs, or anyone with experience on this, have an idea on how to possibly fix this, please give your thoughts. This problem is a relatively prominent one in this device, and it would be awesome if we could fix it.
Here's my questions to anyone who knows more about this,
Would it be possible to disable PLL?
Is PLL hardware based, or software?
And would it be possible to somehow build a kernel to fix this problem?