From: "Sune Mølgaard" <sune@molgaard.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: speedstep-centrino: ENODEV
Date: Thu, 19 Oct 2006 22:30:53 +0200 [thread overview]
Message-ID: <4537E07D.5080402@molgaard.org> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454C1A534@scsmsx413.amr.corp.intel.com>
Pallipadi, Venkatesh wrote:
>
>
> OK. Things seem to be fine with the BIOS.
That sounds promising :-)
> You said it was working with 2.6.15. Do you remember whether kernel was using acpi-cpufreq or speedstep-centrino?
Sorry, I don't know, but I can build it and check.
> One change that has happened in this region is that If your BIOS supports both speedstep-centrino and acpi-cpufreq, with 2.6.15 any one of those drivers would have worked. But now with 2.6.18, acpi-cpufreq will not work in the above case and you have to use speedstep_centrino. This was done because, speedstep-centrino has more features than acpi-cpufreq and also doing this helped to elimiate issues with lot of systems with kernel trying to do multiple ACPI PDC writes when BIOS doesn't expect it to.
>
> In short:
> (1) If you were using acpi-cpufreq in 2.6.15, there is a high chance that it wont work with 2.6.18 and you should be able to use speedstep-centrino in its place. Make sure you have properly configured speedstep-centrino (You should select X86_SPEEDSTEP_CENTRINO_ACPI along with X86_SPEEDSTEP_CENTRINO).
>
> (2) If you were using speedstep-centrino in 2.6.15 and now it doesn't work with 2.6.18, then we have a new regression here and we need to root cause it further by enabling cpufreq.debug and getting more debug messages to see where it is failing....
>
Seems like 1 then. Will check the speedstep-centrino settings in the
kernel. Thanks. I'll report back, but probably not until tomorrow.
BR,
Sune
next prev parent reply other threads:[~2006-10-19 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 18:56 speedstep-centrino: ENODEV Pallipadi, Venkatesh
2006-10-19 20:30 ` Sune Mølgaard [this message]
2006-10-20 7:34 ` Sune Mølgaard
-- strict thread matches above, loose matches on Subject: below --
2006-10-20 12:25 Pallipadi, Venkatesh
2006-10-20 12:30 ` Sune Mølgaard
2006-10-20 11:56 Pallipadi, Venkatesh
2006-10-20 12:09 ` Sune Mølgaard
2006-10-19 18:21 Pallipadi, Venkatesh
2006-10-19 18:33 ` Sune Mølgaard
2006-10-19 19:34 ` Jiri Slaby
2006-10-19 15:57 Pallipadi, Venkatesh
2006-10-19 16:06 ` Jiri Slaby
2006-10-19 18:19 ` Sune Mølgaard
2006-10-19 14:00 Pallipadi, Venkatesh
2006-10-19 14:17 ` Sune Mølgaard
2006-10-19 14:27 ` Sune Mølgaard
2006-10-19 14:20 ` Jiri Slaby
2006-10-18 19:00 Jiri Slaby
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=4537E07D.5080402@molgaard.org \
--to=sune@molgaard.org \
--cc=jirislaby@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).