[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1039029: marked as done (linux-signed-amd64: Core frequencies do not float correctly on AMD Ryzen 7 5700U when running on battery)

Your message dated Sat, 27 Jan 2024 15:37:55 -0700
with message-id <12367259.O9o76ZdvQC@soren-laptop>
and subject line linux-signed-amd64: Core frequencies do not float correctly on AMD Ryzen 7 5700U when running on battery
has caused the Debian Bug report #1039029,
regarding linux-signed-amd64: Core frequencies do not float correctly on AMD Ryzen 7 5700U when running on battery
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1039029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039029
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux-signed-amd64
Version: 6.3.7+1
Severity: normal

On my laptop running an AMD Ryzen 7 5700U CPU, when on battery there are problems with the core frequency logic.
When a process consumes 100% CPU usage on a single core, the system forces the core frequencey to the lowest value (399 MHz)
instead of letting it float up to the highest frequency (4.3 GHz).  At the same time, other cores that have minimal CPU utilization
will increate frequency up to the maximum, meaning that the CPU isn't locked to the lower frequency as a whole, but that something about
the frequency control logic isn't making the correct decisions.  This causes the system to run very slowly when on battery.

When the laptop is plugged in the behavior disappears, with cores that are consuming significant CPU able to increase the frequency to the
maximum value.

It is unclear to me if this problem is with the Linux kernel or some other component.  Someone who is more knowledgeable about these things
than I am might be able to point me in the right direction.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Control: fixed -1 6.5.13-1

This bug has been fixed with the 6.5.13-1 release.

-- 
Soren Stoutner
soren@stoutner.com

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: