@Shengyao Xue,
1.) Intel suspected that this Lenovo issue might be related to this issue: https://bugs.launchpad.net/somerville/+bug/1933807 on Intel vPro system. Lenovo did mention that vPro systems have the same issue.
2.) Intel SW debug engineer is adding some debug prints to the I219 runtime power managements callbacks to see if they are getting called, even though they shouldn’t. I will share patches once it is available.
3.) Can you please try below and see whether you can reproduce the issue? Please also pay attention if the system cannot enter Suspend to Idle after applying this.
@Shengyao Xue, /bugs.launchpad .net/somerville /+bug/1933807 on Intel vPro system. Lenovo did mention that vPro systems have the same issue.
1.) Intel suspected that this Lenovo issue might be related to this issue: https:/
2.) Intel SW debug engineer is adding some debug prints to the I219 runtime power managements callbacks to see if they are getting called, even though they shouldn’t. I will share patches once it is available.
3.) Can you please try below and see whether you can reproduce the issue? Please also pay attention if the system cannot enter Suspend to Idle after applying this.
echo on > /sys/bus/ pci/devices/ 0000\:00\ :16.0/power/ control /www.kernel. org/doc/ Documentation/ ABI/testing/ sysfs-devices- power:
Explanation, taken from https:/
What: /sys/devices/ .../power/ control
Date: January 2009
Contact: Rafael J. Wysocki <email address hidden>
Description:
The /sys/devices/ .../power/ control attribute allows the user
All devices have one of the following two values for the
+ "auto\n" to allow the device to be power managed at run time;
+ "on\n" to prevent the device from being power managed;
The default for all devices is "auto", which means that they may
be subject to automatic power management, depending on their
from power managing the device at run time. Doing that while
the device is suspended causes it to be woken up.