On 6 January 2017 at 12:03, Will Deacon <will.deacon@xxxxxxx> wrote: > On Thu, Jan 05, 2017 at 08:49:44PM +0100, Robert Richter wrote: >> On 05.01.17 13:22:00, Robert Richter wrote: >> > On 05.01.17 12:08:20, Will Deacon wrote: >> > > I really can't see how the fix causes a crash, and I couldn't reproduce >> > > it on any of my boards, nor could any of the Linaro folk afaik. Are you >> > > definitely running mainline with just these two patches from Ard? >> > >> > Yes, just both patches applied. Various other solutions were working. >> >> I have retested the same kernel (v4.9 based) as before and now it >> boots fine including rtc-efi device registration (it was crashing >> there): >> >> rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0 >> >> There could be a difference in firmware and mem setup, though I also >> downgraded the firmware to test it, but can't reproduce it anymore. I >> could reliable trigger the crash the first time. >> >> FTR the oops. > > Hmm, I just can't help but think you were accidentally running with > additional patches when you saw this oops previously. For example, > your log looks very similar to this one: > > http://lists.infradead.org/pipermail/linux-arm-kernel/2016-December/473666.html > > but then again, these crashes probably often look alike. > These are quite different, in fact. In James's case, the UEFI memory map was missing some entries, so not all memory regions that the firmware expected to be there were actually mapped, hence the all-zero *pte. In Robert's case, it looks like the UEFI runtime services page tables are corrupted, i.e., *pte has RES0 bits set. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
