Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)

[koba]

[Impact]
On ADL platform, I+N sku,
get the cpufreq errors during boot-up,
[ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
[ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19)
[ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19)

[Fix]
Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration)
The commit has been landed on mainline since v5.15-rc1.

[Test Case]
1. boot-up the machine.
2. check dmesg if the cpufreq error is presented.

[Where problems could occur]
low

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1954617

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-oem-5.14/5.14.0-1011.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Yuan-Chen Cheng (ycheng-twn)]

Tested on a machine that previous have that issue. After install 5.14 1011 oem kernel from focal proposed, then this is fixed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11

---------------
linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker
    (LP: #1954691)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.11.08)

  * s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
    (LP: #1954633)
    - platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops

  * Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540)
    - ACPI: Add stubs for wakeup handler functions
    - pinctrl: amd: Fix wakeups when IRQ is shared with SCI

  * alsa/hda: the microphone can't be detected on a couple of lenovo machines
    (LP: #1954612)
    - ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform

  * mt7921e: Failed to start WM firmware (LP: #1954300)
    - SAUCE: Bluetooth: btusb: Handle download_firmware failure cases
    - SAUCE: Bluetooth: btusb: Return error code when getting patch status failed

  * Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
    (LP: #1954617)
    - ACPI: CPPC: Introduce cppc_get_nominal_perf()
    - ACPI: CPPC: Add NULL pointer check to cppc_get_perf()
    - cpufreq: intel_pstate: hybrid: Rework HWP calibration

  * Add support for NVIDIA EC backlight (LP: #1953286)
    - platform/x86: Add driver for ACPI WMAA EC-based backlight control
    - platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c
    - platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight
    - [Config] NVIDIA_WMI_EC_BACKLIGHT=m

  * Let VMD follow host bridge PCIe settings (LP: #1954611)
    - SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features

 -- Timo Aaltonen <email address hidden> Mon, 13 Dec 2021 19:41:56 +0200