public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dave Jones <davej@redhat.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: suspending to disk on FC6 not working
Date: Sun, 1 Oct 2006 07:30:32 +0200	[thread overview]
Message-ID: <20061001053032.GB1829@elf.ucw.cz> (raw)
In-Reply-To: <20061001050517.GE28868@redhat.com>

Hi!

>  > I had not noticed it was not loaded. This maybe a bigger problem. With
>  > the latest FC6 kernel this module gets loaded and thus suspend fails. I
>  > rebuilt the same kernel but plopped this patch in. The module does not
>  > want to load:
>  > 
>  > # /sbin/modprobe acpi-cpufreq
>  > FATAL: Error inserting acpi_cpufreq
>  > (/lib/modules/2.6.18-1.2708.cpufreq/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device
>  > 
>  > This is why suspend works. But now this module won't load.
> 
> Right, what the STICKY patch that you reverted does is it silences the
> failure, by not unloading the module when it fails to init.
> 
> What we want is the best of both worlds: Silence when its loaded and
> init fails, and no module around.  Hmm.

? Using more kernel memory when hardware can't do acpi_cpufreq just to
get a rid of message... seems like very bad tradeoff. ACPI tables are
not hotpluggable, so it _should_ be impossible to load that module...

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-10-01  5:30 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 22:55 suspending to disk on FC6 not working 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 [this message]
  -- 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:23 Pallipadi, Venkatesh
2006-09-29 21:35 Pallipadi, Venkatesh
2006-09-29 22:14 ` Pavel Machek
2006-09-29 22:25 ` Dave Jones
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=20061001053032.GB1829@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=davej@redhat.com \
    --cc=linux-pm@lists.osdl.org \
    /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