signature=fd45b8c9a90eebce5d855f07302ab4ee,195039 – Samsung PM951 NVMe sudden controller death-CSDN博客

Hans L

2020-02-13 03:17:50 UTC

I'm not sure if I have the exact same problem as OP, but I've been struggling with NVMe stability issues ever since I put together this Ryzen desktop computer around July 2019. My problems were originally on a "Crucial P1 500GB" NVMe drive, but I just swapped over to a new "Samsung 970 EVO 1TB" by cloning data, and I'm still seeing similar issues.

General Hardware Specs:

Motherboard: ASUS Prime B450 Plus motherboard running BIOS rev. "2008" (also had issues on rev. 1804)

CPU: AMD Ryzen 2700X

GPU: NVIDIA Corporation TU116 [GeForce GTX 1660]

Current drive: Samsung 970 EVO 1TB

Model: MZ-V7E1T0BW

Controller: SM981/PM981

Firmware: 2B2QEXE7

Previous drive (with basically same problems): Crucial P1 500GB

Model: CT500P1SSD8

Controller: SM2263EN

Firmware: P3CR013

The system can be stable for days or weeks on end, as long as I don't put it under particularly heavy sustained load (CPU mainly?). I have VERY repeatable results of AER errors showing up in dmesg just seconds after starting a specific workload: "mprime" executable (Linux version of "Prime95" from mersenne.org), specifically computing "P-1" aka "PM1" type of workunits.

I'd posted my issues on various forums but haven't been able to solve this. So I had basically gave up on running "mprime" on this computer and mostly forgot about the problems for a few months, until recently I needed to use another application which seems is triggering these same type of errors again (Intel "Quartus Prime Lite" EDA tools, for FPGA development)

I initially had tried disabling ASPM via kernel boot command line "pcie_aspm=off", as a recommended "solution" to my kernel logs being filled with spam from NVIDIA gpu. Errors involving: "[12] Timeout", "[ 6] BadTLP", and "[ 7] BadDLLP". Doing this got rid of those messages from GPU, but caused the NVMe to go into some unrecoverable state, at which point it would try to remount the drive as read only (also would show "BTRFS" errors when i'm only using EXT4?)

Here is a snippet of kernel log from when I had ASUS 1804 BIOS, and Crucial P1 500GB SSD, with "pcie_aspm=off", where it was unable to reset NVMe:

[ 989.409598] perf: interrupt took too long (4979 > 4912), lowering kernel.perf_event_max_sample_rate to 40000

[ 1195.031765] fuse: init (API version 7.31)

[ 1327.328770] perf: interrupt took too long (6268 > 6223), lowering kernel.perf_event_max_sample_rate to 31750

[ 2238.284260] perf: interrupt took too long (7846 > 7835), lowering kernel.perf_event_max_sample_rate to 25250

[ 9117.462381] perf: interrupt took too long (9831 > 9807), lowering kernel.perf_event_max_sample_rate to 20250

[ 9261.476036] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff

[ 9261.603999] pci_raw_set_power_state: 19 callbacks suppressed

[ 9261.604009] nvme 0000:01:00.0: Refused to change power state, currently in D3

[ 9261.604430] nvme nvme0: Removing after probe failure status: -19

[ 9261.632241] print_req_error: I/O error, dev nvme0n1, sector 15247304 flags 100001

[ 9261.632255] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0

[ 9261.729511] nvme nvme0: failed to set APST feature (-19)

[ 9261.739582] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0

[ 9261.739591] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0

[ 9261.739595] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0

[ 9261.756670] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 1, flush 0, corrupt 0, gen 0

[ 9261.756951] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 2, flush 0, corrupt 0, gen 0

[ 9261.758061] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 3, flush 0, corrupt 0, gen 0

[ 9261.758368] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 4, flush 0, corrupt 0, gen 0

[ 9261.759112] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 5, flush 0, corrupt 0, gen 0

[ 9261.759138] BTRFS error (device nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 4, rd 6, flush 0, corrupt 0, gen 0

[ 9262.276359] Core dump to |/bin/false pipe failed

[ 9262.336595] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]

[ 9262.336817] caller _nv000939rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs

[ 9262.975980] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 62

[ 9263.012987] Core dump to |/bin/false pipe failed

[ 9263.015801] Core dump to |/bin/false pipe failed

After re-enabling ASPM kernel boot parameter, and upgrading BIOS to latest "2008" revision I got messages like this (still on Crucial P1):

[ 3203.674000] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 3203.674052] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 3203.674076] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 3203.674081] pcieport 0000:00:03.1: AER: [12] Timeout

[ 3205.713683] pcieport 0000:00:01.1: AER: Uncorrected (Fatal) error received: 0000:01:00.0

[ 3205.713694] nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)

[ 3205.713709] nvme nvme0: frozen state error detected, reset controller

[ 3206.820214] pcieport 0000:00:01.1: AER: Root Port link has been reset

[ 3206.820265] nvme nvme0: restart after slot reset

[ 3206.963050] nvme nvme0: 15/0/0 default/read/poll queues

[ 3206.963296] pcieport 0000:00:01.1: AER: Device recovery successful

[ 3207.692447] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 3207.692464] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 3207.692470] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 3207.692472] pcieport 0000:00:03.1: AER: [12] Timeout

[ 3208.608352] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 3208.608370] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)

[ 3208.608378] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00000040/00006000

[ 3208.608381] pcieport 0000:00:03.1: AER: [ 6] BadTLP

[ 3210.904689] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 3210.904707] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 3210.904716] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 3210.904719] pcieport 0000:00:03.1: AER: [12] Timeout

[ 3211.260459] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 3211.260493] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)

[ 3211.260514] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00000040/00006000

[ 3211.260519] pcieport 0000:00:03.1: AER: [ 6] BadTLP

At some point I also tried "nvme_core.default_ps_max_latency_us=0" while on Crucial drive, which at best may have reduced the frequency of the problem occuring, but still eventually had crashing controller issues under loads.

I suspected the Crucial drive had some unresolved controller firmware bugs, so I thought upgrading to a different brand with a new Samsung 970 EVO would help.

I used clonezilla to copy the partition data over and grow to fit the new drive. Geting the clone to work without errors is a whole story in itself but I'll try to keep it short.

Having only one M.2 slot on my motherboard, I was using a NVMe to USB 3.1 Gen 2 (up to 10Gbps) adapter device by mfgr "SSK".

It failed to clone multiple times(some errors about "UAS" iirc) when plugged into my motherboard's USB 3.1 Gen 2 ports.

Then I try swapped the USB adapter to a different port, supporting only USB 3.1 Gen 1 (up to 5Gbps), and that suceeded with 0 errors on the first try.

So after booting up the new Samsung drive, I tried my high load mprime test and saw the same types of errors:

(The high load process wasn't actually started until around 350s. No idea if first 2 lines are relevant or a problem in any way, but I'm including those "errors" just in case.)

[ 194.587710] ucsi_ccg 0-0008: failed to reset PPM!

[ 194.587734] ucsi_ccg 0-0008: PPM init failed (-110)

...

[ 357.259829] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 357.259847] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 357.259855] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 357.259857] pcieport 0000:00:03.1: AER: [12] Timeout

[ 357.866075] pcieport 0000:00:01.1: AER: Uncorrected (Fatal) error received: 0000:01:00.0

[ 357.866098] nvme 0000:01:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessible, (Unregistered Agent ID)

[ 357.866124] nvme nvme0: frozen state error detected, reset controller

[ 358.262744] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 358.262765] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 358.262772] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 358.262775] pcieport 0000:00:03.1: AER: [12] Timeout

[ 358.439057] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 358.439076] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 358.439084] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 358.439086] pcieport 0000:00:03.1: AER: [12] Timeout

[ 358.506164] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 358.506182] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)

[ 358.506194] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00000040/00006000

[ 358.506196] pcieport 0000:00:03.1: AER: [ 6] BadTLP

[ 358.748596] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 358.748606] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 358.748611] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 358.748612] pcieport 0000:00:03.1: AER: [12] Timeout

[ 358.971108] pcieport 0000:00:01.1: AER: Root Port link has been reset

[ 358.971133] nvme nvme0: restart after slot reset

[ 359.231681] nvme nvme0: Shutdown timeout set to 8 seconds

[ 359.270538] nvme nvme0: 32/0/0 default/read/poll queues

[ 359.270843] pcieport 0000:00:01.1: AER: Device recovery successful

[ 359.355805] pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0

[ 359.355825] pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

[ 359.355835] pcieport 0000:00:03.1: AER: device [1022:1453] error status/mask=00001000/00006000

[ 359.355838] pcieport 0000:00:03.1: AER: [12] Timeout

...

More or less identical afaict (besides Samsung having a different queue depth).

So these fatal errors are able to be reset/recovered from, but this is still very concerning to me as I don't know if constantly resetting the NVMe controller multiple times per minute will lead to data corruption?

At this point I still have no idea what is going on and the problem might be any combination of:

1) Linux kernel bug

2) BIOS revision bug from ASUS/AMD (flaw in AMD 400 series PCIe bridge controller?)

3) Specific BIOS settings are not configured right by me?

4) Misbehaving device firmware (NVMe controller and/or GPU causing some kind of PCIe bus conflicts?)

5) Motherboard hardware defect, bad physical connection in some way? (based on other's reports that re-seating NVMe solved their issue)

6) Power or voltages reaching device are fluctuating out of spec? (power issues suspected since only occurs under heavy load). I don't have a scope to check this though.

Any advice would be greatly appreciated.

I don't know what combination of kernel boot settings(ASPM, AER, APST, nvme_core latency, etc.) and/or BIOS settings I should be trying anymore (or different BIOS revisions), as I don't understand how any of these interact and there's just too many combinations to try all of them exhaustively.

Not kernel boot params can override BIOS settings or if they need to be synced to compatible settings, but ASPM setting in BIOS gives me 3 options: "Disabled", "Auto", or "Force L0s"

I don't know off the top of my head if BIOS also had any APST, AER, or other related settings, but I can check if asked.

Below I've included a bunch more various general info and diagnostic commands I've run on my latest configuration with Samsung drive installed.

Let me know if there's any other command output or info I can provide to help:

$ lsb_release -d

Description: Linux Mint 19.3 Tricia

$ uname -r

5.3.0-28-generic

$ ls /sys/class/nvme/nvme0/power

async autosuspend_delay_ms control pm_qos_latency_tolerance_us runtime_active_kids runtime_active_time runtime_enabled runtime_status runtime_suspended_time runtime_usage

$ sudo nvme fw-log /dev/nvme0

Firmware Log for device:nvme0

afi : 0x1

frs1 : 0x3745584551324232 (2B2QEXE7)

$ systool -vm nvme_core

Module = "nvme_core"

Attributes:

coresize = "102400"

initsize = "0"

initstate = "live"

refcnt = "5"

srcversion = "B43C1A5A4BC80B50DFB88F2"

taint = ""

uevent =

version = "1.0"

Parameters:

admin_timeout = "60"

default_ps_max_latency_us= "100000"

force_apst = "N"

io_timeout = "30"

max_retries = "5"

multipath = "Y"

shutdown_timeout = "5"

streams = "N"

Sections:

$ sudo nvme id-ctrl /dev/nvme0

NVME Identify Controller:

vid : 0x144d

ssvid : 0x144d

sn : S5H9NC0MC24244K

mn : Samsung SSD 970 EVO 1TB

fr : 2B2QEXE7

rab : 2

ieee : 002538

cmic : 0

mdts : 9

cntlid : 4

ver : 10300

rtd3r : 30d40

rtd3e : 7a1200

oaes : 0

ctratt : 0

oacs : 0x17

acl : 7

aerl : 3

frmw : 0x16

lpa : 0x3

elpe : 63

npss : 4

avscc : 0x1

apsta : 0x1

wctemp : 358

cctemp : 358

mtfa : 0

hmpre : 0

hmmin : 0

tnvmcap : 1000204886016

unvmcap : 0

rpmbs : 0

edstt : 35

dsto : 0

fwug : 0

kas : 0

hctma : 0x1

mntmt : 356

mxtmt : 358

sanicap : 0

hmminds : 0

hmmaxd : 0

sqes : 0x66

cqes : 0x44

maxcmd : 0

nn : 1

oncs : 0x5f

fuses : 0

fna : 0x5

vwc : 0x1

awun : 1023

awupf : 0

nvscc : 1

acwu : 0

sgls : 0

subnqn :

ioccsz : 0

iorcsz : 0

icdoff : 0

ctrattr : 0

msdbd : 0

ps 0 : mp:6.20W operational enlat:0 exlat:0 rrt:0 rrl:0

rwt:0 rwl:0 idle_power:- active_power:-

ps 1 : mp:4.30W operational enlat:0 exlat:0 rrt:1 rrl:1

rwt:1 rwl:1 idle_power:- active_power:-

ps 2 : mp:2.10W operational enlat:0 exlat:0 rrt:2 rrl:2

rwt:2 rwl:2 idle_power:- active_power:-

ps 3 : mp:0.0400W non-operational enlat:210 exlat:1200 rrt:3 rrl:3

rwt:3 rwl:3 idle_power:- active_power:-

ps 4 : mp:0.0050W non-operational enlat:2000 exlat:8000 rrt:4 rrl:4

rwt:4 rwl:4 idle_power:- active_power:-

$ sudo lspci -vvv -s 00:01:00.0

01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 (prog-if 02 [NVM Express])

Subsystem: Samsung Electronics Co Ltd Device a801

Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-

Latency: 0, Cache Line Size: 64 bytes

Interrupt: pin A routed to IRQ 63

NUMA node: 0

Region 0: Memory at f6800000 (64-bit, non-prefetchable) [size=16K]

Capabilities: [40] Power Management version 3

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+

Address: 0000000000000000 Data: 0000

Capabilities: [70] Express (v2) Endpoint, MSI 00

DevCap:MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited

ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W

DevCtl:Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+

RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-

MaxPayload 256 bytes, MaxReadReq 512 bytes

DevSta:CorrErr- UncorrErr- FatalErr+ UnsuppReq- AuxPwr- TransPend-

LnkCap:Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L0s unlimited, L1 <64us

ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+

LnkCtl:ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+

ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

LnkSta:Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Not Supported

DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled

LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-

Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

Compliance De-emphasis: -6dB

LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+

EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-

Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-

Vector table: BAR=0 offset=00003000

PBA: BAR=0 offset=00002000

Capabilities: [100 v2] Advanced Error Reporting

UESta:DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

UEMsk:DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

UESvrt:DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

CESta:RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-

CEMsk:RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

AERCap:First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-

Capabilities: [148 v1] Device Serial Number 00-00-00-00-00-00-00-00

Capabilities: [158 v1] Power Budgeting >

Capabilities: [168 v1] #19

Capabilities: [188 v1] Latency Tolerance Reporting

Max snoop latency: 0ns

Max no snoop latency: 0ns

Capabilities: [190 v1] L1 PM Substates

L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+

PortCommonModeRestoreTime=10us PortTPowerOnTime=10us

L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-

T_CommonMode=0us LTR1.2_Threshold=0ns

L1SubCtl2: T_PwrOn=10us

Kernel driver in use: nvme

Kernel modules: nvme

$ lspci -tv

-[0000:00]-+-00.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex

+-00.2 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit

+-01.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge

+-01.1-[01]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983

+-01.3-[02-08]--+-00.0 Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller

| +-00.1 Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller

| \-00.2-[03-08]--+-00.0-[04]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

| +-01.0-[05]--

| +-04.0-[06]--

| +-06.0-[07]--

| \-07.0-[08]--

+-02.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge

+-03.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge

+-03.1-[09]--+-00.0 NVIDIA Corporation TU116 [GeForce GTX 1660]

| +-00.1 NVIDIA Corporation TU116 High Definition Audio Controller

| +-00.2 NVIDIA Corporation Device 1aec

| \-00.3 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER]

+-04.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge

+-07.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge

+-07.1-[0a]--+-00.0 Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function

| +-00.2 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor

| \-00.3 Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller

+-08.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge

+-08.1-[0b]--+-00.0 Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function

| +-00.2 Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode]

| \-00.3 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller

+-14.0 Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller

+-14.3 Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge

+-18.0 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0

+-18.1 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1

+-18.2 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2

+-18.3 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3

+-18.4 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4

+-18.5 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5

+-18.6 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6

\-18.7 Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7

$ sudo nvme get-feature -f 0x0c -H /dev/nvme0

get-feature:0xc (Autonomous Power State Transition), Current value:0x000001

Autonomous Power State Transition Enable (APSTE): Enabled

Auto PST Entries.................

Entry[ 0]

.................

Idle Time Prior to Transition (ITPT): 71 ms

Idle Transition Power State (ITPS): 3

.................

Entry[ 1]

.................

Idle Time Prior to Transition (ITPT): 71 ms

Idle Transition Power State (ITPS): 3

.................

Entry[ 2]

.................

Idle Time Prior to Transition (ITPT): 71 ms

Idle Transition Power State (ITPS): 3

.................

Entry[ 3]

.................

Idle Time Prior to Transition (ITPT): 500 ms

Idle Transition Power State (ITPS): 4

.................

Entry[ 4]

.................

Idle Time Prior to Transition (ITPT): 0 ms