public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Luke Gong <lukejgong@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Fail to suspend to ram: "Class driver suspend failed for cpu0"
Date: Thu, 20 Jan 2011 14:54:51 -0800	[thread overview]
Message-ID: <8762tjjidg.fsf@ti.com> (raw)
In-Reply-To: <AANLkTin-q5o1x=0Eu1HvwDZxuCAOsGiVySWHBuAW0v+C@mail.gmail.com> (Luke Gong's message of "Thu, 20 Jan 2011 16:16:58 -0500")

Luke Gong <lukejgong@gmail.com> writes:

> I have a beagle board with OMAP3530. I ported linux-omap-pm2.6.32 to
> this board. When I want to let it suspend to ram, 

This is an old kernel.  Any reason you're not using a newer kernel?

> it fails and I get
> the message "Class driver suspend failed for cpu0"

This is the CPUfreq driver failing to suspend, probably because there is
no CPUfreq driver implemented in your kernel.  Try disabling CPU_FREQ in
your kernel config.

Kevin

> . Here is the log:
>
> root@beagleboard:~# echo mem > /sys/power/state
> PM: Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.00 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> Suspending console(s) (use no_console_suspend to debug)
> omapfb omapfb: timeout waiting for FRAME DONE
> Class driver suspend failed for cpu0
> Restarting tasks ... done.
>
> *********************************************
>
> Is there any idea to fix this problem? Thanks.

  reply	other threads:[~2011-01-20 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 21:16 Fail to suspend to ram: "Class driver suspend failed for cpu0" Luke Gong
2011-01-20 22:54 ` Kevin Hilman [this message]
2011-01-20 23:32   ` Luke Gong
2011-01-21  4:23     ` Vishwanath Sripathy
2011-01-21 15:28       ` Luke Gong
2011-01-21  5:09     ` Kevin Hilman
2011-01-21 15:30       ` Luke Gong

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=8762tjjidg.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lukejgong@gmail.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