cpufreq/powerd workaround?

Ali Mashtizadeh mashtizadeh at gmail.com
Sat May 19 06:01:05 UTC 2007


Hey Everyone

On both my X2 and my Turion single core cpufreq has been a problem. It seems
it is acpi_throttle, part of cpufreq, that seems to be the real issue. So I
added this line to my /boot/loader.conf file and everything is fine now.
I've run 7-CURRENT and 6-STABLE.

hint.acpi_throttle.0.disabled="1"

(It looks like you have acpi_throttle enabled since you have so many
frequencies listed)

-- 
Ali Mashtizadeh
علی مشتی زاده

On 5/18/07, Thomas Hurst <tom.hurst at clara.net> wrote:
>
> * Uwe Laverenz (uwe at laverenz.de) wrote:
>
> > I just learned the hard way, that the use of cpufreq and powerd
> > freezes AMD64/SMP systems almost immediately. I found some old PRs
> > that describe this behaviour: amd64/87305, amd64/87689. The age of
> > these PRs make me think this issue is not going to be solved in the
> > near future. :)
> >
> > Is there a workaround for this or another way of saving energy?
> >
> > The system I use is a Tyan S2875 board with 2 Opteron 250.
>
> Aside from the occasional warning in dmesg from a failure in setting the
> frequency, cpufreq works for me on a Tyan S2895 with 2 Opteron 275's,
> and for the past year or so with 2 Opteron 246's:
>
> dev.cpu.0.freq: 1000
> dev.cpu.0.freq_levels: 2200/95000 2000/90300 1800/75900 1000/36100
> dev.powernow.0.%desc: Cool`n'Quiet K8
> dev.powernow.0.%driver: powernow
> dev.powernow.0.%parent: cpu0
>
> root      93137  0.0  0.0  3616  1128  ??  Ss   22Apr07  10:15.66/usr/sbin/powerd
>
> Are you running an up-to-date BIOS?  Any ACPI throttling stuff
> configured as well?
>
> --
> Thomas 'Freaky' Hurst
>     http://hur.st/
> _______________________________________________
> freebsd-amd64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
>


More information about the freebsd-amd64 mailing list