From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Warnings: pm branch
Date: Tue, 11 Aug 2009 08:27:16 -0700 [thread overview]
Message-ID: <873a7y74mj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F5989815@dbde02.ent.ti.com> (Vikram Pandita's message of "Tue\, 11 Aug 2009 20\:25\:17 +0530")
"Pandita, Vikram" <vikram.pandita@ti.com> writes:
> Has anyone send these warning logs on the pm branch on kevin's tree [1]
> This seems to be some issue in CpuIdle path with interrupts?
>
> <4>WARNING: at arch/arm/kernel/process.c:171 cpu_idle+0x60/0x88()
> WARNING: at arch/arm/kernel/process.c:171 cpu_idle+0x60/0x88()
> <d>Modules linked in:Modules linked in:
> [<c0031344>] [<c0031344>] (unwind_backtrace+0x0/0xdc) (unwind_backtrace+0x0/0xdc
> ) from [<c0057a08>] from [<c0057a08>] (warn_slowpath_common+0x48/0x60)
> (warn_slowpath_common+0x48/0x60)
> [<c0057a08>] [<c0057a08>] (warn_slowpath_common+0x48/0x60) (warn_slowpath_common
> +0x48/0x60) from [<c002d204>] from [<c002d204>] (cpu_idle+0x60/0x88)
> (cpu_idle+0x60/0x88)
> [<c002d204>] [<c002d204>] (cpu_idle+0x60/0x88) (cpu_idle+0x60/0x88) from [<c0008
> a70>] from [<c0008a70>] (start_kernel+0x234/0x28c)
> (start_kernel+0x234/0x28c)
> [<c0008a70>] [<c0008a70>] (start_kernel+0x234/0x28c) (start_kernel+0x234/0x28c)
> from [<80008034>] from [<80008034>] (0x80008034)
> (0x80008034)
>
Yes, I've seen it, but have yet to debug it.
This warning is from the generic ARM idle loop reporting that the OMAP
idle path is returning with IRQs disabled.
Kevin
next prev parent reply other threads:[~2009-08-11 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 14:55 Warnings: pm branch Pandita, Vikram
2009-08-11 15:27 ` Kevin Hilman [this message]
2009-08-12 9:48 ` Hemanth V
2009-08-12 12:54 ` Hemanth V
2009-08-12 13:28 ` Kevin Hilman
2009-08-12 13:38 ` Sripathy, Vishwanath
2009-08-12 14:15 ` Kevin Hilman
2009-08-12 14:22 ` Hemanth V
2009-08-12 14:38 ` Kevin Hilman
2009-09-30 17:32 ` Kevin Hilman
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=873a7y74mj.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox