From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Suspend to RAM broken on BeagleBoard ?
Date: Fri, 10 Sep 2010 14:54:23 -0700 [thread overview]
Message-ID: <87sk1h4640.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100910174814.6e5d439e@surf> (Thomas Petazzoni's message of "Fri, 10 Sep 2010 17:48:14 +0200")
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
>
> I've tested the current linux-omap Git tree and Kevin's pm-core branch
> on a BeagleBoard using the omap3_defconfig, and when trying a suspend
> to RAM, I get a "Class driver suspend failed for cpu0" :
> # echo mem > /sys/power/state
> [ 93.395050] PM: Syncing filesystems ... done.
> [ 93.410827] Freezing user space processes ... (elapsed 0.01 seconds) done.
> [ 93.434570] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
> [ 93.458557] Suspending console(s) (use no_console_suspend to debug)
> [ 93.590728] PM: suspend of devices complete after 119.629 msecs
> [ 93.593902] PM: late suspend of devices complete after 3.112 msecs
> [ 93.594421] Class driver suspend failed for cpu0
It's the CPUfreq driver that's failing to suspend.
> [ 93.595153] PM: early resume of devices complete after 0.518 msecs
> [ 93.887603] PM: resume of devices complete after 292.052 msecs
> [ 93.922851] Restarting tasks ... done.
>
> Is this a known issue ?
Yes, CPUfreq is not supported in l-o master or pm-core (only in the full
pm branch.) If you Kconfig out CPUfreq, this failure will go away.
[...]
Kevin
next prev parent reply other threads:[~2010-09-10 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 15:48 Suspend to RAM broken on BeagleBoard ? Thomas Petazzoni
2010-09-10 17:00 ` Felipe Balbi
2010-09-10 18:47 ` Thomas Petazzoni
2010-09-11 14:21 ` Felipe Balbi
2010-09-10 21:54 ` Kevin Hilman [this message]
2010-09-11 9:00 ` Thomas Petazzoni
2010-09-13 14:56 ` Kevin Hilman
2010-09-13 15:39 ` Thomas Petazzoni
2010-09-13 16:25 ` Grazvydas Ignotas
2010-09-13 19:01 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2010-09-10 20:28 msinger
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=87sk1h4640.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).