NVMe high power state after wake up from sleep

[Snowy]

[ISSUE]

I have a dual boot acer helios laptop (windows is on the nvme, ubuntu on an SSD). Once I boot into Ubuntu (SSD) my nvme drive works as expected.

But once I set my laptop to sleep and wake it back up again the nvme drive power state is set to max rather than the default low power state. This causes a lot of heat to be generated and the smartctl tool reports the tempSenor#2 as 80-90C when in low power mode it runs at 40-60C.

I've observed this behaviour under Ubuntu 20.04.6 LTS and via live USB (22.04.3 LTS, 23.10)

BEFORE SLEEP:
sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H
get-feature:0x2 (Power Management), Current value:0x000004
        Workload Hint (WH): 0 - No Workload
        Power State   (PS): 4

AFTER SLEEP:
sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H
get-feature:0x2 (Power Management), Current value:00000000
        Workload Hint (WH): 0 - No Workload
        Power State (PS): 0

[Fix]

If i run the following command i can manually set the drive into a low power mode which dramatically effects both the onboard nvme temps and system temp (PCH chip)

sudo nvme set-feature /dev/nvme0n1p1 -f 2 -v 4

[INFO]

cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

============================

sudo nvme get-feature /dev/nvme0n1p1 -f 0x0c -H
get-feature:0xc (Autonomous Power State Transition), Current value:0x000001
        Autonomous Power State Transition Enable (APSTE): Enabled

============================

sudo smartctl /dev/nvme0n1p1 -a
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.15.0-92-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZVL2512HCJQ-00B07
Serial Number: <>
Firmware Version: GXA7302Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 6
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Utilization: 200,490,106,880 [200 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 b211b0a1d9
Local Time is: Thu Feb 1 22:18:19 2024 PST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 81 Celsius
Critical Comp. Temp. Threshold: 85 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
 0 + 8.37W - - 0 0 0 0 0 0
 1 + 8.37W - - 1 1 1 1 0 200
 2 + 8.37W - - 2 2 2 2 0 200
 3 - 0.0500W - - 3 3 3 3 2000 1200
 4 - 0.0050W - - 4 4 4 4 500 9500

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
 0 + 512 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 43 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 5,771,370 [2.95 TB]
Data Units Written: 6,509,044 [3.33 TB]
Host Read Commands: 96,282,996
Host Write Commands: 92,199,213
Controller Busy Time: 56
Power Cycles: 1,245
Power On Hours: 2,632
Unsafe Shutdowns: 145
Media and Data Integrity Errors: 3
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 43 Celsius
Temperature Sensor 2: 42 Celsius
Thermal Temp. 1 Transition Count: 3
Thermal Temp. 1 Total Time: 240

Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2052013/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Snowy (snowyoneill)]

Set affected package