Recently, I have frequently noticed console error output where the line
acpicpu1: failed to set frequency to 2534 (err 22)
is repeated several times per second.
I am not certain when this started happening but I think it might be related to the changes that introduced the config line
acpicpu* at cpu?
I do not recall seeing it before I made that change.
My boot messages show several states for acpicpu0:
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: FFH, lat 1 us, pow 1000 mW
acpicpu0: C2: FFH, lat 1 us, pow 500 mW
acpicpu0: C3: FFH, lat 57 us, pow 100 mW, bus master check
acpicpu0: P0: FFH, lat 10 us, pow 35000 mW, 2534 MHz, turbo boost
acpicpu0: P1: FFH, lat 10 us, pow 35000 mW, 2533 MHz
acpicpu0: P2: FFH, lat 10 us, pow 15000 mW, 1600 MHz
acpicpu0: P3: FFH, lat 10 us, pow 12000 mW, 800 MHz
acpicpu0: T0: FFH, lat 1 us, pow 12000 mW, 100 %
acpicpu0: T1: FFH, lat 1 us, pow 10500 mW, 88 %
acpicpu0: T2: FFH, lat 1 us, pow 9000 mW, 75 %
acpicpu0: T3: FFH, lat 1 us, pow 7500 mW, 63 %
acpicpu0: T4: FFH, lat 1 us, pow 6000 mW, 50 %
acpicpu0: T5: FFH, lat 1 us, pow 4500 mW, 38 %
acpicpu0: T6: FFH, lat 1 us, pow 3000 mW, 25 %
acpicpu0: T7: FFH, lat 1 us, pow 1500 mW, 13 %
coretemp0 at cpu0: thermal sensor, 1 C resolution
but only a single line for acpicpu1:
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution
If this is the correct and expected behavior, it would be good if the error messages could be throttled somewhat.
If not, I'll be happy to help track it down.
This is on a Thinkpad T500 running NetBSD-current amd64.