On 2023-03-01 13:53, Abhishek Sahu wrote: > On 3/1/2023 4:04 PM, Tasos Sahanidis wrote: >> On 2023-02-28 20:46, Alex Williamson wrote: >>> Can you do the same for the root port to the GPU, ex. use lspci -t to >>> find the parent root port. Since the device doesn't seem to be >>> achieving D3cold (expected on a desktop system), the other significant >>> change of the identified commit is that the root port will also enter a >>> low power state. Prior to that commit the device would enter D3hot, but >>> we never touched the root port. Perhaps confirm the root port now >>> enters D3hot and compare lspci for the root port when using >>> disable_idle_d3 to that found when trying to use the device without >>> disable_idle_d3. Thanks, >>> >>> Alex >>> >> >> I seem to have trouble understanding the lspci tree. >> > > Can you please try following way to confirm the path > > ls -l /sys/bus/pci/devices > > It generally displays the full path like > > 0000:03:00.0 -> ../../../devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0 Thanks! I had the wrong device (as Alex pointed out), but this helped verify that it is in fact 0000:03:02.0. $ ls -l /sys/bus/pci/devices/ | grep 06: 0000:06:00.0 -> ../../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:02.0/0000:06:00.0 0000:06:00.1 -> ../../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:02.0/0000:06:00.1 > Also, Can you please print the runtime PM control entry as well > > /sys/bus/pci/devices/<root_port B:D:F>/power/control I now printed it in my reply to your other message, and I also did so while collecting information in response to Alex's email. Hope it helps. > Thanks, > Abhishek -- Tasos
