Bug 205847

Summary: Dell G7 7588 - changing power states in bus power management doesn't have any effect
Product: Power Management Reporter: Moitaeel (moises.soares.eel)
Component: Run-Time-PMAssignee: Rafael J. Wysocki (rjw)
Status: CLOSED CODE_FIX    
Severity: normal CC: rui.zhang
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.4.2 Subsystem:
Regression: No Bisected commit-id:
Attachments: acpidump
dmesg
lspci -nn

Description Moitaeel 2019-12-12 20:26:03 UTC 
After updating from kernel 5.4rc7.d1117.g1d4c79e-1 to kernel 5.4.2, when changing power states on /sys/bus/pci/devices/0000\:01\:00..0/power/control, no power consumption change is noted, the consumption on powertop is always 20W. 

Expected results would be of switching to auto on the GPU and bus controller, on "/sys/bus/pci/devices/0000\:01\:00..0/power/control" and "/sys/bus/pci/devices/0000\:00\:01.0/power/control" would turn consumption to about 11W on powertop on idle and when turned on both would consume about 20W on idle.

Removing the card also does not produce change in power or temperature.

No nvidia modules were loaded during these tests.

This problem was first noticed on kernel 5.3.11 but I had solved the problem by upgrading to kernel 5.4rc7.d1117.g1d4c79e-1. I documented power and temperature change on kernel 5.3.11 here https://imgur.com/a/A8J4nM3.


I have a Dell G7 7588, with a Core i7-8750H and a GTX 1060 MaxQ.

Please instruct on debug process.
Comment 1 Moitaeel 2019-12-17 15:41:39 UTC 
Hello again, another update, it seems like this issue is not present at kernel 5.5rc1 and 5.5rc2, nor at kernel 4.19.88, however it is still present in kernel 5.3.16-1 and 5.4.3-1.
Comment 2 Moitaeel 2019-12-17 16:03:13 UTC 
Created attachment 286337 [details]
acpidump

acpidump while on the kernel 5.4.3-1.
Comment 3 Moitaeel 2019-12-17 16:03:58 UTC 
Created attachment 286339 [details]
dmesg

dmesg while on kernel 5.4.3-1
Comment 4 Moitaeel 2019-12-17 16:05:58 UTC 
Created attachment 286341 [details]
lspci -nn

lspci -nn while on kernel 5.4.3-1
Comment 5 Zhang Rui 2019-12-29 04:24:40 UTC 
So the problem is fixed in the latest upstream kernel, right?
then I think this bug can be closed.
please feel free to re-open it if you still have any questions.