I'm seeing the same bus error (in omap_rtc_wait_not_busy's attempt to poll the BUSY flag) with both my customized kernel and even just Robert Nelson's 4.8.0-rc5-bone1 debian package with default DT and no custom kernel parameters. Using loglevel=debug dyndbg="file omap_hwmod.c +p" shows the following rtc-related activity: [ 0.187708] omap_hwmod: dt rtc[0] uses hwmod rtc [ 0.187716] omap_hwmod: rtc: no MPU register target found [ 0.187731] omap_hwmod: rtc: MPU register target at va f9e3e000 [ 0.187738] omap_hwmod: rtc: looking up clocks [ 0.187745] omap_hwmod: rtc: associated to clkdm l4_rtc_clkdm [ 0.207820] omap_hwmod: rtc: enabling [ 0.207829] omap_hwmod: rtc: enabling clocks [ 0.207836] omap_hwmod: rtc: _omap4_enable_module: 2 [ 0.207974] omap_hwmod: rtc: resetting [ 0.208110] omap_hwmod: rtc: idling [ 0.208117] omap_hwmod: rtc: _omap4_disable_module [ 0.208123] omap_hwmod: rtc: disabling clocks [ 5.261634] omap_hwmod: rtc: enabling [ 5.265330] omap_hwmod: rtc: enabling clocks [ 5.269619] omap_hwmod: rtc: _omap4_enable_module: 2 [ 5.274613] <crash> Adding ti,no-reset-on-init; ti,no-idle-on-init; to the rtc DT node lets me boot without any further problems. I'm assuming this merely hides the problem rather than solving its root cause though. I can't think of a good reason for the RTC to give a bus error unless it hasn't actually been reenabled properly in PRCM. 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
