It gets disabled by commit ("cpufreq: amd-pstate: add amd-pstate driver
parameter for mode selection").

Use kernel parameter "amd_pstate=passive" to enable it once again.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2006942

Title:
  With linux kernel 5.19.0-31 amd_pstate is not used, while with
  5.19.0-29 and lower does

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 5.19.0-31 (two of my systems) CPU driver changes to
  acpi-cpufreq. instead of amd_pstate.

  This causes cpu to keep higher frequency and increased consumption.

  ```
  root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ls -l
  total 0
  -r--r--r-- 1 root root 4096 Feb 10 13:27 affected_cpus
  -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_highest_perf
  -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_lowest_nonlinear_freq
  -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_max_freq
  -r--r--r-- 1 root root 4096 Feb 10 12:54 cpuinfo_max_freq
  -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_min_freq
  -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_transition_latency
  -r--r--r-- 1 root root 4096 Feb 10 13:27 related_cpus
  -r--r--r-- 1 root root 4096 Feb 10 12:54 scaling_available_governors
  -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_cur_freq
  -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_driver
  -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_governor
  -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_max_freq
  -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_min_freq
  -rw-r--r-- 1 root root 4096 Feb 10 13:28 scaling_setspeed
  root@zeus:/sys/devices/system/cpu/cpufreq/policy0#
  ```
  with newer kernel also policy files for amd_pstate

  
  Tried it on 2 Asus PN51-S1 systems with AMD Ryzen 7 5700U

  I am currently staying at 5.19.0-29 as it is working better.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.19.0-31-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-11-18 (85 days ago)
  InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64 
(20221019)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-S1
  Package: linux-signed (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic 
root=/dev/mapper/system-root ro
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-31-generic N/A
   linux-backports-modules-5.19.0-31-generic  N/A
   linux-firmware                             20220923.gitf09bebf3-0ubuntu1.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.19.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/10/2022
  dmi.bios.release: 1.12
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0112
  dmi.board.asset.tag: Default string
  dmi.board.name: PN51-S1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0112:bd08/10/2022:br1.12:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-S1:pvr0112:rvnASUSTeKCOMPUTERINC.:rnPN51-S1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: MINIPC PN51-S1
  dmi.product.version: 0112
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006942/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to