On Mon, Jul 29, 2013 at 08:11:39AM +0000, Paul Walmsley wrote: > On Thu, 25 Jul 2013, Aaro Koskinen wrote: > > > On Tue, Jul 16, 2013 at 07:58:34PM +0300, Aaro Koskinen wrote: > > > I get the following boot crash on N950/RM-680 (3630) with unpatched > > > 3.11-rc1. The crash looks specific to 3630 (it happens during > > > omap3630_init_late), also the same kernel binary works with N900/RX-51 > > > (3430). You can find the .config after the crash. > > > > I put a debug print to _omap_hwmod_mux_handle_irq > > (omap_hwmod_mux_scan_wakeups), and it seems when the crash happens the > > pad name is always "uart3_rx_irrx.uart3_rx_irrx". I made another hack > > and just "continue" if the pad name is this, and the crash is gone. > > > > Any ideas? > > Nothing comes to mind, but it's worth mentioning that this doesn't happen > on the 37xx EVM here. So it's probably RM-680-specific. Probably timing specific... I enabled CONFIG_DEBUG_FS and the crash went away. A. -- 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
