I forgot to ask whether this means that you have U3 which runs your kernel fine.LiquidAcid wrote:The only reboot issue that I know of is gargabe in the UART FIFO, but that only affects u-boot, i.e. interrupts auto-boot and drops you to the prompt. See the corresponding patch in my 'stable' u-boot branch.
In any case, could you please comment on the following investigation?
For me, locking at 1Ghz is simply not an option, and since I am not a kernel hacker, I don't think I will succeed in providing something valuable without a very detailed guidance (I don't even know how to get logs when kernel panics, so I only observe the "alive" LED changes).... the problem is that the PMIC does not get reset on the U3.
I reported the issue on samsung ml a while ago, and I was not the only one having the issue. @mdrjr also confirmed and actually had a patch to reset pmic on the 4.8 kernel (which he deleted before making it public ).
Afaik 4.8 should still have the issue. I tried many things, and sometimes it looked like it was fixed, I could reboot sometimes, just to see the issue back after a while, it was pretty random. If the PMIC will not reset, it will keep whatever voltage it has on the next reboot, so it's actually pretty nasty - maybe the mali issue comes from that as well? But test the power source too.
Try changing the DT to have only one frequency available, e.g. lock it at 1Ghz, since that's the frequency uboot uses too. Also try disabling frequency scaling in kernel config, it will get your board to behave better, although you will still have issues.
if you know what you're doing, try to look at the reset code from the HK kernel (in the platform files), and copy the sequence (2 lines of code) to the new kernel (in the new generic reset driver).