If you look more carefully the first problem is actually a bus error: [ 15.776190] Unhandled fault: external abort on non-linefetch (0x1028) at 0xf9e3e044 [ 15.825925] PC is at omap_hwmod_read+0x14/0x28 [ 15.830583] LR is at omap_rtc_wait_not_busy+0x1c/0x44 I have no idea how the kernel manages to continue after a bus error in a driver (inside local_irq_disable even), but I wouldn't be inclined to take any later errors seriously. See also the "4.8 crash on BeagleBone" thread on linux-omap. Matthijs -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
