[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated
https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?id=95dc0f6212b9eb8769fb40b2359a0a61cfac8494 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049793 Title: [MTL] x86: Fix Cache info sysfs is not populated Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] The interface /sys/devices/system/cpu/cpuX/cache is broken (not populated) if CPUs have different numbers of subleaves in CPUID 4. This is the case of Intel Meteor Lake. [Fix] https://lore.kernel.org/all/2023121519.12834-1-ricardo.neri-calde...@linux.intel.com/ Reviewed, but probably will only land in v6.9. [Test Case] Check existence of cpu cache info: $ ls /sys/devices/system/cpu/cpu0/cache/ index0 index1 index2 index3 uevent [Where problems could occur] This populates sysfs entries that should have been available, not something new or alters existing interface. [Other Info] While this is targets v6.8 for Intel LPMD (Low Power Model Daemon)'s use, only Noble and Unstable will be nominated for fix. == original bug report == [Description] The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Meteor Lake Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: TBD External Links: https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] [Testing guidance] [External ID] LFE-6901 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049793/+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
[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049793 Title: [MTL] x86: Fix Cache info sysfs is not populated Status in intel: New Status in linux package in Ubuntu: New Bug description: [Description] The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Meteor Lake Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: TBD External Links: https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] [Testing guidance] [External ID] LFE-6901 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049793/+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
[Kernel-packages] [Bug 2008522] Re: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle
** Description changed: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. - - Target Kernel: 6.3 - Target Release: 23.10 - [HW/SW Information] Meteor Lake + + [Software Information] + Target Version: + 23.10 + Target Kernel: + 6.3 + Commit IDs: + acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 + External Links: [Business Justification] Platform enabling - Upstream: Merged 6.3 - Commit ID: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 + [External ID] + LFE-7117 ** Tags added: 23.10 external-id -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008522 Title: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. [HW/SW Information] Meteor Lake [Software Information] Target Version: 23.10 Target Kernel: 6.3 Commit IDs: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 External Links: [Business Justification] Platform enabling [External ID] LFE-7117 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008522/+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
[Kernel-packages] [Bug 2008522] Re: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle
@p-pisati - I don't know where the last half of the commit: c4e927da893b--> 68b99e94a4a2 came from. But I looked in our internal JIRA and it shows this: c4e927da893b thermal: intel_powerclamp: Remove accounting for IRQ wakes This is the correct one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008522 Title: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. Target Kernel: 6.3 Target Release: 23.10 [HW/SW Information] Meteor Lake [Business Justification] Platform enabling Upstream: Merged 6.3 Commit ID: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008522/+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
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
Please try this patch https://lore.kernel.org/linux-
pci/20231221011250.191599-1-david.e@linux.intel.com/ from David E
Box.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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
[Kernel-packages] [Bug 2028322] Re: Enable Palo Alto Global Protect (PAGP) with SAML authentication working on the Ubuntu desktop supported via 20.04 LTS.
*** This bug is a duplicate of bug 2026771 *** https://bugs.launchpad.net/bugs/2026771 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028322 Title: Enable Palo Alto Global Protect (PAGP) with SAML authentication working on the Ubuntu desktop supported via 20.04 LTS. Status in intel: New Status in linux package in Ubuntu: New Bug description: 1. Feature Overview: Enable Palo Alto Global Protect (PAGP) with SAML authentication working on the Ubuntu desktop supported via 20.04 LTS. We propose 2 options: Option 1: Provide a backport of the OpenConnect and NetworkManager- OpenConnect packages from the Ubuntu Daily Build to Ubuntu 20.04 that will allow PAGP SAML authentication to work (it works in the current daily build for 23.10). OpenConnect version: v9.12-1 NetworkManager-OpenConnect version: 1.2.10-1 Option 2 (Preferred Option): Provide a backport of the 'gp-saml-gui' package which will allow PAGP SAML authentication to work (the current daily build for 23.10 will need to be updated first). gp-saml-gui minimum required version: 0.0~git20230417-1 gp-saml-gui current version (Ubuntu 23.10 daily build): 0.0~git20220831-1 2. Hardware: All 3. Upstream acceptance information: N/A 4. External links: N/A RDC Document #: N/A 5. Ubuntu Target: Ubuntu 20.04 LTS (Focal) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2028322/+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
[Kernel-packages] [Bug 2028320] Re: Enable Palo Alto Global Protect (PAGP) with SAML authentication working via NetworkManager on the Ubuntu desktop supported via 22.04 LTS.
*** This bug is a duplicate of bug 2026771 *** https://bugs.launchpad.net/bugs/2026771 ** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028320 Title: Enable Palo Alto Global Protect (PAGP) with SAML authentication working via NetworkManager on the Ubuntu desktop supported via 22.04 LTS. Status in intel: New Status in linux package in Ubuntu: New Bug description: 1. Feature Overview: Enable Palo Alto Global Protect (PAGP) with SAML authentication working via NetworkManager on the Ubuntu desktop supported via 22.04 LTS. Provide a backport of the OpenConnect and NetworkManager-OpenConnect packages from the Ubuntu Daily Build to Ubuntu 22.04 that will allow PAGP SAML authentication to work (it works in the current daily build for 23.10). OpenConnect version: v9.12-1 NetworkManager-OpenConnect version: 1.2.10-1 2. Hardware: All 3. Upstream acceptance information: N/A 4. External links: N/A RDC Document #: N/A 5. Ubuntu Target: Ubuntu 22.04 LTS (Jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2028320/+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
