If you can reproduce the problem, try running powetop in valgrind to pinpoint it. You can run it like this to not mess up the output:
valgrind --log-file=/tmp/powertoplog powertop valgrind work best if powertop is compiled with debug information included (-g) and not stripped, but it might give some clues about the problem even without debug information in the binary. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
