Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #82282 > unrolled thread

Bug#1069587: linux-cpupower: turbostat core dump in compute_average, regression

Started byWitold Baryluk <witold.baryluk@gmail.com>
First post2024-04-21 07:40 +0200
Last post2025-02-20 15:50 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1069587: linux-cpupower: turbostat core dump in compute_average, regression Witold Baryluk <witold.baryluk@gmail.com> - 2024-04-21 07:40 +0200
    Bug#1069587: marked as done (linux-cpupower: turbostat core dump  in compute_average, regression) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-02-20 15:50 +0100

#82282 — Bug#1069587: linux-cpupower: turbostat core dump in compute_average, regression

FromWitold Baryluk <witold.baryluk@gmail.com>
Date2024-04-21 07:40 +0200
SubjectBug#1069587: linux-cpupower: turbostat core dump in compute_average, regression
Message-ID<Ivy5H-7NC0-1@gated-at.bofh.it>
Package: linux-cpupower
Version: 6.7.9-2
Severity: normal
X-Debbugs-Cc: witold.baryluk@gmail.com


turbostat 6.7.9-2 core dumps on my AMD Threadripper 2950X

linux-cpupower_6.6.15-2_amd64.deb works fine.

gdb session with 6.7.9-2

root@debian:~# gdb turbostat 
GNU gdb (Debian 13.2-1) 13.2
Reading symbols from turbostat...
Reading symbols from /usr/lib/debug/.build-id/6f/8e4bb8d39e0b45899098c6bd0307918833eeb8.debug...
(gdb) r
Starting program: /usr/sbin/turbostat 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
turbostat version 2023.11.07 - Len Brown <lenb@kernel.org>
Kernel command line: BOOT_IMAGE=/live/vmlinuz-6.6.15-amd64 intel_iommu=on iommu=pt amd_iommu=on radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.ppfeaturemask=0xffffffff amdgpu.audio=0 processors.max_cstate=1 intel_idle.max_cstate=0 idle=halt modprobe.blacklist=snd_hda_codec_hdmi,snd_hda_intel boot=live components locales=en_US.UTF-8 findiso=
CPUID(0): AuthenticAMD 0xd CPUID levels
CPUID(1): family:model:stepping 0x17:8:2 (23:8:2) microcode 0x0
CPUID(0x80000000): max_extended_levels: 0x8000001f
CPUID(1): SSE3 MONITOR - - - TSC MSR - HT -
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX No-Hybrid
cpu0: cpufreq driver: acpi-cpufreq
cpu0: cpufreq governor: performance
cpufreq boost: 1
/dev/cpu_dma_latency: 4000 usec (constrained)
current_driver: none
current_governor: menu
current_governor_ro: menu
RAPL: 234 sec. Joule Counter Range, at 280 Watts
[New Thread 0x7ffff7fc1740 (LWP 1098480)]
[New Thread 0x7ffff7d886c0 (LWP 1098481)]
[Thread 0x7ffff7d886c0 (LWP 1098481) exited]

Thread 1 "turbostat" received signal SIGFPE, Arithmetic exception.
0x000055555555fc24 in compute_average (t=<optimized out>, c=<optimized out>, p=<optimized out>) at /build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:2479
2479  /build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c: No such file or directory.
(gdb) bt
#0  0x000055555555fc24 in compute_average (t=<optimized out>, c=<optimized out>, p=<optimized out>) at /build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:2479
#1  0x00005555555676ea in turbostat_loop () at /build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:4364
#2  0x0000555555557542 in main (argc=1, argv=0x7fffffffebe8) at /build/reproducible-path/linux-6.7.9/tools/power/x86/turbostat/turbostat.c:6753
(gdb) 


Probably some division by zero in the code.


For comparison older version of turbostat (on same cpu and kernel) shows:

Die Core  CPU Avg_MHz Busy% Bzy_MHz TSC_MHz IPC IRQ CorWatt PkgWatt
- - - 21  1.37  1511  1750  0.67  14450 2.59  39.87
1 0 8 50  1.74  2893  3500  0.73  1115  0.38  39.87
1 0 24  44  1.42  3111  3500  0.66  822
1 1 9 68  2.17  3127  3500  0.75  1051  0.35
1 1 25  20  0.73  2696  3500  0.33  1244
1 2 10  50  1.59  3158  3500  0.50  987 0.30
1 2 26  31  0.99  3151  3500  0.61  1036
1 3 11  40  1.25  3174  3500  0.77  658 0.46
1 3 27  114 3.62  3137  3500  0.85  1186
1 4 12  102 3.20  3171  3500  0.56  1180  0.44
1 4 28  19  0.67  2860  3500  0.40  887
1 5 13  3 0.12  2810  3500  0.33  112 0.18
1 5 29  22  0.81  2768  3500  0.47  899
1 6 14  22  0.83  2670  3500  0.36  1403  0.23
1 6 30  14  0.48  2855  3500  0.35  617
1 7 15  19  0.73  2607  3500  0.41  936 0.26
1 7 31  45  1.59  2833  3500  1.21  317





-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/32 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

Versions of packages linux-cpupower depends on:
ii  libc6         2.37-17
ii  libcap2       1:2.66-5
ii  libcpupower1  6.7.9-2
ii  libpci3       1:3.10.0-2

linux-cpupower recommends no packages.

linux-cpupower suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]


#85947 — Bug#1069587: marked as done (linux-cpupower: turbostat core dump in compute_average, regression)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-02-20 15:50 +0100
SubjectBug#1069587: marked as done (linux-cpupower: turbostat core dump in compute_average, regression)
Message-ID<Kig2h-D7T-71@gated-at.bofh.it>
In reply to#82282

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 20 Feb 2025 15:39:59 +0100 (CET)
with message-id <20250220143959.B2490BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1069587,
regarding linux-cpupower: turbostat core dump in compute_average, regression
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.)


-- 
1069587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069587
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web