On Tue, 27 Sep 2022 07:59:53 +0100 Stuart Henderson <[email protected]> wrote:
>On 2022/09/26 17:40, Sebastian Oswald wrote:
>> The high interrupt load also seems to cause the CPU to never reduce
>> clock speed (hw.cpuspeed always showing 2001), hence constantly using
>> maximum power and getting relatively hot (>60°C) after a while.
>
>Currently OpenBSD won't automatically change clock speed unless running
>on battery. To workaround you can either manually set to another speed
>(in your case 2000 would at least disable 'turbo' which will probably
>help with the temperature), or run "obsdfreqd" (not in 7.1 ports but
>the -current port will build ok on 7.1), or use this diff - of course
>results will be better if you can get the acpi problem fixed too.
>
>Index: sched_bsd.c
>===================================================================
>RCS file: /cvs/src/sys/kern/sched_bsd.c,v
>retrieving revision 1.72
>diff -u -p -r1.72 sched_bsd.c
>--- sched_bsd.c 14 Aug 2022 01:58:27 -0000 1.72
>+++ sched_bsd.c 27 Sep 2022 06:56:12 -0000
>@@ -543,7 +543,7 @@ setperf_auto(void *v)
> if (cpu_setperf == NULL)
> return;
>
>- if (hw_power) {
>+ if (0 && hw_power) {
> speedup = 1;
> goto faster;
> }
Thanks. I wasn't aware that OpenBSD doesn't change the clock speed.
I will try that patch and obsdfreqd after the interrupt storm has been
dealt with.
pgp4zwQTDuiP4.pgp
Description: OpenPGP digital signature
