-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01/06/15 13:41, Jung-uk Kim wrote: > On 01/05/2015 22:57, Kevin Oberman wrote: >> On Mon, Jan 5, 2015 at 4:56 PM, Sean Bruno >> <sbr...@ignoranthack.me> wrote: >> >>> >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >>> >>> acpi_throttle0: <ACPI CPU Throttling> on cpu0 acpi_throttle0: >>> P_CNT from P_BLK 0x1810 est0: <Enhanced SpeedStep Frequency >>> Control> on cpu0 acpi_throttle1: <ACPI CPU Throttling> on cpu1 >>> acpi_throttle1: failed to attach P_CNT device_attach: >>> acpi_throttle1 attach returned 6 est1: <Enhanced SpeedStep >>> Frequency Control> on cpu1 acpi_throttle2: <ACPI CPU >>> Throttling> on cpu2 acpi_throttle2: failed to attach P_CNT >>> device_attach: acpi_throttle2 attach returned 6 est2: <Enhanced >>> SpeedStep Frequency Control> on cpu2 acpi_throttle3: <ACPI CPU >>> Throttling> on cpu3 acpi_throttle3: failed to attach P_CNT >>> device_attach: acpi_throttle3 attach returned 6 est3: <Enhanced >>> SpeedStep Frequency Control> on cpu3 >>> >>> >>> The call to acpi_bus_alloc_gas() in acpi_throttle.c seems to be >>> failing to attach. What should I be poking at here? >>> >> >> Excellent! Throttling is counter-productive and always has been. >> It's been at least 5 years since mav@ posted his excellent wiki >> article on power management which demonstrated the futility of >> throttling. More important, even if it was useful for power >> management, it has long since been superseded by TCC. Intel >> tried to make the purpose of TCC clear by the name: Thermal >> Control Circuit. So it is ineffective for power management and >> FreeBSD still tries to use it. Looks like the vendor broke ACPI >> so throttling won't work. Or, maybe, Intel simply removed it as >> unused legacy. >> >> Don't worry. Be happy! Make sure that >> hint.acpi_throttle.0.disabled=1 is set in /boot/loader.conf to >> disable it. I'd strongly urge that you also disable P4TCC with >> hint.p4tcc.0.disabled=1. It will trivially improve battery life >> and will seriously compromise performance if powerd is enabled. >> It can also cause hangs with elevated C-states on some systems. > > FYI, acpi_throttle and tcc have been disabled by default for a > while. > > https://svnweb.freebsd.org/changeset/base/265329 > > I guess Nathan forgot to MFC this commit? > > Jung-uk Kim > >
Well, I'm running -current. I don't know, for my case, that an MFC is correct. Is it a bug that this stuff is appearing at all? sean FreeBSD bruno 11.0-CURRENT FreeBSD 11.0-CURRENT #11 r276355M: Mon Jan 5 17:52:37 PST 2015 sbruno@bruno:/usr/obj/usr/src/sys/BRUNO amd64 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJUrFzzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kZtgIANLbUDUly1KJgls/GHNGXuHE WdruuhibrIfHZuoaFSKtodL4SHtqKljfzTxk61ZazOqDixkhaMpyiDa6u23RxyGN 92PeBFmxBkVgdrPwaShOtGiPaREomfMbyB989/avBIBvbUHzKYyZ+PFxbf4In5M7 03ZcLoe7S9Y1Y6MMJkYJS4le80dIBM8XbGuz4qpC6Hq7ncBZPlxDDEtHqKbX0lCF 9izMAl+Ax42LbbqL7GsxXvNeE668AU2gbBOCsgX59MgdNieqm2q9mzq9t0+/DW9s vR7vQkJALhfrJAObm1i4of85lI+iEBt3rt9xWDALSjlixBL9eXDf6OF6ZrmjMQM= =oaxO -----END PGP SIGNATURE----- _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
