From: Sergey Senozhatsky <sergey.senozhatsky at gmail.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault
Date: Sun, 11 Nov 2012 22:45:28 +0300 [thread overview]
Message-ID: <20121111194528.GA3851@swordfish> (raw)
In-Reply-To: 164841353.33797.1352661160320.JavaMail.root@sz0055a.westchester.pa.mail.comcast.net
[-- Attachment #1: Type: text/plain, Size: 2859 bytes --]
On (11/11/12 19:12), cshanahan(a)comcast.net wrote:
> Done. Output below.
>
> I hope this helps to make PowerTop better, though it doesn't look like its going
> to help me with my problem. PowerTop made some change to my system that I cannot
> find. The files in /var/cache/powertop/ are empty. Something was changed with
> systemd and I can't find it. The problem persists after reboot. I can boot using
> any number of LiveCDs and I the WiFi hardware button works as expected. Hardware
> is fine.
>
> 6930p:~ # ll /var/cache/powertop/
> total 0
> -rw-r--r-- 1 root root 0 Nov 8 20:29 saved_parameters.powertop
> -rw-r--r-- 1 root root 0 Nov 8 20:29 saved_results.powertop
>
>
> (gdb) run --calibrate
> Starting program: /usr/sbin/powertop --calibrate
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Starting PowerTOP power estimate calibration
> Calibrating idle
> Detaching after fork from child process 3784.
>
> Program received signal SIGSEGV, Segmentation fault.
> perf_bundle::start (this=0x0) at perf/perf_bundle.cpp:180
> 180 perf/perf_bundle.cpp: No such file or directory.
> Missing separate debuginfos, use: zypper install glibc-debuginfo-2.15-22.6.4.x86_64
> libgcc47-debuginfo-4.7.1_20120723-1.1.1.x86_64 libncurses5-debuginfo-5.9-12.5.1.x86_64
> libnl3-200-debuginfo-3.2.9-2.1.2.x86_64 libpci3-debuginfo-3.1.9-3.1.2.x86_64
> libstdc++47-debuginfo-4.7.1_20120723-1.1.1.x86_64 zlib-debuginfo-1.2.7-2.1.2.x86_64
> (gdb) bt
> #0 perf_bundle::start (this=0x0) at perf/perf_bundle.cpp:180
> #1 0x000000000040ff30 in start_cpu_measurement () at cpu/cpu.cpp:297
> #2 0x0000000000442f15 in one_measurement (seconds=15) at main.cpp:182
> #3 0x000000000043fd7a in idle_calibration () at calibrate/calibrate.cpp:423
> #4 calibrate () at calibrate/calibrate.cpp:466
> #5 0x0000000000406f98 in main (argc=2, argv=0x7fffffffe388) at main.cpp:325
> (gdb)
>
>
hm, that's something. seems like enumerate_cpus(); failed
because perf_bundle was NULL in cpu by the time of
perf_events->start();
call, but it did not crashed on any of enumerate_cpus()
332 perf_events = new perf_power_bundle();
333
334 if (!perf_events->add_event("power:cpu_idle")){
335 perf_events->add_event("power:power_start");
336 perf_events->add_event("power:power_end");
337 }
338 if (!perf_events->add_event("power:cpu_frequency"))
339 perf_events->add_event("power:power_frequency");
so it leaves only one suspect: enumerate_cpus()
269 file.open("/proc/cpuinfo", ios::in);
270
271 if (!file)
272 return;
is that happeninig all the time?
a *very* stupid question - do you have /proc/cpuinfo file?
-ss
next reply other threads:[~2012-11-11 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 19:45 Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-14 1:04 [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault cshanahan
2012-11-13 19:44 Sergey Senozhatsky
2012-11-13 19:28 Sergey Senozhatsky
2012-11-12 2:01 cshanahan
2012-11-11 19:49 Sergey Senozhatsky
2012-11-11 19:12 cshanahan
2012-11-09 7:20 Thomas Spura
2012-11-09 1:37 cshanahan
2012-11-09 1:29 cshanahan
2012-11-05 10:32 Sergey Senozhatsky
2012-11-05 6:47 Kok, Auke-jan H
2012-11-04 15:51 cshanahan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121111194528.GA3851@swordfish \
--to=powertop@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.