Public bug reported:
[ Impact ]
The PCI ID for ARL-U/H is not correct in arl_h_d3_fixup() in
intel_pmc_core. This leads to some platforms not being able to enter
PC10 and subsequently not able to enter S0ix
[ Fix ]
Backport the following commit from linux-next:
f2eae58c4428bd792c8 (platform/x86/intel/pmc: Fix Arrow Lake U/H NPU
PCI ID)
[ Test case ]
Install the kernel inspect the
$ cat
/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
Suspend the system:
$ sudo rtcwake -m freeze -s 60
Inspect the low_power_idle_cpu_residency_us sysfs file again. The number
should increase.
[ Where the problems could occur ]
If the ID is still wrong, the suspend problem will remain. Or it might
attempt to fix up the wrong device.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-oem-6.11 (Ubuntu)
Importance: Undecided
Assignee: Leo Lin (0xff07)
Status: New
** Affects: linux-oem-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Tags: jira-somerville-2114 oem-priority
** Changed in: linux-oem-6.11 (Ubuntu)
Assignee: (unassigned) => Leo Lin (0xff07)
** Also affects: linux-oem-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Tags added: jira-delta-220 oem-priority
** Tags removed: jira-delta-220
** Tags added: jira-somerville-2114
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2111871
Title:
[SRU] Correct NPU PCI ID of ARL-H/U in intel_pmc_core
Status in HWE Next:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux-oem-6.11 source package in Noble:
New
Bug description:
[ Impact ]
The PCI ID for ARL-U/H is not correct in arl_h_d3_fixup() in
intel_pmc_core. This leads to some platforms not being able to enter
PC10 and subsequently not able to enter S0ix
[ Fix ]
Backport the following commit from linux-next:
f2eae58c4428bd792c8 (platform/x86/intel/pmc: Fix Arrow Lake U/H
NPU PCI ID)
[ Test case ]
Install the kernel inspect the
$ cat
/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
Suspend the system:
$ sudo rtcwake -m freeze -s 60
Inspect the low_power_idle_cpu_residency_us sysfs file again. The
number should increase.
[ Where the problems could occur ]
If the ID is still wrong, the suspend problem will remain. Or it might
attempt to fix up the wrong device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2111871/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
