From: bert hubert <bert.hubert@netherlabs.nl>
To: Dave Jones <davej@redhat.com>,
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 21:19:32 +0200 [thread overview]
Message-ID: <20060730191932.GA31309@outpost.ds9a.nl> (raw)
In-Reply-To: <20060730190133.GD18757@redhat.com>
On Sun, Jul 30, 2006 at 03:01:33PM -0400, Dave Jones wrote:
> 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 ?
As far as I can see, acpi_cpufreq does not pass on any errors it sees during
init:
static int __init acpi_cpufreq_init (void)
{
int result = 0;
dprintk("acpi_cpufreq_init\n");
result = acpi_cpufreq_early_init_acpi();
...
And from acpi_cpufreq_early_init_acpi():
static int acpi_cpufreq_early_init_acpi(void)
{
struct acpi_processor_performance *data;
unsigned int i, j;
dprintk("acpi_cpufreq_early_init\n");
( some memory allocations, does not look at acpi or bios )
/* Do initialization in ACPI core */
acpi_processor_preregister_performance(acpi_perf_data);
return 0;
}
Note how any error from acpi_processor_preregister_performance is ignored.
Ghetto patch which "fixes" the problem for me:
--- ./arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c~orig 2006-07-30 21:14:43.000000000 +0200
+++ ./arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c 2006-07-30 21:11:34.000000000 +0200
@@ -384,8 +384,7 @@
}
/* Do initialization in ACPI core */
- acpi_processor_preregister_performance(acpi_perf_data);
- return 0;
+ return acpi_processor_preregister_performance(acpi_perf_data);
}
But tonight I have no speedstep laptop available to check if this does not
kill acpi_cpufreq when it can work.
Thanks for the hint, dave!
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
next prev parent reply other threads:[~2006-07-30 19:19 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
2006-07-30 19:19 ` bert hubert [this message]
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=20060730191932.GA31309@outpost.ds9a.nl \
--to=bert.hubert@netherlabs.nl \
--cc=akpm@osdl.org \
--cc=alexey_y_starikovskiy@linux.intel.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--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