[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
This bug is awaiting verification that the linux- nvidia-6.2/6.2.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-jammy-linux-nvidia-6.2' to 'verification-done-jammy-linux-nvidia-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-failed-jammy-linux-nvidia-6.2'. 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! ** Tags added: kernel-spammed-jammy-linux-nvidia-6.2-v2 verification-needed-jammy-linux-nvidia-6.2 -- 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/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix 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 Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug is awaiting verification that the linux- aws-6.2/6.2.0-1014.14~22.04.1 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-jammy-linux- aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'. 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! ** Tags added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix 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 Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug is awaiting verification that the linux-azure/6.2.0-1015.15 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-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. 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! ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix 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 Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug was fixed in the package linux - 6.2.0-34.34 --- linux (6.2.0-34.34) lunar; urgency=medium * lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779) * CVE-2023-20569 - x86/cpu, kvm: Add support for CPUID_8021_EAX - tools headers x86 cpufeatures: Sync with the kernel sources - x86/alternative: Optimize returns patching - x86/retbleed: Add __x86_return_thunk alignment checks - x86/srso: Add a Speculative RAS Overflow mitigation - x86/srso: Add IBPB_BRTYPE support - x86/srso: Add SRSO_NO support - x86/srso: Add IBPB - x86/srso: Add IBPB on VMEXIT - x86/srso: Fix return thunks in generated code - x86/srso: Add a forgotten NOENDBR annotation - x86/srso: Tie SBPB bit setting to microcode patch detection - Documentation/hw-vuln: Unify filename specification in index - Documentation/srso: Document IBPB aspect and fix formatting - x86/srso: Fix build breakage with the LLVM linker - x86: Move gds_ucode_mitigated() declaration to header - x86/retpoline: Don't clobber RFLAGS during srso_safe_ret() - x86/srso: Disable the mitigation on unaffected configurations - x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG - x86/retpoline,kprobes: Skip optprobe check for indirect jumps with retpolines and IBT - x86/cpu: Fix __x86_return_thunk symbol type - x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk() - objtool/x86: Fix SRSO mess - x86/alternative: Make custom return thunk unconditional - x86/cpu: Clean up SRSO return thunk mess - x86/cpu: Rename original retbleed methods - x86/cpu: Rename srso_(.*)_alias to srso_alias_\1 - x86/cpu: Cleanup the untrain mess - x86/srso: Explain the untraining sequences a bit more - objtool/x86: Fixup frame-pointer vs rethunk - x86/static_call: Fix __static_call_fixup() - x86/srso: Correct the mitigation status when SMT is disabled - Ubuntu: [Config]: enable Speculative Return Stack Overflow mitigation * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console - [Config] Mark sh-sci as built-in * dGPU cannot resume because system firmware stuck in IPCS method (LP: #2021572) - drm/i915/tc: Abort DP AUX transfer on a disconnected TC port - drm/i915/tc: switch to intel_de_* register accessors in display code - drm/i915: Enable a PIPEDMC whenever its corresponding pipe is enabled - drm/i915/tc: Fix TC port link ref init for DP MST during HW readout - drm/i915/tc: Fix system resume MST mode restore for DP-alt sinks - drm/i915/tc: Wait for IOM/FW PHY initialization of legacy TC ports - drm/i915/tc: Factor out helpers converting HPD mask to TC mode - drm/i915/tc: Fix target TC mode for a disconnected legacy port - drm/i915/tc: Fix TC mode for a legacy port if the PHY is not ready - drm/i915/tc: Fix initial TC mode on disabled legacy ports - drm/i915/tc: Make the TC mode readout consistent in all PHY states - drm/i915: Add encoder hook to get the PLL type used by TC ports - drm/i915/tc: Assume a TC port is legacy if VBT says the port has HDMI - drm/i915/tc: Factor out a function querying active links on a TC port - drm/i915/tc: Check the PLL type used by an enabled TC port - drm/i915/tc: Group the TC PHY setup/query functions per platform - drm/i915/tc: Use the adlp prefix for ADLP TC PHY functions - drm/i915/tc: Rename tc_phy_status_complete() to tc_phy_is_ready() - drm/i915/tc: Use the tc_phy prefix for all TC PHY functions - drm/i915/tc: Move TC port fields to a new intel_tc_port struct - drm/i915/tc: Check for TC PHY explicitly in intel_tc_port_fia_max_lane_count() - drm/i915/tc: Move the intel_tc_port struct declaration to intel_tc.c - drm/i915/tc: Add TC PHY hook to get the PHY HPD live status - drm/i915/tc: Add TC PHY hooks to get the PHY ready/owned state - drm/i915/tc: Add TC PHY hook to read out the PHY HW state - drm/i915/tc: Add generic TC PHY connect/disconnect handlers - drm/i915/tc: Factor out tc_phy_verify_legacy_or_dp_alt_mode() - drm/i915/tc: Add TC PHY hooks to connect/disconnect the PHY - drm/i915/tc: Fix up the legacy VBT flag only in disconnected mode - drm/i915/tc: Check TC mode instead of the VBT legacy flag - drm/i915/tc: Block/unblock TC-cold in the PHY connect/disconnect hooks - drm/i915/tc: Remove redundant wakeref=0 check from unblock_tc_cold() - drm/i915/tc: Drop tc_cold_block()/unblock()'s power domain parameter - drm/i915/tc: Add TC PHY hook to get the TC-cold blocking power domain - drm/i915/tc: Add asserts in TC PHY hooks that the required power is on - drm/i915/tc: Add TC PHY hook to init the PHY - drm/i915/adlp/tc: Use the DE HPD ISR register for hotplug detection - drm/i915/tc: Get power ref for reading the HPD live status register
[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
** Tags added: originate-from-2036858 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix 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 Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Tags added: originate-from-2034495 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix 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 Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1022.22 --- linux-oem-6.1 (6.1.0-1022.22) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1022.22 -proposed tracker (LP: #2034205) * amdgpu: Fixes for S0i3 resume on Phoenix (LP: #2033654) - drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11 - drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix - drm/amd: flush any delayed gfxoff on suspend entry * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4569 - netfilter: nf_tables: deactivate catchall elements in next generation * stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) (LP: #2016398) - SAUCE: overlayfs: fix reference count mismatch * Fix blank display when Thunderbolt monitor is plugged second time (LP: #2034491) - thunderbolt: Fix Thunderbolt 3 display flickering issue on 2nd hot plug onwards - thunderbolt: Fix a backport error for display flickering issue * Enable D3cold at s2idle for Intel DG2 GPU (LP: #2033452) - drm/i915/dgfx: Enable d3cold at s2idle * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Fix ACPI TAD on some Intel based systems (LP: #2032767) - ACPI: TAD: Install SystemCMOS address space handler for ACPI000E * Fix panel brightness issues on HP laptops (LP: #2032704) - ACPI: video: Put ACPI video and its child devices into D0 on boot * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration -- Timo Aaltonen Wed, 06 Sep 2023 10:02:26 +0300 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-20588 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4569 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix 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 Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug was fixed in the package linux - 6.5.0-5.5 --- linux (6.5.0-5.5) mantic; urgency=medium * mantic/linux: 6.5.0-5.5 -proposed tracker (LP: #2034546) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/d2023.08.23) -- Andrea Righi Wed, 06 Sep 2023 15:51:04 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
please verify oem-6.1 1022 ** Tags added: verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Tags added: originate-from-202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Tags removed: verification-needed-jammy-linux-oem-6.5 verification-needed-lunar-linux verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-oem-6.5 verification-done-lunar-linux verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug is awaiting verification that the linux/6.2.0-34.34 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-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. 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! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1003.3 --- linux-oem-6.5 (6.5.0-1003.3) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1003.3 -proposed tracker (LP: #2033279) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf * Resync CI Runner Configuration (LP: #2024199) - [CI] resync ci configuration - [CI] resync ci configuration * i915: Backport some fixes for Meteor Lake, vol2 (LP: #2032781) - drm/i915/gsc: fixes and updates for GSC memory allocation - drm/i915/mtl/gsc: extract release and security versions from the gsc binary - drm/i915/mtl/gsc: query the GSC FW for its compatibility version - drm/i915/mtl/gsc: Add a gsc_info debugfs - drm/i915/gsc: Fix intel_gsc_uc_fw_proxy_init_done with directed wakerefs - drm/i915/display: Do not use stolen on MTL - drm/i915/huc: check HuC and GuC version compatibility on MTL - drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests - drm/i915/color: Upscale degamma values for MTL - drm/i915/color: Downscale degamma lut values read from hardware - drm/i915/gt: Simplify shmem_create_from_object map_type selection - SAUCE: drm/i915: Make i915_coherent_map_type GT-centric - drm/i915/gt: Apply workaround 22016122933 correctly * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932) - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE" [ Ubuntu: 6.5.0-2.2 ] * mantic/linux: 6.5.0-2.2 -proposed tracker (LP: #2033240) * Soundwire support for Dell SKU0C87 devices (LP: #2029281) - SAUCE: ASoC: Intel: soc-acpi: add support for Dell SKU0C87 devices * Fix numerous AER related issues (LP: #2033025) - SAUCE: PCI/AER: Disable AER service during suspend, again - SAUCE: PCI/DPC: Disable DPC service during suspend, again * Support Realtek RTL8852CE WiFi 6E/BT Combo (LP: #2025672) - wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() - Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C * Rebase to v6.5 [ Ubuntu: 6.5.0-1.1 ] * mantic/linux: 6.5.0-1.1 -proposed tracker (LP: #2032750) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - [Packaging] update variants - debian/dkms-versions -- update from kernel-versions (main/d2023.07.26) * ceph: support idmapped mounts (LP: #2032959) - SAUCE: libceph: add spinlock around osd->o_requests - SAUCE: libceph: define struct ceph_sparse_extent and add some helpers - SAUCE: libceph: new sparse_read op, support sparse reads on msgr2 crc codepath - SAUCE: libceph: support sparse reads on msgr2 secure codepath - SAUCE: libceph: add sparse read support to msgr1 - SAUCE: libceph: add sparse read support to OSD client - SAUCE: ceph: add new mount option to enable sparse reads - SAUCE: ceph: preallocate inode for ops that may create one - SAUCE: ceph: make ceph_msdc_build_path use ref-walk - SAUCE: libceph: add new iov_iter-based ceph_msg_data_type and ceph_osd_data_type - SAUCE: ceph: use osd_req_op_extent_osd_iter for netfs reads - SAUCE: ceph: fscrypt_auth handling for ceph - SAUCE: ceph: implement -o test_dummy_encryption mount option - SAUCE: ceph: add fscrypt ioctls and ceph.fscrypt.auth vxattr - SAUCE: ceph: make ioctl cmds more readable in debug log - SAUCE: ceph: add base64 endcoding routines for encrypted names - SAUCE: ceph: encode encrypted name in ceph_mdsc_build_path and dentry release - SAUCE: ceph: send alternate_name in MClientRequest - SAUCE: ceph: decode alternate_name in lease info - SAUCE: ceph: set DCACHE_NOKEY_NAME flag in ceph_lookup/atomic_open() - SAUCE: ceph: make d_revalidate call fscrypt revalidator for encrypted dentries - SAUCE: ceph: add helpers for converting names for userland presentation - SAUCE: ceph: make ceph_fill_trace and ceph_get_name decrypt names - SAUCE: ceph: pass the request to parse_reply_info_readdir() - SAUCE: ceph: add support to readdir for encrypted names - SAUCE: ceph: create symlinks with encrypted and base64-encoded targets - SAUCE: ceph: add some fscrypt guardrails - SAUCE: ceph: allow encrypting a directory while not having Ax caps - SAUCE: ceph: mark directory as non-complete after loading key - SAUCE: ceph: size handling in MClientRequest, cap updates and inode traces - SAUCE: ceph: handle fscrypt fields in cap messages from MDS - SAUCE: ceph: add infrastructure for file encryption and decryption - SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support - SAUCE: libceph: allow ceph_osdc_new_request to accept a multi-op read - SAUCE: ceph: add object version support for sync read - SAUCE: ceph: add truncate size handling support for fscrypt - SAUCE: ceph: don't use special DIO path for encrypted
[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues
** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed-jammy-linux-oem-6.5 verification- needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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 2033025] Re: Fix numerous AER related issues
** Changed in: linux (Ubuntu Lunar) Importance: High => Medium ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033025 Title: Fix numerous AER related issues Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Numerous issues triggered from AER/DPC services - When AER is shared with PME, cutting the power off the device can trigger AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, preventing the system from entering sleep. - When system resume from S3, device can reset itself and start sending PTM messages, triggering AER and reset the entire hierarchy. Since the hardware/firmware starts before software, it's never soon enough to put a band-aid from kernel. - Following above one, device firmware restarts before kernel resume, when DPC is triggered then the device is gone without any recovering method. We really want to prevent that from happening. [Fix] Disable and re-enable AER and DPC services on suspend and resume, respectively. Right now the the PCI mailing list doesn't have a consensus which PCI state (D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate the old workaround for now. [Test] One the workaround is applied, symptoms described above can no longer be observed. [Where problems could occur] Theoretically there can be some "real" issues get unnoticed once AER gets temporarily disabled, but the benefit far outweighs the downside. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033025/+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