[Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[cshanahan]

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

Hello,

I was reading PowerTOP documentation and was curious whether it could help me better manage power on my HP EliteBook 6930p laptop. I am running PowerTOP v.2.0 on openSUSE 12.2 64-bit. After looking at some of my options from the Overview and Stats tabs, I elected to run 'powertop --calibrate' as the docs suggest. PowerTOP did not complete the calibration process; it exited with a seg fault. Now the hardware button for WiFi (small button along the top of the laptop near the screen) flashes constantly. I'm concerned that PowerTOP caused some sort of hardware problem and damaged my laptop.

Is there a way for me to check what PowerTOP did to my machine?
Is there a way for me to completely revert any changes made by PowerTOP?

uname -a
Linux 6930p.site 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00 UTC 2012 (259fc87) x86_64 x86_64 x86_64 GNU/Linux

6930p:~ # powertop --calibrate
Starting PowerTOP power estimate calibration 
Calibrating idle
Segmentation fault


Any help would be greatly appreciated.

--
Chris

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Kok, Auke-jan H]

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

On Sun, Nov 4, 2012 at 7:51 AM,  <cshanahan(a)comcast.net> wrote:
> Hello,
>
> I was reading PowerTOP documentation and was curious whether it could help me better manage power on my HP EliteBook 6930p laptop. I am running PowerTOP v.2.0 on openSUSE 12.2 64-bit. After looking at some of my options from the Overview and Stats tabs, I elected to run 'powertop --calibrate' as the docs suggest. PowerTOP did not complete the calibration process; it exited with a seg fault. Now the hardware button for WiFi (small button along the top of the laptop near the screen) flashes constantly. I'm concerned that PowerTOP caused some sort of hardware problem and damaged my laptop.
>
> Is there a way for me to check what PowerTOP did to my machine?

the calibration file will be instrumental, check if there are any
files under /var/cache/powertop?

> Is there a way for me to completely revert any changes made by PowerTOP?

reboot.

Does the wifi LED still flash after a reboot? If so, I'm wondering if
it was RFKILL'ed. the 'rfkill' tool may be usable to un-rfkill it
again.

None of the changes powertop makes are permanent, and your systemd
should be operational if you reboot.

> uname -a
> Linux 6930p.site 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00 UTC 2012 (259fc87) x86_64 x86_64 x86_64 GNU/Linux
>
> 6930p:~ # powertop --calibrate
> Starting PowerTOP power estimate calibration
> Calibrating idle
> Segmentation fault

If you can, compile powertop from git, enable debug symbols (-g) and
run it under gdb and capture a backtrace, that will help us a lot
already to figure out where the problem may be.

Cheers,


Auke

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Sergey Senozhatsky]

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

On (11/04/12 22:47), Kok, Auke-jan H wrote:
> On Sun, Nov 4, 2012 at 7:51 AM,  <cshanahan(a)comcast.net> wrote:
> > Hello,
> >
> > I was reading PowerTOP documentation and was curious whether it could help me better manage power on my HP EliteBook 6930p laptop. I am running PowerTOP v.2.0 on openSUSE 12.2 64-bit. After looking at some of my options from the Overview and Stats tabs, I elected to run 'powertop --calibrate' as the docs suggest. PowerTOP did not complete the calibration process; it exited with a seg fault. Now the hardware button for WiFi (small button along the top of the laptop near the screen) flashes constantly. I'm concerned that PowerTOP caused some sort of hardware problem and damaged my laptop.
> >
> > Is there a way for me to check what PowerTOP did to my machine?
> 
> the calibration file will be instrumental, check if there are any
> files under /var/cache/powertop?
> 
> > Is there a way for me to completely revert any changes made by PowerTOP?
> 
> reboot.
> 
> Does the wifi LED still flash after a reboot? If so, I'm wondering if
> it was RFKILL'ed. the 'rfkill' tool may be usable to un-rfkill it
> again.
> 
> None of the changes powertop makes are permanent, and your systemd
> should be operational if you reboot.
> 
> > uname -a
> > Linux 6930p.site 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00 UTC 2012 (259fc87) x86_64 x86_64 x86_64 GNU/Linux
> >
> > 6930p:~ # powertop --calibrate
> > Starting PowerTOP power estimate calibration
> > Calibrating idle
> > Segmentation fault
> 
> If you can, compile powertop from git, enable debug symbols (-g) and
> run it under gdb and capture a backtrace, that will help us a lot
> already to figure out where the problem may be.
> 

can you please do the following one (may be it'll work out w/o powertop
re-compile)

gdb PATH_TO_POWERTOP_BINARY
$ run --calibrate
$ bt


	-ss

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[cshanahan]

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

>> I was reading PowerTOP documentation and was curious whether it could help me
>> better manage power on my HP EliteBook 6930p laptop. I am running PowerTOP
>> v.2.0 on openSUSE 12.2 64-bit. After looking at some of my options from the
>> Overview and Stats tabs, I elected to run 'powertop --calibrate' as the docs
>> suggest. PowerTOP did not complete the calibration process; it exited with a
>> seg fault. Now the hardware button for WiFi (small button along the top of
>> the laptop near the screen) flashes constantly. I'm concerned that PowerTOP
>> caused some sort of hardware problem and damaged my laptop.
>>
>> Is there a way for me to check what PowerTOP did to my machine?
>
>
> the calibration file will be instrumental, check if there are any
> files under /var/cache/powertop?


Yes, there are two files in /var/cache/powertop/ though they are empty.

cms(a)6930p:~> ll /var/cache/powertop/
total 8
drwxr-xr-x  2 root root 4096 Nov  4 10:10 ./
drwxr-xr-x 15 root root 4096 Nov  4 10:10 ../
-rw-r--r--  1 root root    0 Nov  4 10:48 saved_parameters.powertop
-rw-r--r--  1 root root    0 Nov  4 10:48 saved_results.powertop


>> Is there a way for me to completely revert any changes made by PowerTOP?
>
> reboot.


The problem persists after many reboots.


> Does the wifi LED still flash after a reboot? If so, I'm wondering if
> it was RFKILL'ed. the 'rfkill' tool may be usable to un-rfkill it
> again.


I'm not sure about this one, but rfkill in not installed on my machine.
Are you suggesting I install rfkill and use it to fix the problem?


> None of the changes powertop makes are permanent, and your systemd
> should be operational if you reboot.
>
> If you can, compile powertop from git, enable debug symbols (-g) and
> run it under gdb and capture a backtrace, that will help us a lot
> already to figure out where the problem may be.


I may try the newer version (v2.1) from RPM before compiling. I'll report
back.

Thank you for your suggestions.


--
Chris

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[cshanahan]

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

>> I was reading PowerTOP documentation and was curious whether it could help me
>> better manage power on my HP EliteBook 6930p laptop. I am running PowerTOP
>> v.2.0 on openSUSE 12.2 64-bit. After looking at some of my options from the
>> Overview and Stats tabs, I elected to run 'powertop --calibrate' as the docs
>> suggest. PowerTOP did not complete the calibration process; it exited with a
>> seg fault. Now the hardware button for WiFi (small button along the top of
>> the laptop near the screen) flashes constantly. I'm concerned that PowerTOP
>> caused some sort of hardware problem and damaged my laptop.
>>
>> Is there a way for me to check what PowerTOP did to my machine?
>>
>> Is there a way for me to completely revert any changes made by PowerTOP?
>>
>> uname -a
>> Linux 6930p.site 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00 UTC 2012 (259fc87) x86_64 x86_64 x86_64 GNU/Linux
>>
>> 6930p:~ # powertop --calibrate
>> Starting PowerTOP power estimate calibration
>> Calibrating idle
>> Segmentation fault
>
>
> can you please do the following one (may be it'll work out w/o powertop
> re-compile)
>
> gdb PATH_TO_POWERTOP_BINARY
> $ run --calibrate
> $ bt


Sure can.

6930p:~ # gdb /usr/sbin/powertop
GNU gdb (GDB) SUSE (7.4.50.20120603-2.1.2)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/powertop...(no debugging symbols found)...done.
Missing separate debuginfos, use: zypper install powertop-debuginfo-2.0-2.1.2.x86_64
(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 17369.

Program received signal SIGSEGV, Segmentation fault.
0x000000000042885c in ?? ()
(gdb) bt
#0  0x000000000042885c in ?? ()
#1  0x000000000040ff30 in ?? ()
#2  0x0000000000442f15 in ?? ()
#3  0x000000000043fd7a in ?? ()
#4  0x0000000000406f98 in ?? ()
#5  0x00007ffff6597455 in __libc_start_main () from /lib64/libc.so.6
#6  0x000000000040748d in ?? ()
#7  0x00007fffffffe378 in ?? ()
#8  0x0000000000000000 in ?? ()
(gdb) 


I hope this helps. The WiFi hardware light continues to blink, though WiFi
seems to work as expected.

Again, Thank you.


--
Chris

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Thomas Spura]

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

On Fri, Nov 9, 2012 at 2:37 AM, <cshanahan(a)comcast.net> wrote:

> >> I was reading PowerTOP documentation and was curious whether it could
> help me
> >> better manage power on my HP EliteBook 6930p laptop. I am running
> PowerTOP
> >> v.2.0 on openSUSE 12.2 64-bit. After looking at some of my options from
> the
> >> Overview and Stats tabs, I elected to run 'powertop --calibrate' as the
> docs
> >> suggest. PowerTOP did not complete the calibration process; it exited
> with a
> >> seg fault. Now the hardware button for WiFi (small button along the top
> of
> >> the laptop near the screen) flashes constantly. I'm concerned that
> PowerTOP
> >> caused some sort of hardware problem and damaged my laptop.
> >>
> >> Is there a way for me to check what PowerTOP did to my machine?
> >>
> >> Is there a way for me to completely revert any changes made by PowerTOP?
> >>
> >> uname -a
> >> Linux 6930p.site 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00
> UTC 2012 (259fc87) x86_64 x86_64 x86_64 GNU/Linux
> >>
> >> 6930p:~ # powertop --calibrate
> >> Starting PowerTOP power estimate calibration
> >> Calibrating idle
> >> Segmentation fault
> >
> >
> > can you please do the following one (may be it'll work out w/o powertop
> > re-compile)
> >
> > gdb PATH_TO_POWERTOP_BINARY
> > $ run --calibrate
> > $ bt
>
>
> Sure can.
>
> 6930p:~ # gdb /usr/sbin/powertop
> GNU gdb (GDB) SUSE (7.4.50.20120603-2.1.2)
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-suse-linux".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/sbin/powertop...(no debugging symbols
> found)...done.
> Missing separate debuginfos, use: zypper install
> powertop-debuginfo-2.0-2.1.2.x86_64
> (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 17369.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000042885c in ?? ()
> (gdb) bt
> #0  0x000000000042885c in ?? ()
> #1  0x000000000040ff30 in ?? ()
> #2  0x0000000000442f15 in ?? ()
> #3  0x000000000043fd7a in ?? ()
> #4  0x0000000000406f98 in ?? ()
> #5  0x00007ffff6597455 in __libc_start_main () from /lib64/libc.so.6
> #6  0x000000000040748d in ?? ()
> #7  0x00007fffffffe378 in ?? ()
> #8  0x0000000000000000 in ?? ()
> (gdb)
>
>
> I hope this helps. The WiFi hardware light continues to blink, though WiFi
> seems to work as expected.
>

The "??" will turn into real functions, when you install powertop-debuginfo
from above:
Missing separate debuginfos, use: zypper install
powertop-debuginfo-2.0-2.1.2.x86_64

Could you install that package and try it again please?

Greetings,
     Tom

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4070 bytes --]

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[cshanahan]

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

> Sent: Friday, November 9, 2012 2:20:59 AM
> Subject: Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault
>>
>> can you please do the following one (may be it'll work out w/o powertop
>> re-compile)
>>
>> gdb PATH_TO_POWERTOP_BINARY
>> $ run --calibrate
>> $ bt
>>
>>
> The "??" will turn into real functions, when you install powertop-debuginfo
> from above:
> Missing separate debuginfos, use: zypper install
> powertop-debuginfo-2.0-2.1.2.x86_64
>
> Could you install that package and try it again please?


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)


Do you need me to install the additional missing debuginfos (noted above) or is
this sufficient?


--
Chris

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Sergey Senozhatsky]

[-- 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 

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Sergey Senozhatsky]

[-- 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

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[cshanahan]

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

----- Original Message -----
Sent: Sunday, November 11, 2012 2:45:28 PM
Subject: Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

>> 
>> (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?

Yes. Happens all the time.


> a *very* stupid question - do you have /proc/cpuinfo file?

Yes, I do.

Any idea about my problem?

Thank you for youe help.


--
Chris

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Sergey Senozhatsky]

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

On (11/12/12 02:01), cshanahan(a)comcast.net 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?
> 
> Yes. Happens all the time.
> 
>

hm. this is very-very early stages of calibration process, and it's very
unlikely that powertop has done something to your system.

 
> > a *very* stupid question - do you have /proc/cpuinfo file?
> 
> Yes, I do.
> 
> Any idea about my problem?
> 

are you talking about WIFI button?


may I ask you to do two things

	$ ls  /proc/cpuinfo
and
	$ cat /proc/cpuinfo


	-ss

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[Sergey Senozhatsky]

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

On (11/13/12 22:28), Sergey Senozhatsky wrote:
> may I ask you to do two things
> 
> 	$ ls  /proc/cpuinfo
> and
> 	$ cat /proc/cpuinfo
> 
> 

$ ls -la /proc/cpuinfo, of course.
sorry.

	-ss

Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault

[cshanahan]

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

----- Original Message -----
Sent: Tuesday, November 13, 2012 2:28:39 PM
Subject: Re: [Powertop] Strange Behavior - PowerTOP 2.0 Seg Fault
>
> hm. this is very-very early stages of calibration process, and it's very
> unlikely that powertop has done something to your system.
>
>>
>> a *very* stupid question - do you have /proc/cpuinfo file?
>>
>> Yes, I do.
>>
>> Any idea about my problem?
>>
>
> are you talking about WIFI button?


Yes sir, the WIFI button. It started flashing (orange (off) to blue (on)) the moment I ran PowerTop and continues whenever I run openSUSE. I set the machine up to dual-boot openSUSE and Win7 Pro. Windows does not exhibit this behavior. I have tried a number of LiveCDs as well, such as Mint, Ubuntu, even an openSUSE KDE LiveCD, and none exhibits this behavior.

Incidentally, a number of other things happened when I ran PowerTop on this machine. The screen went black and the WIFI hardware button switched to off (orange). After ~two minutes the screen came back to life, albeit at 40% power. I had to push the WIFI button to reenable WIFI. At that point, and since then, the button flashes.

I also checked the BIOS to make sure no changes were made. I'm fairly sure the BIOS is unchanged.


> may I ask you to do two things
>
>	$ ls  /proc/cpuinfo
> and
>	$ cat /proc/cpuinfo
>

Sure.

cms(a)6930p:~> ls -al /proc/cpuinfo 
-r--r--r-- 1 root root 0 Nov 13 20:00 /proc/cpuinfo
cms(a)6930p:~> cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Duo CPU     T9800  @ 2.93GHz
stepping        : 10
microcode       : 0xa0b
cpu MHz         : 800.000
cache size      : 6144 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority
bogomips        : 5851.79
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Duo CPU     T9800  @ 2.93GHz
stepping        : 10
microcode       : 0xa0b
cpu MHz         : 800.000
cache size      : 6144 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1      
initial apicid  : 1      
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority
bogomips        : 5851.79
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:


--
Chris