From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: NOTE: hwmod changes merged to linux-omap master for testing Date: Tue, 05 Oct 2010 07:57:28 -0700 Message-ID: <87eic4vg9z.fsf@deeprootsystems.com> References: <20101002004821.GN3117@atomide.com> <8762xi3sm1.fsf@deeprootsystems.com> <87pqvpyco5.fsf@deeprootsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:49160 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753283Ab0JEO5b (ORCPT ); Tue, 5 Oct 2010 10:57:31 -0400 Received: by iwn5 with SMTP id 5so8417994iwn.19 for ; Tue, 05 Oct 2010 07:57:31 -0700 (PDT) In-Reply-To: (Manjunath Kondaiah G.'s message of "Tue, 5 Oct 2010 12:06:17 +0530") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "G, Manjunath Kondaiah" Cc: Tony Lindgren , "linux-omap@vger.kernel.org" "G, Manjunath Kondaiah" writes: >> -----Original Message----- >> From: Kevin Hilman [mailto:khilman@deeprootsystems.com] >> Sent: Tuesday, October 05, 2010 1:05 AM >> To: G, Manjunath Kondaiah >> Cc: Tony Lindgren; linux-omap@vger.kernel.org >> Subject: Re: NOTE: hwmod changes merged to linux-omap master >> for testing >> >> "G, Manjunath Kondaiah" writes: > ... > >> > As I mentioned no changes to defconfig and it looks like >> cpu idle is >> > disabled and cpu idle wait is enabled in .config after running make >> > omap2plus_defconfig >> >> OK, my fault. I misread your bootlog, and now see that it's >> the default idle path that is triggering the fault, not CPUidle. >> >> I tried on my es2.0 panda and see the same thing now, dump below. >> The misc. PM warnings on boot are expected as OMAP4 does not have >> functioning PM support in mainline yet. The error that crashes is >> somewhat different, but also likely related to PM as it >> appears to be triggered the upon the first attempt at idle. >> >> I haven't debugged any further, but you might want to try >> again with enabling more verbose kernel debugging, specifically: >> >> CONFIG_DEBUG_BUGVERBOSE=y >> CONFIG_DEBUG_ERRORS=y >> >> as you shoul hopefully get some more information as to what >> causes the initial panic. > > After enabling above debug options also, I don't see any change in the log. > http://pastebin.com/mf8HvQCX Do you have 'debug' on your kernel command line? Kevin