From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pramod Subject: Re: beagle hangs in uart3 disabling clocks Date: Tue, 5 Oct 2010 16:39:51 +0530 Message-ID: <4CAB077F.5020806@ti.com> References: <4CA9C5F6.7060902@ti.com> <87wrpy0xp3.fsf@deeprootsystems.com> <87iq1hzt3u.fsf@deeprootsystems.com> <4CAACFFF.9040702@ti.com> <4CAAF126.5080206@ti.com> <4CAAF6B4.4030708@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from arroyo.ext.ti.com ([192.94.94.40]:52081 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751172Ab0JELJt (ORCPT ); Tue, 5 Oct 2010 07:09:49 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley Cc: Ming Lei , Kevin Hilman , Govindraj , "Premi, Sanjeev" , "linux-omap@vger.kernel.org" On Tuesday 05 October 2010 03:33 PM, Paul Walmsley wrote: > 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 The hwmod debug messages will be seen when I enable them on the go with: echo -n 'file omap_hwmod.c +p' > /debug/dynamic_debug/control This will show lots of logs as below ending with UART3 clock disabling and a hang. omap_hwmod:omap_hwmod: uart1: idling omap_hwmod:omap_hwmod: uart1: disabling clocks omap_hwmod:omap_hwmod: uart2: idling omap_hwmod:omap_hwmod: uart2: disabling clocks omap_hwmod:omap_hwmod: uart1: enabling omap_hwmod:omap_hwmod: uart1: enabling clocks omap_hwmod:omap_hwmod: uart2: enabling omap_hwmod:omap_hwmod: uart2: enabling clocks omap_hwmod:omap_hwmod: uart3: idling omap_hwmod:omap_hwmod: uart3: disabling clock - Pramod