Hi, I have this problem as well. Reproducable every time. It reaches a point where it has turned off the screen and killed wifi.
root@bohr:~# uname -a Linux bohr 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux root@bohr:~# valgrind powertop -calibrate ==9791== Memcheck, a memory error detector ==9791== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==9791== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==9791== Command: powertop -calibrate ==9791== Starting PowerTOP power estimate calibration Calibrating idle ==9791== Invalid read of size 8 ==9791== at 0x4287DC: ??? (in /usr/sbin/powertop) ==9791== by 0x40FEAF: ??? (in /usr/sbin/powertop) ==9791== by 0x442E84: ??? (in /usr/sbin/powertop) ==9791== by 0x43FCF9: ??? (in /usr/sbin/powertop) ==9791== by 0x406F17: ??? (in /usr/sbin/powertop) ==9791== by 0x64A7EAC: (below main) (libc-start.c:228) ==9791== Address 0x10 is not stack'd, malloc'd or (recently) free'd ==9791== ==9791== ==9791== Process terminating with default action of signal 11 (SIGSEGV) ==9791== Access not within mapped region at address 0x10 ==9791== at 0x4287DC: ??? (in /usr/sbin/powertop) ==9791== by 0x40FEAF: ??? (in /usr/sbin/powertop) ==9791== by 0x442E84: ??? (in /usr/sbin/powertop) ==9791== by 0x43FCF9: ??? (in /usr/sbin/powertop) ==9791== by 0x406F17: ??? (in /usr/sbin/powertop) ==9791== by 0x64A7EAC: (below main) (libc-start.c:228) ==9791== If you believe this happened as a result of a stack ==9791== overflow in your program's main thread (unlikely but ==9791== possible), you can try to increase the size of the ==9791== main thread stack using the --main-stacksize= flag. ==9791== The main thread stack size used in this run was 8388608. ==9791== ==9791== HEAP SUMMARY: ==9791== in use at exit: 155,445 bytes in 116 blocks ==9791== total heap usage: 645 allocs, 529 frees, 967,255 bytes allocated ==9791== ==9791== LEAK SUMMARY: ==9791== definitely lost: 0 bytes in 0 blocks ==9791== indirectly lost: 0 bytes in 0 blocks ==9791== possibly lost: 3,621 bytes in 67 blocks ==9791== still reachable: 151,824 bytes in 49 blocks ==9791== suppressed: 0 bytes in 0 blocks ==9791== Rerun with --leak-check=full to see details of leaked memory ==9791== ==9791== For counts of detected and suppressed errors, rerun with: -v ==9791== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4) Segmentation fault Hope this helps. Please let me know if I can supply anything else that would help you investigate this issue. Regards, -- --------------------------------------------------------------- | Olof Johansson http://stdlib.se/ | | irc: zibri https://github.com/olof | --------------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
