Date: Fri, 21 Feb 2020 08:31:11 -0500 From: David Schlachter <david@schlachter.ca> To: freebsd-current@freebsd.org Subject: Fwd: powerdxx: Assertion failed: (min < max && "minimum must be less than maximum") Message-ID: <CAF104kOu1xsAKWC0jpyt7pPDCY_BEntuNLPpv_apuhefLpo9Ow@mail.gmail.com> In-Reply-To: <CAF104kNq4UzGthhrHgMp4aOmfkdYjSR1osLdehq3ntxGz%2Bf-Lw@mail.gmail.com> References: <CAF104kNq4UzGthhrHgMp4aOmfkdYjSR1osLdehq3ntxGz%2Bf-Lw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
A heads up for any powerd++ users on CURRENT. For me at least it's been broken for a few weeks & a fix may not be forthcoming. Link to GitHub issue: https://github.com/lonkamikaze/powerdxx/issues/10 ---------- Forwarded message --------- De : Dominic Fandrey Date: ven. 21 f=C3=A9vr. 2020 04 h 30 Subject: Re: [lonkamikaze/powerdxx] CURRENT: Assertion failed: (min < max && "minimum must be less than maximum") (#10) This is in deed related to the hwpstate support. Powerd++ cannot do anything for you any more (manual frequency control via the sysctl interface is no longer possible). I think there are some loader hints to turn this feature off, but unless hwpstate is malfunctioning in some fashion this is probably not desired. All I can do is fail more gracefully or monitor the state in foreground mode. I'll take a bit of time to fiddle with the usability implications of this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF104kOu1xsAKWC0jpyt7pPDCY_BEntuNLPpv_apuhefLpo9Ow>