Package: powertop Version: 1.97-2 Severity: important I see this in a freshly installed Wheezy/testing. Trying to run powertop on a Dell Latitude D505 causes powertop to crash very quickly after it is started. Here is a valgrind run:
root@pxelinux:~# valgrind powertop ==3310== Memcheck, a memory error detector ==3310== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==3310== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==3310== Command: powertop ==3310== Cannot load from file /var/cache/powertop/saved_results.powertop Cannot load from file /var/cache/powertop/saved_parameters.powertop ==3310== Invalid read of size 4 ==3310== at 0x8056EDB: ??? (in /usr/sbin/powertop) ==3310== by 0x804F0C1: ??? (in /usr/sbin/powertop) ==3310== by 0x4260E45: (below main) (libc-start.c:228) ==3310== Address 0xfffffffc is not stack'd, malloc'd or (recently) free'd ==3310== ==3310== ==3310== Process terminating with default action of signal 11 (SIGSEGV) ==3310== Access not within mapped region at address 0xFFFFFFFC ==3310== at 0x8056EDB: ??? (in /usr/sbin/powertop) ==3310== by 0x804F0C1: ??? (in /usr/sbin/powertop) ==3310== by 0x4260E45: (below main) (libc-start.c:228) ==3310== If you believe this happened as a result of a stack ==3310== overflow in your program's main thread (unlikely but ==3310== possible), you can try to increase the size of the ==3310== main thread stack using the --main-stacksize= flag. ==3310== The main thread stack size used in this run was 8388608. ==3310== ==3310== HEAP SUMMARY: ==3310== in use at exit: 9,789 bytes in 22 blocks ==3310== total heap usage: 125 allocs, 103 frees, 36,829 bytes allocated ==3310== ==3310== LEAK SUMMARY: ==3310== definitely lost: 0 bytes in 0 blocks ==3310== indirectly lost: 0 bytes in 0 blocks ==3310== possibly lost: 205 bytes in 18 blocks ==3310== still reachable: 9,584 bytes in 4 blocks ==3310== suppressed: 0 bytes in 0 blocks ==3310== Rerun with --leak-check=full to see details of leaked memory ==3310== ==3310== For counts of detected and suppressed errors, rerun with: -v ==3310== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 41 from 6) Minnesegmentsfeil root@pxelinux:~# wc /boot/config-3.1.0-1-486 5880 9855 134133 /boot/config-3.1.0-1-486 root@pxelinux:~# I notice in bug #646522 that a problem with reading large kernel config might cause this, but that this problem is supposed to be fixed in Wheezy. A similar problem is bug #602289 which is said to be a duplicate of the already solved #646522. Are you sure the problem is solved in version 1.97-2? If this affect everyone and not just me, I guess the severity should be raised to make this problem release critical. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
