Gerard ROBIN writes:
Hello, the maximum frequency of my cpu is 2.8 GHz and under "bullseye" the frequency of my cpu is always higher than 2.7 GHz. If this is a bug how can we determine which package is affected ?
Normally, modern CPUs go to high frequency only if they are "loaded". Thus, I'd suggest to check if there is any process obviously taking a lot of CPU time. `top` might be enough for a glance, but I normally like `htop` and `atop` outputs more (`htop` is more "friendly", but `atop` is more informative IMHO). The other thing is: As long as it is always below or equal to 2.8 GHz, it need not be wrong. However, most machines with U-processors (especially notebooks) have a cooling system which does not permit them to sustain the maximum frequency for long. You might investigate this by generating load on all cores e.g. like this: dd if=/dev/urandom bs=4M count=1024 | pv | xz -T 0 -9 > /dev/null
With "buster" on the same machine the problem does not occur. The cpu frequency is between 900 MHz and 1.8 GHz
That sounds very low? What happens if you generate some load. Does it stay this way or go (temporarily?) up to the 2.3 or 2.8 GHz? Test (vary the `count` to check for longer times, add `-T` parameters to `xz` to check a specific number of cores): dd if=/dev/urandom bs=4M count=10 | xz -9 > /dev/null In case it would be missing on your system, `xz` is part of package `xz-utils`. It is not a "proper" benchmark tool btw. In case it is not obvious: None of these tests outputs anything useful, the idea is to check the frequencies while the tests are running and see how they differ from before/afterwards as to find out if the frequency behaves as expected. I'd generally expect the following results (in the absence of bugs :) ) * Loading a single core (`xz -9` without `-T 0`) brings it to maximum frequency (2.8 GHz). * Loading multiple cores (`xz -9 -T 0`) brings them to the max frequency for a short time and then has them drop to the base frequency or even below. * Not having any load on the machine should go in the low requency range, the 800 MHz to 1.8 GHz range sounds plausible for this. Another interesting check: Which of the two behaviours seen (low freq range vs. high freq range) is exposed if you run a backported Kernel on the Buster system such as to have the comparison for similar kernel versions?
cpu: intel i5-6200U Base frequency: 2.3 GHz Max Frequency: 2.8 GHz
HTH Linux-Fan [...]
_________________________________ ********************************* * Created with "mutt 1.10.1-2.1" * under Debian Linux BUSTER 10.1 *********************************
[begin humor/OT] Oh no, why are there no asterisks on the right side? It looks so asymmetrical? SCNR, see also: https://xkcd.com/859/ [end humor/OT]
Attachment:
pgpCAkAYF4x4f.pgp
Description: PGP signature