@Rick,
would you please try this test kernel and thermald 2.4.9.
https://drive.google.com/drive/folders/12jIHUbGFnYyPzZbo3qO8XeIalyBDSrtW?usp=sharing
I have applied the related kernel patches
@Rick, here's built mainline kernel image, you could find the deb files for
amd64 platform.
https://kernel.ubuntu.com/~kernel-ppa/mainline/
just download them and file this command.
#dpkg -i *.deb
please find the first bad or last good kernel version.
thanks
--
You received this bug
I'm not sure what's needed to bisect the kernel? What would I need to
do?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again
@Rick, would you mind to help bisect the kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Status in
There is no powerlimit via RAPL also here. Prochot can be generated by some
device on the system. We don't know the source.
If some old kernel works it is possible that newer kernel activated some new
device which is causing issue.
It is also possible that some device is now malfunctioning on
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Status in thermald package in Ubuntu:
In Progress
Bug
The speed is limited on every boot now...I also notice my bios time
being reset to 2013...when unplugged from the wall (I'm going to open it
up, the cmos battery may have died.)
rt@sys76:~$ sudo grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
[sudo] password for rt:
Also monitor
# cat /proc/interrupts | grep Thermal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Status in
@Srinivas,
could you please list the situations when the lock would be triggered?
here's first, #PROCHOT is flagged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU
As Doug correctly described, there is a active prochot situation on the system,
so processor frequency is limited.
Can you dump:
#grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
Also if you are able to boot the system without being stuck at 800MHz, can you
try
#echo 1 >
I would still likes to know what MSR 0x64F says, as per comment #20.
Yes, thermald should have been disabled for all of this stuff, and I
thought it was.
Recall one the askubuntu threads, where I suggested writing 0x4005C to
MSR 0x1FC. Do so at your own risk.
Your hardware seems to have issues,
@koba issue still occurs.
@Doug
rt@sys76:~$ sudo rdmsr -c -p0 0x1b2
0x3
rt@sys76:~$ sudo strace rdmsr 0x1b2
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1b2"], 0x7fff4f90a298 /* 17 vars */) = 0
brk(NULL) = 0x56510cc31000
arch_prctl(0x3001 /* ARCH_??? */,
@Rick, could you try to disable thermald.service on systemd and reboot then
enter active mode,
check the issue status. thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Your processor is indicating this:
PROCHOT# or FORCEPR# Event (bit 2, RO) — Indicates whether PROCHOT# or FORCEPR#
is being
asserted by another agent on the platform.
The related sticky log bit is also set.
This is something I suspected a couple of months ago, on one of those
askubuntu
ok
rt@sys76:~$ sudo rdmsr -c -p0 0x19c
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x1aa
0x40
rt@sys76:~$ sudo rdmsr -c -p0 0x1b1
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x16f
rdmsr: CPU 0 cannot read MSR 0x016f
rt@sys76:~$ sudo rdmsr -c -p0 0x1fc
0x4005d
rt@sys76:~$ sudo strace rdmsr
Sorry, 0x16f was wrong, it should have been 0x64F. I have no idea why
you are doing strace on this stuff. Since you haven't used my decoder,
it will be sometime before I manually decode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Since the intel_pstate driver is asking for 3.4 GHz, but the processor
itself is only granting 0.8 GHz we now know that the throttling is
within the processor and not externally driven.
It might be related to what koba noted in comment #8, I don't know.
The processor has MSRs with bits to
Ok
One terminal was running
rt@sys76:~$ taskset -c 2 yes > /dev/null
2nd terminal data:
rt@sys76:~$ grep . /sys/devices/system/cpu/intel_pstate/*
/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:50
When the frequency seems stuck at 800 MHz, then please put a load on a
CPU and look at the pstate request and granted MSR's.
Example, where I force CPU 2:
$ taskset -c 2 yes > /dev/null
and then look at the request and granted pstates:
$ sudo rdmsr --bitfield 15:8 -u -a 0x199
8
8
48
8
30
8
8
8
Try changing to the powersave governor. If something else set another
pstate request and the intel_pstate driver doesn't know about it, then
with the performance governor it might never send a new pstate request.
All of this is very similar to a few months ago, on askubuntu and the path of
Now after another reboot the speed is stuck at 800mhz again and doesn't
move
rt@sys76:~$ uname -r
5.15.5-76051505-generic
rt@sys76:~$ grep CONFIG_CPU_FREQ_DEFAULT /boot/config-5.15.5-76051505-generic
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is
If the intel_pstate scaling driver is "active" then "powersave" is the
default governor. If the driver "passive" or the is the acpi-cpufreq
driver during boot, then the default governor will be "ondemand". Note
that "active-powersave" is crudely the equivalent of "passive-ondemand".
You can
Yes I can get it to boot into active mode thanks to Doug, but after
several minutes the cpu drops to 798-800mhz and won't increase no matter
if I try and change it. I did notice that the scaling_governor always
boots to powersave mode. When I change it to performance after several
minutes the
He is using the intel_pstate CPU frequency scaling driver. Now by
default processors without HWP will boot into the intel_pstate driver in
passive mode (A.K.A. intel_cpufreq).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in
@Rick, did you try this one?
sudo cpufreq-set -f `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU
Here's a list I can't remember the last time it worked, if you do a
google search on "ubuntu cpu lowest freq" seems to be a very common
problem but none of the fixes work for me.
I can't change the speed of my CPU's in my bios (a system76 linux machine).
What do you want me to check in the
found one interesting thing in the log
CONFIG_TDP_CONTROL is locked, could you check the bios first?
e.g. c-state control
cpu4: MSR_CONFIG_TDP_NOMINAL: 0x0018 (base_ratio=24)
cpu4: MSR_CONFIG_TDP_LEVEL_1: 0x ()
cpu4: MSR_CONFIG_TDP_LEVEL_2: 0x ()
cpu4: MSR_CONFIG_TDP_CONTROL:
@Rick, could you list the using kernel version?
Do you remember which kernel version you didn't observe the issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU
ok...
rt@sys76:~$ sudo cpupower -c all frequency-info
[sudo] password for rt:
analyzing CPU 0:
driver: intel_cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 20.0 us
hardware limits:
@Rick,
please dump frequency info before doing any changed
#sudo cpupower -c all frequency-info
if governor is powersave, please change to performance then run some loadings,
and observe the cpu current frequency
#cpupower frequency-set --governor performance
--
You received this bug
rt@sys76:~$ sudo systemctl status thermald.service
● thermald.service - Thermal Daemon Service
Loaded: loaded (/lib/systemd/system/thermald.service; enabled; v>
Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) => koba (kobako)
** Changed in: thermald (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
@Rick, could you please run some loadings and log the turbstat?
thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again
I'm not sure if this is the right package
** Package changed: ubuntu => thermald (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at
34 matches
Mail list logo
