CPU frequency doesn't drop below 1200MHz (like it used to)
Hi, I just noticed that my CPU's frequency doesn't support dropping below 1200MHz. It used to be able to go down to 150MHz, if I am not mistaken. I'd like it to go down to 600MHz via powerd, like it used to go. This is a month's old 10-STABLE. [nik@moby ~]$ sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 1400/18055 1300/16611 1200/15194 This is the CPU: > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz Thanks in advance for any ideas, Nikos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
Fri, 22 May 2015 09:33:15 +0200 Nikos Vassiliadis написав: > Hi, > > I just noticed that my CPU's frequency doesn't support dropping > below 1200MHz. It used to be able to go down to 150MHz, if I am > not mistaken. I'd like it to go down to 600MHz via powerd, like > it used to go. This is a month's old 10-STABLE. > > > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels > > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 > > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 > > 1400/18055 1300/16611 1200/15194 > > This is the CPU: > > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz > > Thanks in advance for any ideas, > Nikos Try changing the options in /boot/device.hints hint.acpi_throttle.0.disabled="0" hint.p4tcc.0.disabled="0" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD_STABLE_10-i386 - Build #90 - Failure
FreeBSD_STABLE_10-i386 - Build #90 - Failure: Check console output at https://jenkins.freebsd.org/job/FreeBSD_STABLE_10-i386/90/ to view the results. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
On 05/22/15 09:42, Ivan Klymenko wrote: Try changing the options in /boot/device.hints hint.acpi_throttle.0.disabled="0" hint.p4tcc.0.disabled="0" Thanks Ivan, now it works as it did before! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > Fri, 22 May 2015 09:33:15 +0200 > Nikos Vassiliadis написав: > >> Hi, >> >> I just noticed that my CPU's frequency doesn't support dropping >> below 1200MHz. It used to be able to go down to 150MHz, if I am >> not mistaken. I'd like it to go down to 600MHz via powerd, like >> it used to go. This is a month's old 10-STABLE. >> >> > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >> > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >> > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >> > 1400/18055 1300/16611 1200/15194 >> >> This is the CPU: >> > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >> >> Thanks in advance for any ideas, >> Nikos > > Try changing the options in /boot/device.hints > hint.acpi_throttle.0.disabled="0" > hint.p4tcc.0.disabled="0" Thanks, those also fixed powerd(8) for me that stopped working after upgrading to stable/10 from releng/10.1. Why are those setting suddenly needed now? -Kimmo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD_STABLE_10-i386 - Build #91 - Fixed
FreeBSD_STABLE_10-i386 - Build #91 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_STABLE_10-i386/91/ to view the results. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: > Fri, 22 May 2015 09:33:15 +0200 > Nikos Vassiliadis ÿÿ: > >> Hi, >> >> I just noticed that my CPU's frequency doesn't support dropping >> below 1200MHz. It used to be able to go down to 150MHz, if I am >> not mistaken. I'd like it to go down to 600MHz via powerd, like >> it used to go. This is a month's old 10-STABLE. >> >> > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >> > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >> > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >> > 1400/18055 1300/16611 1200/15194 >> >> This is the CPU: >> > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >> >> Thanks in advance for any ideas, >> Nikos > > Try changing the options in /boot/device.hints > hint.acpi_throttle.0.disabled="0" > hint.p4tcc.0.disabled="0" > Thanks, those also fixed powerd(8) for me that stopped working after > upgrading to stable/10 from releng/10.1. Why are those setting > suddenly needed now? > > -Kimmo Looks like the changes to these two hints, now defaulting to 1, committed to -head some months ago has been merged to stable/10. Can you say exactly in what way powerd stopped working then? Except that the minimum frequency that may be set with powerd's -m switch will be higher without p4tcc (or acpi_throttle) running, this change shouldn't hurt powerd; if anything it should be more efficient, as the lower p4tcc-generated frequencies don't save much if any power. If you compare dev.cpu.0.freq_levels, as above, both before and after booting with the changed hints, you can see the ones due to p4tcc's use of subfrequencies with factors of 1/8 to 7/8 of some base freq, but the power use in milliWatts provided for these seems largely ficticious. On my Lenovo X200, Core2Duo 2.4GHz, idling on battery at 800MHz (minimum EST freq) or at 100MHz using p4tcc draws almost exactly the same power, about 7.6W measured from the battery - but responsiveness as performance is required is a great deal better using just the base EST freqs; YMMV. This generally gets discussed on the freebsd-mobile and freebsd-acpi lists; not sure if a deeper discussion of issues is warranted here. cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
On Fri, May 22, 2015 at 8:19 PM, Ian Smith wrote: > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko wrote: >> Fri, 22 May 2015 09:33:15 +0200 >> Nikos Vassiliadis яя: >> >>> Hi, >>> >>> I just noticed that my CPU's frequency doesn't support dropping >>> below 1200MHz. It used to be able to go down to 150MHz, if I am >>> not mistaken. I'd like it to go down to 600MHz via powerd, like >>> it used to go. This is a month's old 10-STABLE. >>> >>> > [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >>> > dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >>> > 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >>> > 1400/18055 1300/16611 1200/15194 >>> >>> This is the CPU: >>> > hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz >>> >>> Thanks in advance for any ideas, >>> Nikos >> >> Try changing the options in /boot/device.hints >> hint.acpi_throttle.0.disabled="0" >> hint.p4tcc.0.disabled="0" > > > Thanks, those also fixed powerd(8) for me that stopped working after > > upgrading to stable/10 from releng/10.1. Why are those setting > > suddenly needed now? > > > > -Kimmo > > Looks like the changes to these two hints, now defaulting to 1, > committed to -head some months ago has been merged to stable/10. > > Can you say exactly in what way powerd stopped working then? Powerd(8) complained (excerpt from dmesg -a): Starting powerd. powerd: no cpufreq(4) support -- aborting: No such file or directory /etc/rc: WARNING: failed to start powerd Putting those two settings in loader.conf and rebooting fixed the problem and powerd started working again apparently because cpufreq(4) device was available again. -Kimmo > > Except that the minimum frequency that may be set with powerd's -m > switch will be higher without p4tcc (or acpi_throttle) running, this > change shouldn't hurt powerd; if anything it should be more efficient, > as the lower p4tcc-generated frequencies don't save much if any power. > > If you compare dev.cpu.0.freq_levels, as above, both before and after > booting with the changed hints, you can see the ones due to p4tcc's use > of subfrequencies with factors of 1/8 to 7/8 of some base freq, but the > power use in milliWatts provided for these seems largely ficticious. > > On my Lenovo X200, Core2Duo 2.4GHz, idling on battery at 800MHz (minimum > EST freq) or at 100MHz using p4tcc draws almost exactly the same power, > about 7.6W measured from the battery - but responsiveness as performance > is required is a great deal better using just the base EST freqs; YMMV. > > This generally gets discussed on the freebsd-mobile and freebsd-acpi > lists; not sure if a deeper discussion of issues is warranted here. > > cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
Am 22.05.2015 um 09:33 schrieb Nikos Vassiliadis: > Hi, > > I just noticed that my CPU's frequency doesn't support dropping > below 1200MHz. It used to be able to go down to 150MHz, if I am > not mistaken. I'd like it to go down to 600MHz via powerd, like > it used to go. This is a month's old 10-STABLE. > >> [nik@moby ~]$ sysctl dev.cpu.0.freq_levels >> dev.cpu.0.freq_levels: 2400/35000 2300/32872 2200/31127 2100/29417 >> 2000/27740 1900/26096 1800/24490 1700/22588 1600/21045 1500/19534 >> 1400/18055 1300/16611 1200/15194 > > This is the CPU: >> hw.model: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz Well, your CPU does not support clock frequencies below 1200 MHz. Throttling works by injection of "wait cycles" that reduce the amount of work the CPU can perform per unit of time, but does not really lower the CPU frequency. That means, that with throttling the CPU will need more energy to perform some calculation than it would without. If you select 150 MHz, then your CPU will be clocked at 1200 MHz, but will only perform any operations on each 8th clock cycle. This limits peak energy consumption (and that was the reason this feature was introduced in the power-hungry Pentium-4 processors), but increases the amount of energy needed to perform the computation. The power consumption of your CPU may be (an estimated) 50% to 70% at "150 Mhz" compared to 1200 Mhz. But you'll need 8 times as long until the CPU can fall into a deep sleep state. Since RAM and other components see the same clock whether throttling is enabled or not, you'll need 8 times as long full power for your RAM (which will also go into a low power refresh mode, when the CPU is idle). Throttling has been disabled, because there are no longer any CPUs which need it to prevent overheating. (Or rather: there are now better mechanisms than throttling, which are implemented in any modern x68 CPU.) Throttling could also impact system stability. It really serves no purpose anymore and it was never suitable to improve the power efficiency of e.g. a laptop computer. You'll see better battery live if you keep throttling disabled. Regards, STefan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
Hi, The whole point of throttling on modern hardware isn't to get really low clock rates, it's to deal with being out of thermal envelope. But, the modern intel cores will do that for you without OS involvement. So, you don't have to actually use p4tcc and it may actually configure your hardware wrong. Just throttle down to 1200MHz and go into deeper sleep states (>C1). I checked this on a variety of older and modern hardware; they all worked better just doing lowest ACPI P state and lowest ACPI C state. -adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: CPU frequency doesn't drop below 1200MHz (like it used to)
On Fri, May 22, 2015 at 11:47 AM, Adrian Chadd wrote: > Hi, > > The whole point of throttling on modern hardware isn't to get really > low clock rates, it's to deal with being out of thermal envelope. > > But, the modern intel cores will do that for you without OS involvement. > > So, you don't have to actually use p4tcc and it may actually configure > your hardware wrong. Just throttle down to 1200MHz and go into deeper > sleep states (>C1). I checked this on a variety of older and modern > hardware; they all worked better just doing lowest ACPI P state and > lowest ACPI C state. > > > > -adrian > > It's actually worse than this. TCC (which was first available on the Pentium 4) was always documented by Intel as a Thermal Control Circuit. Nothing about power management. FreeBSD suborned it for power management a long time go, but it never actually saved power. EST , which adjusts frequency and voltage does save a bit. Cx states save a lot. Using TCC for this was a very bad idea. (I did research on this back when I worked for Berkeley Lab.) There are a couple of very limited corner cases where throttling MAY save an utterly insignificant amount of power, but when C-states came about, Intel never considered the impact of C-states when the OS was playing around with throttling. (Windows never did that.) If you want to save power, set both economy_cx_lowest (battery) and performance_cx_lowest (AC) to Cmax in rc.conf. (This is the default in head.) Do not set a minimum frequency for powerd or it may fail to start if you specify a "frequncy" that is no longer available. That capability was to prevent system lockups when TCC and Cx collided. With TCC off, there is no need to worry about it. Please don't just turn TCC back on. It really just makes things worse. Read mav's excellent article on the issues on the FreeBSD wiki at https://wiki.freebsd.org/TuningPowerConsumption. His research and mine came to virtually identical conclusions. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
