From: Kevin Hilman <khilman@deeprootsystems.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: NOTE: hwmod changes merged to linux-omap master for testing
Date: Tue, 05 Oct 2010 07:57:28 -0700 [thread overview]
Message-ID: <87eic4vg9z.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E9402DB90D031@dbde02.ent.ti.com> (Manjunath Kondaiah G.'s message of "Tue, 5 Oct 2010 12:06:17 +0530")
"G, Manjunath Kondaiah" <manjugk@ti.com> 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" <manjugk@ti.com> 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
prev parent reply other threads:[~2010-10-05 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 0:48 NOTE: hwmod changes merged to linux-omap master for testing Tony Lindgren
2010-10-04 7:49 ` G, Manjunath Kondaiah
2010-10-04 9:20 ` Govindraj
2010-10-04 11:34 ` G, Manjunath Kondaiah
2010-10-04 12:09 ` Ohad Ben-Cohen
2010-10-04 12:13 ` G, Manjunath Kondaiah
2010-10-04 12:13 ` Ohad Ben-Cohen
2010-10-04 12:20 ` G, Manjunath Kondaiah
2010-10-04 12:32 ` Ohad Ben-Cohen
2010-10-04 12:52 ` G, Manjunath Kondaiah
2010-10-04 22:29 ` Ohad Ben-Cohen
2010-10-07 0:04 ` Tony Lindgren
2010-10-07 8:17 ` G, Manjunath Kondaiah
2010-10-04 15:06 ` Kevin Hilman
2010-10-04 16:46 ` G, Manjunath Kondaiah
2010-10-04 18:26 ` G, Manjunath Kondaiah
2010-10-04 19:34 ` Kevin Hilman
2010-10-05 6:36 ` G, Manjunath Kondaiah
2010-10-05 14:57 ` Kevin Hilman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eic4vg9z.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.