On Tue, 5 Oct 2010, Pramod wrote: > On Tuesday 05 October 2010 03:17 PM, Paul Walmsley wrote: > > On Tue, 5 Oct 2010, Pramod wrote: > > > > > On Tuesday 05 October 2010 12:49 PM, Paul Walmsley wrote: > > > > On Tue, 5 Oct 2010, Pramod wrote: > > > > > > > > > I applied this patch on my kernel which is based on android-2.6.32 > > > > > enabling > > > > > dynamic printks. I still see the console hang after enabling the logs > > > > > in > > > > > hwmod. > > > > > > > > > > I am using zoom3 board. Can you please let me know which defconfig > > > > > from lo > > > > > master branch can be used to test on zoom3? I would like to test this > > > > > patch > > > > > with lo master branch and zoom3. > > > > > > > > Could you please paste your boot log messages here? > > > > > > > > > > > > - Paul > > > > > > Hi paul, > > > These are the boot log messages. > > > > Is that with the patch applied or without it? If without, please post the > > log messages from a boot after you apply the patch. > > > > - Paul > > These logs are with the patch shared by you.
Looks to me like it boots fine. If you had hwmod debugging enabled, your kernel should have crashed after omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0 omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1 omap-hsuart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2 ... but it didn't crash there. I'm not seeing any hwmod debug messages though, so you probably don't have DEBUG defined in omap_hwmod.c. So, I suspect whatever problem you're seeing is unrelated to the problem that the patch was intended to solve. - 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
