Re: powerd forgets top CPU frequency ?
- In reply to: Poul-Henning Kamp: "Re: powerd forgets top CPU frequency ?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 25 Aug 2024 09:31:09 UTC
On Sun, 25 Aug 2024 08:40:19 +0000 "Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote: > -------- > Ronald Klop writes: > > > This is interesting by itself. According to the sysctl the CPU only has 1 frequency to select, which is 2803, but it is running on 3103. Maybe there is some > > Yes, I've always had a bit of trouble understanding how these things fit together... > > (Also not the best laptop I've had in a number of other ways) You likely have hwpstate, so powerd will do nothing. Try changing dev.hwpstate_intel.<CPU>.epp value and see if you manage to do what you want, otherwise you will need to disable hwpstate (it's doable with some hints iirc) and use powerd. Cheers, > > other mechanism which influences the CPU freq on your machine. I hope somebody else can shine some light on this. > > Doesn't the output (or source) of powerd give some insight on why it makes the decisions it makes? > > Only stuff like: > > load 144%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 127%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 120%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 136%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 132%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > > But it is not entirely obvious to me that powerd actually does anything... > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>