https://bugzilla.kernel.org/show_bug.cgi?id=215742
--- Comment #30 from Daniel Drake (dr...@endlessm.com) --- Another test. Again with the kernel modified to allow a driverless child device to go properly into D3cold (must release the power management resource, because it is shared with the parent bridge, otherwise parent bridge will not go into D3cold in the experiment below): # Prevent bridge from going into D3cold echo on > "/sys/bus/pci/devices/0000:00:06.0/power/control" # Unbind NVMe and remove the device echo "0000:01:00.0" > /sys/bus/pci/drivers/nvme/unbind # Put NVMe device in D3cold and check echo auto > "/sys/bus/pci/devices/0000:01:00.0/power/control" cat "/sys/bus/pci/devices/0000:01:00.0/power_state" # D3cold # Remove NVMe device echo 1 > "/sys/bus/pci/devices/0000:01:00.0/remove" # Put bridge in D3cold echo auto > "/sys/bus/pci/devices/0000:00:06.0/power/control" # Check D3cold state with associated PXP power resource off cat "/sys/bus/pci/devices/0000:00:06.0/power_state" # D3cold cat /sys/bus/acpi/devices/LNXPOWER:00/path # confirm PEG0.PXP cat /sys/bus/acpi/devices/LNXPOWER:00/status # confirm 0 # Power on bridge again echo on > "/sys/bus/pci/devices/0000:00:06.0/power/control" # Force rescan echo 1 > "/sys/bus/pci/devices/0000:00:06.0/rescan" # Check for NVMe device reappearance ls "/sys/bus/pci/devices/0000:00:06.0/0000:01:00.0" # FAIL This leaves me more confident that the NVMe device is the one causing problems in this scenario. It should be in D3hot at this point (we did turn on its power resource at the same time as we power on the bridge, because it is the same power resource) yet it cannot be found by probing configuration space. Also, no error messages were produced during the above sequence (no more messages about retraining), and in the final state, the PCI bridge control space is accessible. -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
