Package: powertop
Version: 1.97-2
Followup-For: Bug #671836

Dear Maintainer,

don't know is this is same issue or not, but i have similar crash at startup,
last strace output:

open("/proc/cpuinfo", O_RDONLY|O_LARGEFILE) = 3
read(3, "processor\t: 0\nvendor_id\t: Genuin"..., 8191) = 554
open("/sys/devices/system/cpu/cpu0/topology/core_id", O_RDONLY|O_LARGEFILE) = 4
read(4, "0\n", 8191)                    = 2
close(4)                                = 0
open("/sys/devices/system/cpu/cpu0/topology/physical_package_id",
O_RDONLY|O_LARGEFILE) = 4
read(4, "-1\n", 8191)                   = 3
close(4)                                = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Segmentation fault

there in /cpu/cpu.cpp:

static void handle_one_cpu(unsigned int number, char *vendor, int family, int
model)
{
        char filename[1024];
        ifstream file;
        unsigned int package_number = 0;
        unsigned int core_number = 0;

blabla
        sprintf(filename,
"/sys/devices/system/cpu/cpu%i/topology/physical_package_id", number);
        file.open(filename, ios::in);
        if (file) {
                file >> package_number;
                file.close();
        }

package_number is unsigned, but:

cat /sys/devices/system/cpu/cpu0/topology/physical_package_id
-1

may be this is a problem?







-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.19-rt31-rc1-r249 (PREEMPT)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/dash

Versions of packages powertop depends on:
ii  libc6         2.13-33
ii  libgcc1       1:4.7.0-8
ii  libncursesw5  5.9-7
ii  libnl2        2.0-1
ii  libpci3       1:3.1.9-3
ii  libstdc++6    4.7.0-8
ii  zlib1g        1:1.2.7.dfsg-11

powertop recommends no packages.

Versions of packages powertop suggests:
pn  cpufrequtils       <none>
pn  laptop-mode-tools  <none>

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to