Hi Afzal, On Thu, Apr 5, 2012 at 3:47 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > 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? Can you try this patch [1], Just to confirm its serial mux issue however still the patch is not aligned on how to fix it. -- Thanks, Govindraj.R [1]: http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg65347.html -- 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
