On Fri, 22 May 2015 20:26:40 +0300, Kimmo Paasiala wrote: > On Fri, May 22, 2015 at 8:19 PM, Ian Smith <smi...@nimnet.asn.au> wrote: > > On Fri, 22 May 2015 16:28:49 +0300, Kimmo Paasiala wrote: > > > On Fri, May 22, 2015 at 10:42 AM, Ivan Klymenko <fi...@ukr.net> wrote: [..] > >> 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 [..] > > 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.
Ok, if anabling acpi_throttle and/or p4tcc made cpufreq - and thus powerd - work for you, then it seems likely that you do not have EST enabled in your BIOS. Or at least, we've seen another instance where that was the case, which was fixed by enabling EST (or however your particular BIOS refers to it .. AMD for example use different terms). What CPU is this? In what machine? If EST (ono) IS enabled in your BIOS, this needs further investigation. As is, powerd may be running, but it's doing so highly inefficiently; refer to Stefan, Adrian and Kevin's responses for details. 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"
