Rongronggg9 / power-profiles-daemon

[FORK: USE AT YOUR OWN RISK] Makes power profiles handling available over D-Bus, with TLP driver (unsafe, dirty and experimental).
https://gitlab.freedesktop.org/upower/power-profiles-daemon
GNU General Public License v3.0
8 stars 0 forks source link

`powerprofilesctl list` shows performance state possibly incorrectly #3

Closed ademuri closed 10 months ago

ademuri commented 10 months ago

I am running Ubuntu 22.04.3. My power-profiles-daemon package is version 0.10.1-3. I have an Intel Core i3-8100, running at the stock frequency of 3.6 GHz.

I have the "Performance" power profile selected. The Gnome power settings says "Performance mode is temporarily disabled due to high operating temperature." And:

$ powerprofilesctl list
* performance:
    Driver:     intel_pstate
    Degraded:   yes (high-operating-temperature)

  balanced:
    Driver:     intel_pstate

  power-saver:
    Driver:     intel_pstate

But, I don't think that my CPU is actually too hot:

$ sensors
nct6797-isa-0a20
Adapter: ISA adapter
in0:                   744.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                     1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.31 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.30 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                   1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                   144.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                   960.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.31 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                  824.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                  672.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.51 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                   782 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan6:                  1096 RPM  (min =    0 RPM)
fan7:                  1067 RPM  (min =    0 RPM)
SYSTIN:                 +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
CPUTIN:                 +34.5°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN0:                +28.0°C    sensor = thermistor
AUXTIN1:                +23.0°C    sensor = thermistor
AUXTIN2:                +36.0°C    sensor = thermistor
AUXTIN3:                 -1.0°C    sensor = thermistor
PECI Agent 0:           +45.0°C  
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +119.0°C)

pch_cannonlake-virtual-0
Adapter: Virtual device
temp1:        +43.0°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +47.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +47.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:        +42.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:        +46.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:        +43.0°C  (high = +80.0°C, crit = +100.0°C)

Additionally, if I manually run the daemon, I don't see any log output which suggests why this is degraded:

$ sudo /usr/libexec/power-profiles-daemon -r -v
** (power-profiles-daemon:7161): DEBUG: 20:12:51.631: Starting power-profiles-daemon version 0.10.1
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: Handling driver 'fake'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: probe() failed for driver fake, skipping
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: Handling driver 'platform_profile'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: No platform_profile sysfs file
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: probe() failed for driver platform_profile, skipping
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: Handling driver 'intel_pstate'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: Opening policy dir '/sys/devices/system/cpu/cpufreq/'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.636: About to start monitoring '/sys/devices/system/cpu/intel_pstate/no_turbo'
(power-profiles-daemon:7161): GLib-GIO-DEBUG: 20:12:51.637: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
** (power-profiles-daemon:7161): DEBUG: 20:12:51.637: Found p-state settings
** (power-profiles-daemon:7161): DEBUG: 20:12:51.637: Handling driver 'placeholder'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.637: Driver 'intel_pstate' already probed, skipping driver 'placeholder'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.637: Handling action 'trickle_charge'
** (power-profiles-daemon:7161): DEBUG: 20:12:51.637: Applying profile 'performance' from configuration file
** (power-profiles-daemon:7161): DEBUG: 20:12:51.637: Setting active profile 'performance' for reason 'reset' (current: 'performance')

Is it correct in this case for the performance profile to be degraded? How can I find more information on why this is the case?

Rongronggg9 commented 10 months ago

This is a downstream fork. Any feedback should go to gitlab.freedesktop.org/upower/power-profiles-daemon.