All of lore.kernel.org
 help / color / mirror / Atom feed
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:49:46 +0300	[thread overview]
Message-ID: <20121111194946.GB3851@swordfish> (raw)
In-Reply-To: 20121111194528.GA3851@swordfish

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On (11/11/12 22:45), Sergey Senozhatsky wrote:
> 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?
> 

sorry for mistakes and typos.



 "# CONFIG_PROC_FS is not set" case?
 

	-ss

             reply	other threads:[~2012-11-11 19:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 19:49 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:45 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=20121111194946.GB3851@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.