public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
To: bert hubert <bert.hubert@netherlabs.nl>,
	linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk,
	davej@redhat.com, venkatesh.pallipadi@intel.com,
	tony@atomide.com, akpm@osdl.org, cpufreq@lists.linux.org.uk
Subject: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on	pentium4
Date: Sun, 30 Jul 2006 22:07:18 +0400	[thread overview]
Message-ID: <44CCF556.2060505@linux.intel.com> (raw)
In-Reply-To: <20060730165137.GA26511@outpost.ds9a.nl>

Do I understand your logs right and acpi-cpufreq is already loaded and works on your processor?
Do you have any info in /sys/devices/system/cpu/cpu0/cpufreq ?
Why do you want to load p4-clockmod over it? It does not save you any power, just limits performance.

Regards,
	Alex.

bert hubert wrote:
>>   I have similar problem with cpufreq-nforce2 -- http://lkml.org/lkml/2006/7/7/234
>>   I haven't do a git-bisect yet.
> 
> To recap, cpufreq died for at least two people (Tomasz Torcz and me) between
> 2.6.17 and 2.6.18-rc1. I've cc'd everybody who touched cpufreq according to
> the shortlog.
> 
> Abundant details are in:
> 
> http://lkml.org/lkml/2006/7/30/87
> 
> New information is that I've narrowed it down from between 2.6.16.9 and
> 2.6.18-rc1 to between 2.6.17.7 (which works) and 2.6.18-rc1 (which doesn't).
> 
> The problem exists both with cpufreq as modules and staticly, and both with
> P4 and nforce2.
> 
> Please let me know how I can help you solve this problem. I'll try a git
> bisect but a lot of the cpufreq changes appear to be interrelated, so I'm
> unsure if it will work.
> 
> Thanks!
> 

  reply	other threads:[~2006-07-30 18:07 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 [this message]
2006-07-30 18:44       ` bert hubert
2006-07-30 19:01         ` Dave Jones
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=44CCF556.2060505@linux.intel.com \
    --to=alexey_y_starikovskiy@linux.intel.com \
    --cc=akpm@osdl.org \
    --cc=bert.hubert@netherlabs.nl \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.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