On 22/07/2019 16:31, Vicente Bergas wrote: > Hi, i have been running linux on rk3399 booted with kexec fine until 5.2 > From 5.2 onwards, there are memory corruption issues as reported here: > http://lkml.iu.edu/hypermail/linux/kernel/1906.2/07211.html > kexec has been identified as the principal reason for the issues. > > It turns out that kexec has never worked reliably on this platform, > i was just lucky until recently. > > Please, can you provide some directions on how to debug the issue? > > The latest test performed is: > 1.- Boot v5.3-rc1 > 2.- Kexec into v5.2.2 > 3.- The kernel reports nothing (earlycon not enabled) and does not boot. > The same kernel v5.2.2 works fine when booted without kexec. Is there a known kernel where kexec was working (v5.2 e.g.)? If you can find one, you can run git bisect to find the commit that breaks things. Apart from that you should try to enable earlycon on your kernel you want to kexec into, so at least you can see if it crashes in the new kernel. If you still don't see anything you can try to use prugatory printing (if you use kexec_load and not kexec_file_load). I have a work-in-progress patches that I can share with you if needed. Just let me know. Regards, Matthias > > Regards, > Vicenç. > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel _______________________________________________ Linux-rockchip mailing list Linux-rockchip@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-rockchip
