From: Tomasz Torcz <zdzichu@irc.pl>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: bert hubert <bert.hubert@netherlabs.nl>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
Date: Mon, 31 Jul 2006 17:22:47 +0200 [thread overview]
Message-ID: <20060731152247.GA6768@irc.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0607310701190.10584@montezuma.fsmlabs.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Mon, Jul 31, 2006 at 07:04:07AM -0700, Zwane Mwaikambo wrote:
> On Mon, 31 Jul 2006, Tomasz Torcz wrote:
>
> > On Sun, Jul 30, 2006 at 10:45:13AM -0700, Zwane Mwaikambo wrote:
> >
> > > CONFIG_X86_ACPI_CPUFREQ
> >
> > I had this one =y. After setting =n, cpufreq-nforce2 (=m) works again.
> >
> > powernowd: PowerNow Daemon v0.96, (c) 2003-2005 John Clemens
> > powernowd: Found 1 cpu: -- 1 thread (or core) per physical cpu
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: No
> > such file or directory
> > powernowd: cpu0: 1228Mhz - 1753Mhz (7 steps)
>
> Hi Tomasz,
>
> Could you also please test Bert's patch which propogates error
> return values with your previous configuration?
Bert's patch works. With CONFIG_X86_ACPI_CPUFREQ=y and
cpufre-nforce2=m I have working cpufreq (like in 2.6.17 and before).
--
Tomasz Torcz "Never underestimate the bandwidth of a station
zdzichu@irc.-nie.spam-.pl wagon filled with backup tapes." -- Jim Gray
[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]
next prev parent reply other threads:[~2006-07-31 15:22 UTC|newest]
Thread overview: 22+ 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 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 [this message]
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
[not found] <fa.I17h4UhBWCsvus2I0Myp7dcrW/c@ifi.uio.no>
[not found] ` <fa.+Nle/k4hS56BZtGd2LF1VOaLvRg@ifi.uio.no>
2006-07-31 19:14 ` Robert Hancock
2006-07-31 19:35 ` 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=20060731152247.GA6768@irc.pl \
--to=zdzichu@irc.pl \
--cc=bert.hubert@netherlabs.nl \
--cc=linux-kernel@vger.kernel.org \
--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 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.