Active Topics

 



Notices


Reply
Thread Tools
Posts: 489 | Thanked: 404 times | Joined on Dec 2009
#1
Hi everyone,

back from holidays, I was trying to test some apps in order to resume my testing activity, when I discovered that my PowerTop no longer works. It leads to a segmentation fault.

Code:
~ $ powertop
Powertop 1.13.3
sh: status: not found
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 8881us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |   4.7% |          |  1150 MHz |   nan% |
     C1 |  95.1% |   23.4ms | 
     C2 |   0.1% |    0.2ms | 
     C3 |   0.0% |          | 
     C4 |   0.0% |          | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |       3067 |           INTC | i2c_omap
     86 |        637 |           INTC | mmc1
     37 |        579 |           INTC | gp
     12 |        509 |           INTC | DMA
     57 |        315 |           INTC | i2c_omap
     92 |        300 |           INTC | musb_hdrc
     21 |        124 |           INTC | SGX
     11 |        111 |           INTC | prcm
    225 |          2 |           GPIO | omap2-onenand
     25 |          1 |           INTC | OMAP
Segmentation fault
~ $
What should I do? Thanks in advance, any help will be appreciated, I really need that little nice utility.
 
Posts: 958 | Thanked: 483 times | Joined on May 2010
#2
did that for me too. a reboot solved the problem for me.
 
Posts: 489 | Thanked: 404 times | Joined on Dec 2009
#3
I've already rebooted several times, even removing and reinstalling PowrTop, but it never worked... This thing's driving me mad.
 
Posts: 131 | Thanked: 78 times | Joined on May 2010
#4
you need to run it as root.

make sure you have rootsh installed.

1. sudo gainroot (or root by itself)
2. powertop

also, i see your device is in c1 for the most part. bet your battery life could be better. c4 is where you don't lose much charge at all.
 

The Following User Says Thank You to m0da For This Useful Post:
Posts: 489 | Thanked: 404 times | Joined on Dec 2009
#5
Originally Posted by m0da View Post
you need to run it as root.

make sure you have rootsh installed.

1. sudo gainroot (or root by itself)
2. powertop

also, i see your device is in c1 for the most part. bet your battery life could be better. c4 is where you don't lose much charge at all.
Thanks for your efforts, I've solved my (weird) problem.

I have always used PowerTop without root privileges, so I didn't tried obtaining them. When I read your post I tried it, and it worked: after that try I used PowerTop again without root privileges and, magically, it now works again even with user privileges.

Seems like the root thing has magically unlocked PowerTop from segfault; I can't explain how that worked...

About the power consumption thing: thanks for your suggestion, but that was just an example test, my typical results are these:

Code:
~ $ powertop
Powertop 1.13.3
sh: status: not found
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 28349us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |   0.6% |          |  1150 MHz |   nan% |
     C1 |   0.0% |          | 
     C2 |   2.2% |   10.7ms | 
     C3 |   4.4% |  110.3ms | 
     C4 |  92.7% | 1855.3ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |        155 |           INTC | i2c_omap
     37 |         56 |           INTC | gp
     11 |         52 |           INTC | prcm
     57 |         40 |           INTC | i2c_omap
     86 |         37 |           INTC | mmc1
     12 |          3 |           INTC | DMA
     21 |          2 |           INTC | SGX

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |         28 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
   1874 |         19 |     osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
     38 |         13D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    736 |          8 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
      0 |          7 |  <kernel core> | hrtimer_start (tick_sched_timer)
    872 |          4 |           Xorg | queue_delayed_work (delayed_work_timer_fn)
    722 |          3 |           dsme | do_nanosleep (hrtimer_wakeup)
    722 |          3 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
    736 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
    872 |          2 |           Xorg | hrtimer_start (it_real_fn)
    833 |          2 |       sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    736 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
      1 |          2D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    721 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
     30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
    736 |          1 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    521 |          1 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
    789 |          1 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
   1806 |          1 |       browserd | futex_wait (hrtimer_wakeup)
      0 |          1 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
   1882 |          1 |       powertop | do_nanosleep (hrtimer_wakeup)

Power domain activity breakdown
Domain  | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    sgx |OFF:  99%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    per |OFF:  96%|RET:   2%|INA:   0%| ON:   0%| now:(ON)
    dss |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    cam |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
   core |OFF:  92%|RET:   3%|INA:   0%| ON:   3%| now:(ON)
   neon |OFF:  92%|RET:   4%|INA:   2%| ON:   0%| now:(ON)
    mpu |OFF:  92%|RET:   4%|INA:   2%| ON:   0%| now:(ON)
   iva2 |OFF: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)

Clock activity breakdown at end of period
Domain  | Active clocks
--------+---------------+---------------+------------------
   core |          SDRC | HSOTGUSB_IDLE |      OMAPCTRL 
        |     MAILBOXES |
   wkup |          GPT1 |       32KSYNC |         GPIO1 
        |          WDT1 |
  ckgen |          CORE |          PERI |           96M 
        |           48M |           12M |           54M 
        |      EMU_CORE |
    per |         GPIO2 |         GPIO3 |         GPIO4 
        |         GPIO5 |         GPIO6 |

Total wakeups   451,  15.0/s | IRQ  345,  11.5/s | Timers  106,   3.5/s
HW wakeups       52,   1.7/s |     Real gp_timers expired   56,   1.9/s
~ $
As you can see, my battery life isn't that bad, my CPU stays in C0 for very little times
 
Posts: 1,258 | Thanked: 672 times | Joined on Mar 2009
#6
Those are quite awesome numbers
 
Posts: 388 | Thanked: 842 times | Joined on Sep 2009 @ Finland
#7
Originally Posted by torpedo48 View Post
C0 | 4.7% | | 1150 MHz | nan% |
You really shouldn't be wondering why you are getting random segfaults on a device overclocked to 1150 MHz....
 

The Following 2 Users Say Thank You to hqh For This Useful Post:
Posts: 489 | Thanked: 404 times | Joined on Dec 2009
#8
Originally Posted by hqh View Post
You really shouldn't be wondering why you are getting random segfaults on a device overclocked to 1150 MHz....
It's not overclocked at that frequency (my actual CPU MAX frequency is 500 MHz, so it's downclocked). That represent the maximum overclock frequency possible with your actual kernel, not the actual frequency.

BTW my N900 is very stable even at the highest frequencies, never experienced a crash or a reboot (but I usually overclock at 800 MHz maximum).
 

The Following User Says Thank You to torpedo48 For This Useful Post:
Posts: 388 | Thanked: 842 times | Joined on Sep 2009 @ Finland
#9
Originally Posted by torpedo48 View Post
It's not overclocked at that frequency (my actual CPU MAX frequency is 500 MHz, so it's downclocked). That represent the maximum overclock frequency possible with your actual kernel, not the actual frequency.
Oh, ok. I haven't used that kernel (kernel-power I assume)

Originally Posted by torpedo48 View Post
BTW my N900 is very stable even at the highest frequencies, never experienced a crash or a reboot (but I usually overclock at 800 MHz maximum).
I'm sure it is, but every device has its limits

Last edited by hqh; 2010-08-20 at 15:12.
 

The Following User Says Thank You to hqh For This Useful Post:
Posts: 489 | Thanked: 404 times | Joined on Dec 2009
#10
Originally Posted by hqh View Post
I'm sure it is, but every device has its limits
That's why I've never even tried to overclock at 1150 MHz

I usually monitor my CPU temperature and I never reach overheating
 
Reply


 
Forum Jump


All times are GMT. The time now is 18:30.