Menno.Lageman wrote: > Li, Aubrey wrote: >> Menno Lageman wrote: >> >>> Hi, >>> >>> after resuming from S3 suspend powertop is (understandably) >>> confused. The top causes for wakeups are all 0 and stay 0 after >>> forcing >>> a refresh. >>> The P-states display still updates ok, as does the ACPI power usage >>> estimate. A freshly started copy works fine. Not a big issue, but it >>> might be nice to somehow reinitialize after resume? >>> >> Hi Menno, >> >> Thanks to report this issue. To be clarified, do you mean refresh >> key 'R' can't recover the top causes after S3 resume? or the second >> refresh key works? Or PowerTOP need to be restarted to fix this >> issue? >> > > Hi Aubrey, > > PowerTOP needs to be restarted to fix it. The 'R' key doesn't help. > The attached output is a truss of the confused powertop. >
Hi Menno, You know it's difficult to find a machine supporting S3. So can you please try "intrstat" as well to see if it works properly after S3 resume? Thanks, -Aubrey
