Package: linux
Followup-For: Bug #912596
Appears to be fixed somewhere before kernel 5.2.17.
No issues on:
$ uname -a
Linux debian 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-09-26) x86_64 GNU/Linux
$
Package:
ii linux-image-5.2.0-3-amd64 5.2.17-1
Still experiencing the same issue with newer kernel from testing.
$ uname -a
Linux debian 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64
GNU/Linux
$
Package:
ii linux-image-4.19.0-1-amd64
4.19.13-1 amd64Linux 4.19 for 64-bit
PCs (signed)
Package: linux
Followup-For: Bug #912596
(I sent this before, but for some reasons it didn't get into bts.)
I have 32 cpus. So cpus indexed 0 - 31. Yes.
* the cpu 0 - 30 show correct power/frequency info.
* cpu 31 doesn't.
Please inspect carefully my attached outputs of the tools used.
So it
I might be missing something, but ...
0 - 31 means a count of 32. Or do you have more than 32?
On 2018-11-08 11:01 a.m., Witold Baryluk wrote:
Package: linux-image-4.18
Followup-For: Bug #912596
# cpupower -c all frequency-info
analyzing CPU 0:
<- cut ->
...
analyzing CPU 30:
<- cut ->
I have 16 cores, 32 threads.
It only shows correctly first 31 CPUs. (cpu0 to cpu30). Last one cpu31 is
missing some data.
On 8 Nov 2018 19:36, "Raymond Burkholder" wrote:
I might be missing something, but ...
0 - 31 means a count of 32. Or do you have more than 32?
On 2018-11-08 11:01
Package: linux-image-4.18
Followup-For: Bug #912596
# cpupower -c all frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or
6 matches
Mail list logo