maemo.org - Talk - View Single Post - [HELP] 50% CPU Use When "Off", Constant CPU Use ~10%

	Switch_	2011-02-02 , 08:52
	Posts: 601 \| Thanked: 549 times \| Joined on Mar 2010 @ Redditch, UK	#9

Nice one fella. Here's the powertop output (bearing in mind I have lots of widgets like pedometer / digital clock that are updating every n milliseconds on my desktop(s), three minutes after boot once system has settled in straight GSM without WiFi or any other tethered connections. Bleeding edge drivers are not loaded either. Standard O/C, 250Mhz lower and 1Ghz higher clock speeds on CPU. Switch to N900 for ouput, will update post in about 5 minutes...............

EDIT: Powertop output from device;

Code:

Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 28839us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |   0.8% |          |  1150 MHz |   nan% |
     C1 |   0.0% |    0.2ms | 
     C2 |   3.7% |    7.7ms | 
     C3 |  27.4% |  191.4ms | 
     C4 |  68.1% |  817.6ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     37 |        211 |           INTC | gp
     11 |        203 |           INTC | prcm
     56 |        125 |           INTC | i2c_omap
     57 |         34 |           INTC | i2c_omap
     21 |         10 |           INTC | SGX
     12 |          5 |           INTC | DMA
    225 |          4 |           GPIO | omap2-onenand

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        116 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
     38 |         48D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
   1274 |         30 | hildon-desktop | schedule_hrtimeout_range (hrtimer_wakeup)
   1406 |         29 |          fmtxd | schedule_hrtimeout_range (hrtimer_wakeup)
   1588 |         19 |     osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
    732 |          8 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
      0 |          5 |  <kernel core> | hrtimer_start (tick_sched_timer)
    732 |          3 |      bme_RX-51 | schedule_timeout (process_timeout)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    690 |          3 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
   1021 |          2 |           Xorg | queue_delayed_work (delayed_work_timer_fn)
    991 |          2 |       sgx_perf | queue_delayed_work (delayed_work_timer_fn)
    732 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    690 |          2 |           dsme | do_nanosleep (hrtimer_wakeup)
    718 |          2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
   1021 |          1 |           Xorg | hrtimer_start (it_real_fn)
     30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
    936 |          1 |           ohmd | schedule_hrtimeout_range (hrtimer_wakeup)
     14 |          1 |        pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
     14 |          1 |        pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
   1231 |          1 |mission-control | schedule_hrtimeout_range (hrtimer_wakeup)
   1426 |          1 |    gconftool-2 | queue_delayed_work (delayed_work_timer_fn)
    968 |          1 |            csd | schedule_hrtimeout_range (hrtimer_wakeup)
   1266 |          1 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
   1611 |          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:  95%|RET:   3%|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:  68%|RET:  26%|INA:   2%| ON:   2%| now:(ON)
   neon |OFF:  68%|RET:  27%|INA:   3%| ON:   0%| now:(ON)
    mpu |OFF:  68%|RET:  27%|INA:   3%| 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 
        |
  ckgen |          CORE |          PERI |           96M 
        |           48M |           12M |           54M 
        |      EMU_CORE |
    per |         GPIO2 |         GPIO3 |         GPIO4 
        |         GPIO5 |         GPIO6 |

Total wakeups   876,  29.2/s | IRQ  592,  19.7/s | Timers  284,   9.5/s
HW wakeups      203,   6.8/s |     Real gp_timers expired  211,   7.0/s

As I suspected it looks a helluva lot cleaner from fresh boot, so something is chewing up the system when programs are run and then close - guess it's just not a clean close. I'm no linux buff so the question is, is there anything like "Windo$e Task Manager" that I can kill processes and process trees with intergrated in this OS, or an equivalent app?

__________________
---<|| Alt + F4 for GOD MODE ||>---
---<|| Deviant Art Linky Linky ||>---

Last edited by Switch_; 2011-02-02 at 08:58.

Quote & Reply |