From: Dave Jones <davej@redhat.com>
To: Louis Garcia <louisg00@bellsouth.net>
Cc: linux-pm@lists.osdl.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: suspending to disk on FC6 not working
Date: Sat, 30 Sep 2006 23:21:35 -0400 [thread overview]
Message-ID: <20061001032135.GB21796@redhat.com> (raw)
In-Reply-To: <1159670982.3714.3.camel@soncomputer>
On Sat, Sep 30, 2006 at 10:49:42PM -0400, Louis Garcia wrote:
> On Fri, 2006-09-29 at 15:55 -0700, Pallipadi, Venkatesh wrote:
> > That's it.. This issue seems to be a side effect of that patch...
> >
> > Louis: After normal boot of 2.6.18, if you are not seeing the directory
> > /sys/devices/system/cpu/cpu0/cpufreq
> >
> > Then try reverting this patch
> > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
> > ommit;h=911cb74bb9e77e40749abc2fca6fe74d87d940f3
> >
> > and then check whether the suspend resume issue goes away.
> >
> > Thanks,
> > Venki
>
> I reverted this patch and my suspend issue is gone. Though the
> directory /sys/devices/system/cpu/cpu0/cpufreq is non existent, with or
> without this patch.
Ok, I've backed that out in cpufreq.git, it'll go along to Linus soon.
If you build acpi-cpufreq as a module, and you modprobe acpi-cpufreq,
does it fail silently ? Or does it revert us back to the behaviour
where it's noisy again?
Dave
next prev parent reply other threads:[~2006-10-01 3:21 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 [this message]
2006-10-01 5:00 ` Louis Garcia
2006-10-01 5:05 ` Dave Jones
2006-10-01 5:30 ` Pavel Machek
-- 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=20061001032135.GB21796@redhat.com \
--to=davej@redhat.com \
--cc=linux-pm@lists.osdl.org \
--cc=louisg00@bellsouth.net \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.