Reply
Thread Tools
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#71
Originally Posted by StocChr View Post
after several problems, i did yesterday night a full reset.
i flashed the eMMC and the rootfs

i installed all programms, overclocked, cssu, ...

Code:
Nokia-N900:~# powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 29606us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |   0.7% |          |  1150 MHz |   nan% |
     C1 |   0.0% |          | 
     C2 |   1.6% |    7.8ms | 
     C3 |   4.0% |   63.4ms | 
     C4 |  93.7% | 2343.4ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |        198 |           INTC | i2c_omap
     37 |         76 |           INTC | gp
     11 |         50 |           INTC | prcm
     86 |         35 |           INTC | mmc1
     57 |         22 |           INTC | i2c_omap
     21 |          9 |           INTC | SGX
     12 |          4 |           INTC | DMA

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |         23 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
   2205 |         19 |     osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
      0 |         19 |  <kernel core> | hrtimer_start (tick_sched_timer)
     38 |         16D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    600 |          7 |          mmcqd | schedule_timeout (process_timeout)
   1018 |          4 |           Xorg | queue_delayed_work (delayed_work_timer_fn)
    897 |          4 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    986 |          3 |       sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    600 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    678 |          3 |           dsme | do_nanosleep (hrtimer_wakeup)
    678 |          3 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
   1018 |          2 |           Xorg | hrtimer_start (it_real_fn)
    897 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    897 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    704 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    897 |          2 |      bme_RX-51 | schedule_timeout (process_timeout)
     30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
     14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
    600 |          1 |          mmcqd | schedule_timeout (process_timeout)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
      0 |          1 |  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
   2225 |          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:  97%|RET:   0%|INA:   0%| ON:   2%| now:(OFF)
    per |OFF:  97%|RET:   1%|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:  93%|RET:   2%|INA:   0%| ON:   3%| now:(ON)
   neon |OFF:  93%|RET:   4%|INA:   1%| ON:   0%| now:(ON)
    mpu |OFF:  93%|RET:   4%|INA:   1%| 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   517,  17.2/s | IRQ  394,  13.1/s | Timers  123,   4.1/s
HW wakeups       50,   1.7/s |     Real gp_timers expired   76,   2.5/s
is the cpu usage now, as it should be?

cheers

finally you got it! What you have there is about as good as you can get 'stock'. For further battery, enable smart reflex 1+2 and overclock 250-805. Don't install programs that poll the hardware or widgets that relentlessly autoupdate.

Job done.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 

The Following User Says Thank You to vi_ For This Useful Post:
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#72
Originally Posted by p900 View Post
This is my powertop output in case someone can help me find what drains my battery.
it's not a serious situation but I feel my battery can perform better (around 15% more)

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

C# | Ratio | Avg/dura | Frequency | Ratio 
--------+--------+----------+-----------+--------+ 
C0 | 1.5% | | 600 MHz | 0.0% | 
C1 | 1.3% | 3.8ms | 550 MHz | 0.0% | 
C2 | 77.1% | 127.2ms | 500 MHz | 0.0% | 
C3 | 14.3% | 538.2ms | 250 MHz | 100.0% | 
C4 | 5.7% | 569.9ms | 

IRQ# | Activity | Type | Name 
--------+------------+----------------+--------------------------- 
57 | 289 | INTC | i2c_omap 
56 | 171 | INTC | i2c_omap 
37 | 161 | INTC | gp 
11 | 137 | INTC | prcm 
21 | 5 | INTC | SGX 
86 | 2 | INTC | mmc1 

PID# | Activity | Name | Function Entry (Expire) 
--------+------------+----------------+--------------------------- 
0 | 296 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer) 
38 | 86D| awk | cpufreq_governor_dbs (delayed_work_timer_fn) 
1204 | 60 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup) 
0 | 39 | <kernel core> | hrtimer_start (tick_sched_timer) 
793 | 21 | mce | schedule_hrtimeout_range (hrtimer_wakeup) 
3820 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup) 
709 | 12 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 
3786 | 8 | skyhost | futex_wait (hrtimer_wakeup) 
593 | 8 | mmcqd | schedule_timeout (process_timeout) 
3780 | 7 | skyhost | do_nanosleep (hrtimer_wakeup) 
546 | 7 | wl12xx | schedule_timeout (process_timeout) 
546 | 7 | wl12xx | queue_delayed_work (delayed_work_timer_fn) 
593 | 6 | mmcqd | queue_delayed_work (delayed_work_timer_fn) 
709 | 6 | bme_RX-51 | schedule_timeout (process_timeout) 
10 | 4 | omap2_mcspi | inet_twsk_schedule (inet_twdr_hangman) 
3771 | 4 |telepathy-pecan | schedule_hrtimeout_range (hrtimer_wakeup) 
593 | 4 | mmcqd | cfq_completed_request (cfq_idle_slice_timer) 
1215 | 3 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn) 
807 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn) 
2801 | 3 | browserd | futex_wait (hrtimer_wakeup) 
3771 | 3 |telepathy-pecan | neigh_add_timer (neigh_timer_handler) 
793 | 3 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler) 
1258 | 3 | wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer) 
709 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup) 
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn) 
665 | 2 | dsme | do_nanosleep (hrtimer_wakeup) 
665 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer) 
862 | 1 | Xorg | hrtimer_start (it_real_fn) 
862 | 1 | Xorg | queue_delayed_work (delayed_work_timer_fn) 
709 | 1 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 
1204 | 1 |hildon-status-m | queue_delayed_work (delayed_work_timer_fn) 
593 | 1 | mmcqd | schedule_timeout (process_timeout) 
546 | 1 | wl12xx | schedule_timeout (process_timeout) 
3771 | 1 |telepathy-pecan | sk_reset_timer (tcp_write_timer) 
1 | 1 | <kernel core> | inet_initpeers (peer_check_expire) 
3788 | 1 | skyhost | schedule_hrtimeout_range (hrtimer_wakeup) 
3964 | 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: 20%|RET: 77%|INA: 0%| ON: 2%| now:(ON) 
dss |OFF: 0%|RET: 0%|INA: 0%| ON: 100%| now:(ON) 
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF) 
core |OFF: 0%|RET: 0%|INA: 96%| ON: 3%| now:(ON) 
neon |OFF: 5%|RET: 14%|INA: 77%| ON: 2%| now:(ON) 
mpu |OFF: 5%|RET: 14%|INA: 77%| ON: 2%| 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 | MMC2 | 
core3 | USBTLL 
wkup | GPT1 | 32KSYNC | GPIO1 
| WDT1 | 
ckgen | CORE | PERI | 96M 
| 48M | 12M | 54M 
| EMU_CORE | 
dss | DSS_IDLE 
per | GPIO2 | GPIO3 | GPIO4 
| GPIO5 | GPIO6 | 

Total wakeups 1395, 46.5/s | IRQ 765, 25.5/s | Timers 630, 21.0/s 
HW wakeups 137, 4.6/s | Real gp_timers expired 161, 5.4/s 
~ $

there are not enough picard f/palms in the world for this.

do EVERYTHING that was explained to the last guy including 'the procedure'. Come back, tell us what you have done and post your results. Only then can we trouble shoot.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#73
Well, I didn't read the whole thread but from initial "top" output it seems the problem with hildon-home again. It can loop if some modification is done in "Application" menu. Or it is related with installation of some group application menu software, please search forum.
 
Temporal's Avatar
Posts: 323 | Thanked: 189 times | Joined on Oct 2010 @ Brazil
#74
Did you install flashlight-extra, camkeyd or dbus-switchboard? I would BET that any of these are your bad guys. If flashlight-extra is installed, you'll need to do this:
http://talk.maemo.org/showpost.php?p...p;postcount=19
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.
 
Posts: 306 | Thanked: 38 times | Joined on Dec 2009 @ Austria
#75
Originally Posted by vi_ View Post
finally you got it! What you have there is about as good as you can get 'stock'. For further battery, enable smart reflex 1+2 and overclock 250-805. Don't install programs that poll the hardware or widgets that relentlessly autoupdate.

Job done.
i played with smartreflex with following results:

250-850MHz: device reboot after enabling smartreflex
250-805MHz: device runs smooth without reboots

what does smartreflex exactly do? why it doenst run with 850MHz?
what about ignore nice load? 0 or 1?

cheers

EDIT: my kernel configuration

Code:
MINFREQ=250
MAXFREQ=805
FREQS="0:30,90 250:38,180 500:48,360 550:48,400 600:54,430 700:54,430 750:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 "
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
IGNORE_NICE_LOAD=0
UP_THRESHOLD=75
SAMPLING_RATE=150000
POWERSAVE_BIAS=0

Last edited by StocChr; 2011-03-03 at 07:09.
 
Posts: 212 | Thanked: 66 times | Joined on May 2010 @ India
#76
please somebody with a good battery life post the output of powertop here so that people like me will get a chance to further decipher wt is going with our batteries.Thank you.
 
Posts: 306 | Thanked: 38 times | Joined on Dec 2009 @ Austria
#77
Originally Posted by udaychaitanya16 View Post
please somebody with a good battery life post the output of powertop here so that people like me will get a chance to further decipher wt is going with our batteries.Thank you.
http://talk.maemo.org/showpost.php?p...2&postcount=70
 
Posts: 306 | Thanked: 38 times | Joined on Dec 2009 @ Austria
#78
Originally Posted by vi_ View Post
finally you got it! What you have there is about as good as you can get 'stock'. For further battery, enable smart reflex 1+2 and overclock 250-805. Don't install programs that poll the hardware or widgets that relentlessly autoupdate.

Job done.
i played with smartreflex with following results:

250-850MHz: device reboot after enabling smartreflex
250-805MHz: device runs smooth without reboots

what does smartreflex exactly do? why it doenst run with 850MHz?
what about ignore nice load? 0 or 1?

cheers

EDIT: my kernel configuration

Code:
MINFREQ=250
MAXFREQ=805
FREQS="0:30,90 250:38,180 500:48,360 550:48,400 600:54,430 700:54,430 750:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 "
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
IGNORE_NICE_LOAD=0
UP_THRESHOLD=75
SAMPLING_RATE=150000
POWERSAVE_BIAS=0
 
Posts: 122 | Thanked: 17 times | Joined on Jun 2010
#79
i reflashed my phone recently and slowly started adding apps back on
and watching 2 see if any cause high cpu usgae when idle as i had that problem b4
i got to flash light extra hexahop and kanban and got high cpu usage so uninstalled kanban and hexahop and still had high cpu so uninstalled flash light extra and it stopped
i then installed flash light extra gtk version and cpu looked fine for a few hrs so installed hexahop and kanban and then got high cpu usage again so uninstalled both of them again and was still high cpu usage so uninstalled flash light extra gtk aswell and still having high cpu usage when the phone is idle
yet b4 i installed those apps it was running perfect not using any cpu usage unless i unlocked it and used it
now over night its draining the bttery real fast and battery graph is showing steady cpu usage while it should be doing nothing ??
is there settings left behind that can cause this?


Code:
home/user # powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 30m 30s 19867us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |  98.5% |          |  1150 MHz |   nan% |
     C1 |   0.0% |    0.4ms | 
     C2 |   0.1% |    8.6ms | 
     C3 |   0.4% |  164.6ms | 
     C4 |   1.1% |  922.5ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     37 |        442 |           INTC | gp
     56 |        236 |           INTC | i2c_omap
     11 |        170 |           INTC | prcm
     86 |         89 |           INTC | mmc1
     57 |         30 |           INTC | i2c_omap
     12 |         24 |           INTC | DMA
    225 |         14 |           GPIO | omap2-onenand
     21 |          9 |           INTC | SGX

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        364 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
     38 |         47D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
      0 |         22 |  <kernel core> | hrtimer_start (tick_sched_timer)
   3374 |         19 |     osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    668 |         19 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
    581 |         17 |          mmcqd | schedule_timeout (process_timeout)
    707 |          7 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    581 |          5 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
   1008 |          3 |           Xorg | queue_delayed_work (delayed_work_timer_fn)
    707 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
    962 |          2 |       sgx_perf | queue_delayed_work (delayed_work_timer_fn)
      1 |          2D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    707 |          2 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    707 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
   1246 |          2 |        signond | futex_wait (hrtimer_wakeup)
   1352 |          2 |  BatteryGraphd | start_this_handle (commit_timeout)
    668 |          2 |           dsme | do_nanosleep (hrtimer_wakeup)
     30 |          2 |          mount | setup_wb_timer (wb_timer_fn)
   3565 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   1246 |          1 |        signond | schedule_hrtimeout_range (hrtimer_wakeup)
   3579 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   3593 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   1352 |          1 |  BatteryGraphd | schedule_hrtimeout_range (hrtimer_wakeup)
   3607 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   3621 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   3635 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   1352 |          1 |  BatteryGraphd | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
   3649 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
    693 |          1D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
   3663 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   3677 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
   3691 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
    934 |          1 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
   2307 |          1 |       browserd | futex_wait (hrtimer_wakeup)
   3705 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   3719 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   3733 |          1 |          sleep | do_nanosleep (hrtimer_wakeup)
   1032 |          1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
   3479 |          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:  97%|RET:   0%|INA:   0%| ON:   2%| now:(OFF)
    per |OFF:  86%|RET:   5%|INA:   0%| ON:   7%| 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:  64%|RET:  20%|INA:   1%| ON:  12%| now:(ON)
   neon |OFF:  64%|RET:  22%|INA:   5%| ON:   7%| now:(ON)
    mpu |OFF:  64%|RET:  22%|INA:   5%| ON:   7%| 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  1558,  51.9/s | IRQ 1014,  33.8/s | Timers  544,  18.1/s
HW wakeups      170,   5.7/s |     Real gp_timers expired  186,   6.2/s
 
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#80
Originally Posted by StocChr View Post
i played with smartreflex with following results:

250-850MHz: device reboot after enabling smartreflex
250-805MHz: device runs smooth without reboots

what does smartreflex exactly do? why it doenst run with 850MHz?
what about ignore nice load? 0 or 1?

cheers

EDIT: my kernel configuration

Code:
MINFREQ=250
MAXFREQ=805
FREQS="0:30,90 250:38,180 500:48,360 550:48,400 600:54,430 700:54,430 750:54,430 805:54,430 850:54,500 900:54,500 950:54,500 1000:60,500 1100:72,520 1150:72,520 "
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
IGNORE_NICE_LOAD=0
UP_THRESHOLD=75
SAMPLING_RATE=150000
POWERSAVE_BIAS=0
This talks about smartreflex.

Think of smart relfex as a scaling for the cpu voltage. How exactly it interacts with undervolting I am not sure, however from my own mesaurable results (with battery graph) I can see that the best way to minimise the gradient of the mAh curve is by using SR 1+2 and overclocking 250/805.

Unfortunatley 805 is the maximum you can overclock with SR enabled so you will have to choose, SR+max cpu of 805 or no SR and max CPU of 1150 (or whatever you hardware can take).

I for one have two schemes. 'profile':SR1+2 ON,CPU@250-500 with starving voltages and 'overclock':SR1+2 OFF,CPU@500-1000 with starving voltages.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 14:58.