public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: suspending to disk on FC6 not working
Date: Fri, 29 Sep 2006 22:14:41 +0000	[thread overview]
Message-ID: <20060929221440.GA6242@ucw.cz> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454ABBA55@scsmsx413.amr.corp.intel.com>

Hi!

> > > Could not power down device &q->lock: error -22
> > > Some devices failed to power down, aborting suspend
> >
> >Ok, I'm not quite sure how we got into this state.  Venkatesh, 
> >any ideas ?
> >acpi-cpufreq got quite a few changes between .17 and .18, including the
> >two large 'P-state coordination' change.
> >
> >Louis, I'm attaching two smaller changes that went into .18.
> >Can you apply those with -R, and see if either of those makes 
> >a difference?
> 
> cpufreq_cpu_data[] = NULL; only happens when acpi_cpufreq driver init
> fails;
> Looks like acpi_cpufreq driver init is failing at some point in this
> case and the driver is staying loaded after that failure. That in turn
> seems similar to one other bug I saw recently.

Uh, if acpi_cpufreq is built-in... you can't unload it when init
fails, so you need to handle that somehow...?

							Pavel
-- 
Thanks for all the (sleeping) penguins.

  reply	other threads:[~2006-09-29 22:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 21:35 suspending to disk on FC6 not working Pallipadi, Venkatesh
2006-09-29 22:14 ` Pavel Machek [this message]
2006-09-29 22:25 ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2006-10-01  5:07 Pallipadi, Venkatesh
2006-10-01  5:22 ` Dave Jones
2006-10-01 12:28   ` Rafael J. Wysocki
2006-10-01 18:36     ` Dave Jones
2006-10-01 18:38       ` Pavel Machek
2006-10-01 18:56         ` Dave Jones
2006-10-01  5:22 ` Louis Garcia
2006-09-29 22:55 Pallipadi, Venkatesh
2006-10-01  2:49 ` Louis Garcia
2006-10-01  3:21   ` Dave Jones
2006-10-01  5:00     ` Louis Garcia
2006-10-01  5:05       ` Dave Jones
2006-10-01  5:30         ` Pavel Machek
2006-09-29 22:23 Pallipadi, Venkatesh
2006-09-24 22:55 Louis Garcia
2006-09-25  7:16 ` Rafael J. Wysocki
2006-09-25 17:10   ` Louis Garcia
2006-09-25 18:43     ` Rafael J. Wysocki
2006-09-25 19:34       ` Louis Garcia
2006-09-25 20:15         ` Rafael J. Wysocki
2006-09-25 23:04           ` Louis Garcia
2006-09-26 10:00             ` Rafael J. Wysocki
2006-09-26 21:47               ` Louis Garcia
2006-09-26 22:01                 ` Rafael J. Wysocki
2006-09-26 22:15                   ` Pavel Machek
2006-09-26 22:26                     ` Rafael J. Wysocki
2006-09-26 22:39                       ` Louis Garcia
2006-09-26 22:45                         ` Pavel Machek
2006-09-26 22:54                           ` Rafael J. Wysocki
2006-09-26 22:58                             ` Pavel Machek
2006-09-26 23:09                               ` Louis Garcia
2006-09-26 23:12                                 ` Pavel Machek
2006-09-27  2:36                     ` Dave Jones
2006-09-27  2:51                       ` Dave Jones
2006-09-27  6:55                         ` Louis Garcia
2006-09-29 20:54                           ` Dave Jones

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=20060929221440.GA6242@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@lists.osdl.org \
    --cc=venkatesh.pallipadi@intel.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