From: Dave Jones <davej@redhat.com>
To: bert hubert <bert.hubert@netherlabs.nl>,
Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>,
linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk,
venkatesh.pallipadi@intel.com, tony@atomide.com, akpm@osdl.org,
cpufreq@lists.linux.org.uk, len.brown@intel.com
Subject: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
Date: Sun, 30 Jul 2006 15:01:33 -0400 [thread overview]
Message-ID: <20060730190133.GD18757@redhat.com> (raw)
In-Reply-To: <20060730184443.GA30067@outpost.ds9a.nl>
On Sun, Jul 30, 2006 at 08:44:43PM +0200, bert hubert wrote:
> > Do you have any info in /sys/devices/system/cpu/cpu0/cpufreq ?
>
> No, not with just acpi-cpufreq loaded. With the help of Zwane, I've
> discovered that if I unload acpi-cpufreq, I *can* load p4-clockmod, and then
> the directory you mention appears, and I can configure governors, and life
> is good. This all on 2.6.18-rc3.
Right, cpufreq drivers aren't 'stackable'.
> Do I understand correctly that acpi-cpufreq is supposed to offer comparable
> features?
If the BIOS supports the relevant ACPI tables.
> Perhaps acpi-cpufreq *has* loaded, but did not find the proper hooks, but
> has now registered itself, thus blocking p4-clockmod? When everything is
> in-kernel, acpi-cpufreq might register itself first, which would lead to the
> same thing.
Normally, if the necessary BIOS bits aren't there, then acpi-cpufreq will
fail to register. For some reason it sounds like it believes that everything
went ok. I wonder if something changed in acpi recently that caused this
change in behaviour ? Len ?
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-30 19:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 12:08 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4 bert hubert
2006-07-30 16:07 ` Tomasz Torcz
2006-07-30 16:51 ` 2.6.17 -> " bert hubert
2006-07-30 18:07 ` Alexey Starikovskiy
2006-07-30 18:44 ` bert hubert
2006-07-30 19:01 ` Dave Jones [this message]
2006-07-30 19:19 ` bert hubert
2006-07-31 7:08 ` bert hubert
2006-07-31 16:20 ` Dave Jones
2006-07-31 18:57 ` bert hubert
2006-07-31 20:38 ` Dave Jones
2006-07-30 17:45 ` Zwane Mwaikambo
2006-07-31 5:56 ` Tomasz Torcz
2006-07-31 14:04 ` Zwane Mwaikambo
2006-07-31 15:22 ` Tomasz Torcz
2006-07-30 19:46 ` Arjan van de Ven
2006-07-30 19:53 ` bert hubert
2006-07-31 7:50 ` David Rees
2006-07-31 8:12 ` bert hubert
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=20060730190133.GD18757@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=alexey_y_starikovskiy@linux.intel.com \
--cc=bert.hubert@netherlabs.nl \
--cc=cpufreq@lists.linux.org.uk \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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