This bug was fixed in the package linux-oem-6.11 - 6.11.0-1023.23
---------------
linux-oem-6.11 (6.11.0-1023.23) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1023.23 -proposed tracker (LP:
#2111230)
* ACPICA: Add support for printing AML arguments when trace point enabled
(LP: #2111220)
- ACPICA: Add support for printing AML arguments when trace point enabled
* When the speaker volume is adjusted above 80%, noise occurs from the
speakers with cs42l43. (LP: #2110950)
- ASoC: intel/sdw_utils: Add volume limit to cs42l43 speakers
* Support Sony IMX471 camera sensor for Intel IPU7 platforms (LP: #2107320)
- SAUCE: media: ipu-bridge: Support imx471 sensor
- [Packaging] debian.oem/dkms-versions -- bump ipu6-drivers version
* Mediatek MT7920 WLAN card does not respect Wireless Radio Control in BIOS
(LP: #2109314)
- wifi: mt76: mt7921: add rfkill_poll for hardware rfkill
* The system with VMD enabled may encounter hang (LP: #2110178)
- SAUCE: PCI: vmd: Fix use-after-free bug in resource name assignment
* Fix divide by zero errors in DML2 (LP: #2106923)
- drm/amd/display: Protect FPU in dml2_init()/dml21_init()
- drm/amd/display: Protect FPU in dml2_validate()/dml21_validate()
- drm/amd/display: Protect FPU in dml21_copy()
* Not all monitors connected on the dock display correctly when the system
resumes from restart or suspend on AMD platform (LP: #2110095)
- drm/amd/display: use drm_warn instead of DRM_WARN
- drm/amd/display: Shift DMUB AUX reply command if necessary
- drm/amd/display: Fix the checking condition in dmub aux handling
- drm/amd/display: Remove incorrect checking in dmub aux handler
- drm/amd/display: Copy AUX read reply data whenever length > 0
- drm/amd/display: Fix wrong handling for AUX_DEFER case
* Support AMD Image Signal Processing (ISP) unit V4.0 (LP: #2110092)
- Revert "UBUNTU: [Config] Enable AMD_ISP4"
- Revert "UBUNTU: SAUCE: ispkernel 3.0 release"
- drm/amdgpu: Add MFD support for ISP I2C bus
- drm/amd/amdgpu: Add support for isp buffers
- SAUCE: ispkernel: 4.0 release
- SAUCE: fix amd-isp4 build failures
- [Config] Enable AMD_ISP4
* System will restart while resuming with SATA HDD or nvme installed with
password set (LP: #2110090)
- PCI: Explicitly put devices into D0 when initializing
* Privacy LED may not be turned on on OEM Renegade platform with Intel IPU7
camera (LP: #2106807)
- [Packaging] debian.oem/dkms-versions -- bump vision-drivers version
* Fix volume control no effect on HP EliteStudio AIO (LP: #2109539)
- ALSA: hda: Apply volume control on speaker+lineout for HP EliteStudio AIO
* Fix Mic Mute LED no function on HP G12 laptops with ACP7.0 platform
(LP: #2108954)
- ASoC: amd: acp: Remove redundant acp70 chip->name
- ASoC: amd: acp: Implement acp_common_hw_ops support for acp platforms
- ASoC: amd: acp: Refactor dmic-codec platform device creation
-- Chia-Lin Kao (AceLan) <acelan....@canonical.com> Mon, 19 May 2025
14:27:43 +0800
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/2110090
Title:
System will restart while resuming with SATA HDD or nvme installed
with password set
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
Invalid
Bug description:
[Impact]
The BIOS PCI device configuration and restoration during modern standby will
check the ACPI function _REG value. It expects this value to be 0x2
(PCI_Config), and this value is returned by the operating system.
Windows returns 0x2 (PCI_Config), which allows the PCI device
configuration and restoration function to complete successfully.
However, Ubuntu returns 0x3 (EmbeddedControl), which prevents the SATA
HDD password unlock function from working during Modern Standby
resume.
[Fix]
The commit which will be included in v6.16 explicitly set all devices into D0
during initialization, so that _REG method works as expected.
https://lore.kernel.org/all/20250424043232.1848107-1-supe...@kernel.org/
4d4c10f763d78 PCI: Explicitly put devices into D0 when initializing
[Test]
1. Install ubuntu 2404 on any machine(the issue has been found on Dell Pro
Micro Mini PC with AMD Ryzen Processors), and enabled SATA HDD password.
1.1 connect SATA HDD on system
1.2 press F2 enter BIOS menu
1.3 choose the menu “Passwords“ in the left side
1.4 setup passowrd in “Internal HDD Passward“
1.5 save setting and boot into OS
2. After resume from suspend with w/ SATA HDD installed and hdd password set.
3. The machine should keep working and the SATA HDD could be accessed
[Where problems could occur]
It's trivial to set the device to D0 state while iniailizing, I don't see it
could lead to any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2110090/+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
