> I've just upgraded to an X2 5000+ black edition. This model
> doesn't have a multiple lock and I tried bumping the multiplier
> up, which is perfectly stable, but which causes powernow-k8 to
> fail to load. I also tried with the updated patch you posted
> at the beginning of october
I've just upgraded to an X2 5000+ black edition. This model
doesn't have a multiple lock and I tried bumping the multiplier
up, which is perfectly stable, but which causes powernow-k8 to
fail to load. I also tried with the updated patch you posted
at the beginning of october
> > Has this been tested on older implementations of powernow yet?
> > I'm happy to merge this and give it some time in -mm, before it
> > goes to mainline, but if no-one is testing on those older
> > opterons/turions etc then we're not going to know we regressed
> > until its too late. If it
Has this been tested on older implementations of powernow yet?
I'm happy to merge this and give it some time in -mm, before it
goes to mainline, but if no-one is testing on those older
opterons/turions etc then we're not going to know we regressed
until its too late. If it hasn't been
> > Commit 991528d7348667924176f3e29addea0675298944
> > introduced mwait_idle which is supposed to work
> > for Intel CPUs starting with Core Duo.
> >
> > AMD Fam10 processors won't enter C1 on mwait.
>
> Unfortunate. Will this be fixed?
Fam10 processors were not designed to enter C1 on mwait.
Commit 991528d7348667924176f3e29addea0675298944
introduced mwait_idle which is supposed to work
for Intel CPUs starting with Core Duo.
AMD Fam10 processors won't enter C1 on mwait.
Unfortunate. Will this be fixed?
Fam10 processors were not designed to enter C1 on mwait.
That feature
> On 3/16/07, Langsdorf, Mark <[EMAIL PROTECTED]> wrote:
> > The processor is not changing frequency in response to your
> > launch of mplayer. The powersave governor forces it to the
> > lowest frequency regardless of system load. You really want
> > to u
On 3/16/07, Langsdorf, Mark [EMAIL PROTECTED] wrote:
The processor is not changing frequency in response to your
launch of mplayer. The powersave governor forces it to the
lowest frequency regardless of system load. You really want
to use ondemand for dynamic frequency scaling
> > If we really care about using the LAPIC timer on systems with deeper
> > than C1 support, the only alternative seems to be to test
> > if it actually works or not at boot and run-time.
> > Otherwise, we wait for future hardware with guaranteed
> > not to break under any (BIOS) conditions
If we really care about using the LAPIC timer on systems with deeper
than C1 support, the only alternative seems to be to test
if it actually works or not at boot and run-time.
Otherwise, we wait for future hardware with guaranteed
not to break under any (BIOS) conditions ships, and
> My kernel boots up with performance cpufreq governor, thus setting
> frequency to 2hgz. Then I change it to powersave governor, thus
> setting frequency to 1ghz just like that:
>
> echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> Everything works well. Then I launch
My kernel boots up with performance cpufreq governor, thus setting
frequency to 2hgz. Then I change it to powersave governor, thus
setting frequency to 1ghz just like that:
echo powersave /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Everything works well. Then I launch mplayer
> > I'm using a PC with AMD 64 3000+ cpu which is theoricaly running at
> > 2Ghz. But when looking at /proc/cpuinfo, the kernel reports that it
> > runs only at 1Ghz:
> > ...
> > What's going wrong ?
>
> Do you have feature called "Cool N' Quiet" enabled in BIOS?
> I had the same problem and
I'm using a PC with AMD 64 3000+ cpu which is theoricaly running at
2Ghz. But when looking at /proc/cpuinfo, the kernel reports that it
runs only at 1Ghz:
...
What's going wrong ?
Do you have feature called Cool N' Quiet enabled in BIOS?
I had the same problem and disabling the
> These machines are running a 2.6.9-42 RHEL4 kernel with the
> powernow-k8 module loaded - which I believe have backported
> cpufreq support from more recent mainline kernels.
To an extent. The problem is not the powernow-k8 driver,
but the cpufreq infrastructure. See below.
> In trying to
These machines are running a 2.6.9-42 RHEL4 kernel with the
powernow-k8 module loaded - which I believe have backported
cpufreq support from more recent mainline kernels.
To an extent. The problem is not the powernow-k8 driver,
but the cpufreq infrastructure. See below.
In trying to
16 matches
Mail list logo
