Re: [acpi] Bug report: nvme :Cannot transition to power state D0 for parent in D3hot

Re: [acpi] Bug report: nvme :Cannot transition to power state D0 for parent in D3hot

[Rafael J. Wysocki]

On 10/15/2021 2:43 PM, Jun Miao wrote:
> Hi all
>
>
> bug log:
>
> *  acpi device:1b: Cannot transition to power state D0 for parent in 
> D3hot*

When does this happen?


>
> *
> *
>
>
> kernel version：
>
>         Linux intel-x86-64 5.15.0-rc4
>
> device info:
>
> root@intel-x86-64:~#lspci:
>
>   02:00.0 Non-Volatile memory controller: Intel Corporation SSD Pro 
> 7600p/760p/E 6100p Series (rev 03)
>
> root@intel-x86-64:~# lspci -vnn -s 02:00.0
> 02:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD 
> Pro 7600p/760p/E 6100p Series [8086:f1a6] (rev 03) (prog-if 02 [NVM 
> Express])
>     Subsystem: Intel Corporation Intel Corporation SSD Pro 
> 7600p/760p/E 6100p Series [NVM Express] [8086:390b]
>     Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0, 
> IOMMU group 11
>     Memory at df000000 (64-bit, non-prefetchable) [size=16K]
>     Capabilities: [40] Power Management version 3
>     Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
>     Capabilities: [70] Express Endpoint, MSI 00
>     Capabilities: [b0] MSI-X: Enable+ Count=16 Masked-
>     Capabilities: [100] Advanced Error Reporting
>     Capabilities: [158] Secondary PCI Express
>     Capabilities: [178] Latency Tolerance Reporting
>     Capabilities: [180] L1 PM Substates
>     Kernel driver in use: nvme
>
>
> kernel source :
>
> drivers/acpi/device_pm.c
>
> / 197         if (!device->power.flags.ignore_parent && //
> // 198             device->parent && (state < 
> device->parent->power.state)) { //
> // 199 dev_warn(&device->dev, //
> // 200                          "Cannot transition to power state %s 
> for parent in %s\n",//
> // 201 acpi_power_state_string(state), //
> // 202 acpi_power_state_string(device->parent->power.state)); //
> // 203                 return -ENODEV; //
> // 204         }
> /
>
> /
> /
>
> Whice one  is this device(device:1b) parent device ???//
>
>
You can check which device is pointed to by the physical_node link in 
/sys/bus/acpi/devices/.

Why do you think that NVMe is affected?