cc Tony Hi,
On Thu, 5 Apr 2012, Mohammed, Afzal wrote: > On Thu, Apr 05, 2012 at 15:03:36, Paul Walmsley wrote: > > Could you try booting with initcall_debug and posting the boot log? > > Logs as follows, thanks. ... > [ 6.065307] calling omap_mux_late_init+0x0/0x1a0 @ 1 Looks like a mux-related problem. Tony recently found some mux-related bugs that got merged with the v3.3 mach-omap2/serial.c - I wonder if they might be affecting your board too? - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
