Page 2 of 6 1 2 34 Last »
Reply
Thread Tools
Estel's Avatar
Estel is offline Estel
2014-07-13 , 06:36
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#11
codelad, zzztop lacks some functions of powertop. Please activate extras-devel, and search for powertop again (then, after installing, you might want to disable extras-devel again).

If you were doing the tests with every radios and programs disabled, it is very strange that CPU is only 70% of time in deepest sleep (C4). It should be 90%+. But, re-do the test with complete powertop, and of course, GPS disabled.

As for hardware failure, it's possible that some current is just converted into heat due to something broken, but then, you should notice device being much hotter than it should. Otherwise, no idea.

/Estel

// Edit

Ah, and do that powertop tests as root!
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following User Says Thank You to Estel For This Useful Post:
codelad is offline codelad
2014-07-13 , 08:52
Posts: 25 | Thanked: 19 times | Joined on Apr 2014
#12
Managed to fetch powertop, and I'm afraid the results appear to show a totally different picture (to that of my previous zzztop runs). Here's what I see:

Code:
/home/user # powertop -t 45 > ptop.txt
status: Unknown job: pmtrackerdaemon

/home/user # cat ptop.txt
Powertop 1.13.3
Sleeping for 11 seconds before sampling
Collecting data for 45 seconds
Sample interval was 30m 45s 19928us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |  97.6% |          |  1150 MHz |   nan% |
     C1 |   0.0% |          | 
     C2 |   0.4% |   83.4ms | 
     C3 |   0.3% |  309.4ms | 
     C4 |   1.6% | 1504.6ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |        315 |           INTC | i2c_omap
     37 |        155 |           INTC | gp
     11 |         91 |           INTC | prcm
     57 |         60 |           INTC | i2c_omap
     86 |         36 |           INTC | mmc1
     12 |          3 |           INTC | DMA

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |        105 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
     38 |         24D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
      0 |         21 |  <kernel core> | hrtimer_start (tick_sched_timer)
    766 |         14 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    603 |         13 |          mmcqd | schedule_timeout (process_timeout)
    731 |          7 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
    766 |          5 |      bme_RX-51 | schedule_timeout (process_timeout)
    731 |          4 |           dsme | do_nanosleep (hrtimer_wakeup)
      1 |          4D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    603 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    755 |          3D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
    766 |          3 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
   1185 |          2 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
   1144 |          2 |        signond | futex_wait (hrtimer_wakeup)
    807 |          1 |           ohmd | queue_delayed_work (delayed_work_timer_fn)
    975 |          1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
   1109 |          1 |          iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
      0 |          1 |  <kernel core> | addrconf_verify (addrconf_verify)
    843 |          1 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
   1144 |          1 |        signond | schedule_hrtimeout_range (hrtimer_wakeup)
   1511 |          1 |       browserd | futex_wait (hrtimer_wakeup)
    805 |          1 |           hald | schedule_hrtimeout_range (hrtimer_wakeup)
   1229 |          1 |tracker-indexer | schedule_hrtimeout_range (hrtimer_wakeup)
   1229 |          1 |tracker-indexer | journal_get_write_access (commit_timeout)
    603 |          1 |          mmcqd | schedule_timeout (process_timeout)
     30 |          1 |          mount | setup_wb_timer (wb_timer_fn)
   1561 |          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: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    per |OFF:   0%|RET:  98%|INA:   0%| ON:   1%| 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:   0%|RET:   0%|INA:   0%| ON: 100%| now:(ON)
   neon |OFF:  66%|RET:  13%|INA:  17%| ON:   1%| now:(ON)
    mpu |OFF:  66%|RET:  13%|INA:  17%| ON:   1%| 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 |         UART2 |
  core3 |       USBTLL
   wkup |          GPT1 |       32KSYNC |         GPIO1 
        |          WDT1 |
  ckgen |          CORE |          PERI |           96M 
        |           48M |           12M |           54M 
        |      EMU_CORE |
    per |         GPIO2 |         GPIO3 |         GPIO4 
        |         GPIO5 |         GPIO6 |

Total wakeups   883,  19.6/s | IRQ  660,  14.7/s | Timers  223,   5.0/s
HW wakeups       91,   2.0/s |     Real gp_timers expired  155,   3.4/s
I did indeed run both zzztop and powertop as root. If the results are too haphazard, I can re-flash the device one more time, set up CSSU stable and run the tests all over again.

Thank you.
 

The Following User Says Thank You to codelad For This Useful Post:
Estel's Avatar
Estel is offline Estel
2014-07-13 , 12:25
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#13
For some reason device doesn't seem to standby properly, almost at all - it is awake >98% of time, which explains the battery drain. Hoever, looking at the wakeups, I don't see anything odd (Am I missing something?).

dumb question - you had device locked with screen disabled during test, right? (I don't talk about locked as in "input code", just locked via spring switch on the right side).

/Estel

// Edit

You may try to install advanced interface switcher and disable bluetooth (or do the same manually, by unloading bluetooth modules - I don't remember which ones, now). If you're absolutely positive that it's damaged, maybe device try to access it, somehow... Unloading modules could help. Or not, won't know until you try it.
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 4 Users Say Thank You to Estel For This Useful Post:
pichlo's Avatar
pichlo is offline pichlo
2014-07-13 , 19:39
Posts: 6,447 | Thanked: 20,981 times | Joined on Sep 2012 @ UK
#14
I have two anecdotal stories to support Estel:

Story 1
I had (have but no longer use) a no-name, el-cheapo Android tablet made in China. Despite having no phone functionality, it had the Phone process running all the time. Following a recommendation on a dedicated forum, I rooted the tablet and uninstalled the Phone app. Doing that doubled the battery ife. The theory goes that the Phone process would normally do what it had to do and then go to sleep but without the hardware, it was constantly trying and failing, trying and failing...

Story 2
My wife's phone normally lasts about 4 days on a single charge. Except last week when we went on holiday: it was nearly empty after just one day. We still have no explanation except the same theory: a temporary loss of GSM connection resulting in the phone constantly trying to establish it.
 

The Following 3 Users Say Thank You to pichlo For This Useful Post:
sixwheeledbeast is offline sixwheeledbeast
2014-07-13 , 22:21
Posts: 2,290 | Thanked: 4,134 times | Joined on Apr 2010 @ UK
#15
Originally Posted by codelad View Post
@Estel: Afraid I couldn't locate the package for powertop, but found something called zzztop that claimed to be something similar.
zzztop is a perl FOSS version of powertop.
It is missing "power domain activity breakup" however, it is FOSS, optified, in Extras and doesn't have the 1150Mhz bug with KP that powertop has.

I have had odd battery drain issues before, I never got to the bottom of them as they disappeared.
I was getting odd messages in dmesg at the time.
Here's the thread if it helps http://talk.maemo.org/showthread.php?t=85701
__________________

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -


Before posting or starting a thread please try this.
 

The Following 3 Users Say Thank You to sixwheeledbeast For This Useful Post:
codelad is offline codelad
2014-07-14 , 11:59
Posts: 25 | Thanked: 19 times | Joined on Apr 2014
#16
As it turned out, the spring lock switch was broken. I bought the N900 used, and the switch has always just moved loosely. Before Estel mentioned it, I never even realized it was a "spring" switch. I took apart the device and discovered that spring in 2 pieces. By reversing the spring (and some bending with pliers), I was able to engage it to the switch again, and the switch is now functional. Requires a bit of force to use, but it always works.

I have since flashed the device again (both rootfs and emmc), set up CSSU stable. Afraid the battery drain problem remains. This is what powertop came up with:

Code:
Powertop 1.13.3
Sleeping for 11 seconds before sampling
Collecting data for 45 seconds
Sample interval was 30m 45s 20356us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |  97.6% |          |   600 MHz |   8.9% |
     C1 |   0.6% |  552.0ms |   550 MHz |   0.0% |
     C2 |   0.1% |   24.1ms |   500 MHz |   2.5% |
     C3 |   0.5% |  642.0ms |   250 MHz |  88.6% |
     C4 |   1.2% | 1429.8ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |        294 |           INTC | i2c_omap
     37 |         80 |           INTC | gp
     11 |         61 |           INTC | prcm
     57 |         60 |           INTC | i2c_omap
     86 |         60 |           INTC | mmc1
     12 |         20 |           INTC | DMA
    225 |         10 |           GPIO | omap2-onenand

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |         37 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
     37 |         19D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
      0 |         19 |  <kernel core> | hrtimer_start (tick_sched_timer)
    716 |         14 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    602 |         11 |          mmcqd | schedule_timeout (process_timeout)
    716 |          5 |      bme_RX-51 | schedule_timeout (process_timeout)
    602 |          5 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    676 |          4 |           dsme | do_nanosleep (hrtimer_wakeup)
    676 |          4 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
     29 |          3 |          mount | setup_wb_timer (wb_timer_fn)
    716 |          3 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
      1 |          3D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
   1136 |          2 |  BatteryGraphd | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
     14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
    785 |          1 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
   1380 |          1 |       browserd | futex_wait (hrtimer_wakeup)
      1 |          1D|  <kernel core> | rt_secret_timer_init (rt_secret_rebuild)
      1 |          1 |  <kernel core> | inet_initpeers (peer_check_expire)
    888 |          1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
   1136 |          1 |  BatteryGraphd | journal_get_write_access (commit_timeout)
   1550 |          1 |       powertop | do_nanosleep (hrtimer_wakeup)
   1010 |          1 |          iphbd | schedule_hrtimeout_range (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: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    per |OFF:   0%|RET:  74%|INA:   0%| ON:  25%| 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:   0%|RET:   0%|INA:   0%| ON: 100%| now:(ON)
   neon |OFF:  50%|RET:  19%|INA:   4%| ON:  25%| now:(ON)
    mpu |OFF:  50%|RET:  19%|INA:   4%| ON:  25%| 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 |         UART2 |
  core3 |       USBTLL
   wkup |          GPT1 |       32KSYNC |         GPIO1 
        |          WDT1 |
  ckgen |          CORE |          PERI |           96M 
        |           48M |           12M |           54M 
        |      EMU_CORE |
    per |         GPIO2 |         GPIO3 |         GPIO4 
        |         GPIO5 |         GPIO6 |

Total wakeups   723,  16.1/s | IRQ  585,  13.0/s | Timers  138,   3.1/s
HW wakeups       61,   1.4/s |     Real gp_timers expired   80,   1.8/s
Estel: Found a module "bluetooth" (from lsmod), and here's what happens when I attempt to unload it:

Code:
Nokia-N900:~# modprobe -r bluetooth
FATAL: Module bluetooth is in use.
Also found something I thought was suspicious, in my dmesg. I'm attaching the complete file, and here's the part I speak about:

Code:
...
[19311.320037] Bluetooth: HCI device and connection manager initialized
[19311.320098] Bluetooth: HCI socket layer initialized
[19311.356567] SSI DRIVER Version 1.1-rc2
[19311.357025] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[19311.383666] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[19311.569427] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[19311.680969] smc91x: not found (-19).
[19311.681304] hci_h4p hci_h4p: Registering HCI H4P device
[19311.804595] phy0: Selected rate control algorithm 'minstrel'
[19311.812011] hci_h4p hci_h4p: No cts from bt chip
[19311.812194] hci_h4p: probe of hci_h4p failed with error -110
[19311.812652] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
...
Also I've since cleaned the insides during disassembly. Bluetooth still doesn't work, and I'll try the advanced interface switcher next. There have been occassions when the device was warm to the touch, but I've not noticed it happen today.

I have an increasing feeling that the issue could be directly connected with the bluetooth failure.

Thank you.
Attached Files
File Type: gz dmesg_2014071401.txt.gz (4.2 KB, 62 views)
Last edited by codelad; 2014-07-14 at 12:01. Reason: Missed the attachment. Adding now.
 

The Following User Says Thank You to codelad For This Useful Post:
Estel's Avatar
Estel is offline Estel
2014-07-14 , 13:04
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#17
Originally Posted by codelad View Post
Code:
Nokia-N900:~# modprobe -r bluetooth
FATAL: Module bluetooth is in use.
Code:
[19311.320037] Bluetooth: HCI device and connection manager initialized
[19311.320098] Bluetooth: HCI socket layer initialized
[19311.356567] SSI DRIVER Version 1.1-rc2
[19311.357025] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[19311.383666] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[19311.569427] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[19311.680969] smc91x: not found (-19).
[19311.681304] hci_h4p hci_h4p: Registering HCI H4P device
[19311.804595] phy0: Selected rate control algorithm 'minstrel'
[19311.812011] hci_h4p hci_h4p: No cts from bt chip
[19311.812194] hci_h4p: probe of hci_h4p failed with error -110
[19311.812652] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
...
(...)
I have an increasing feeling that the issue could be directly connected with the bluetooth failure.

Thank you.
Same feeling here. You powertop output looks ok - no overly suspicious wakeups, etc. Yet, device doesn't want to sleep. At the same time, that bluetooth failing thing is perfectly capable of producing just that.

Now, how to solve it? I would guess that you need to somehow perma-blacklist module to avoid it's loading on boot (may be tricky, as there are few things, that ignore usual blacklist) or later, no matter what tries to load it. If you're lucky, things calling it will just go to sleep. Otherwise, they will try to load module and fail constantly, resulting in same problem - you will have to disable those things to.

This is as far as my ideas are going - I have no clue how to do it in practice, You need real gurus here. Personally, I would start in kernel-related threads (re preventing modules to load), and later, investigate what may be calling those modules on startup/during runtime - via some grep magic, or something like that.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
Last edited by Estel; 2014-07-15 at 05:07.
 

The Following 2 Users Say Thank You to Estel For This Useful Post:
pichlo's Avatar
pichlo is offline pichlo
2014-07-14 , 15:21
Posts: 6,447 | Thanked: 20,981 times | Joined on Sep 2012 @ UK
#18
Alternatively, if you are sure that BT is permanently broken, you can just as well uninstall everything remotely related to it and then reboot the device. I cannot give you a list but I would start by installing FAM, showing "all packages (advanced)" and typing "bluetooth" and/or "bt" and applying some common sense.
 

The Following 2 Users Say Thank You to pichlo For This Useful Post:
peterleinchen's Avatar
peterleinchen is offline peterleinchen
2014-07-14 , 19:16
Posts: 4,118 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#19
Why not try starting by adding a new line
Code:
bluetooth
to
/etc/modprobe.d/blacklist
and reboot?

and/or
Code:
fmtx_si4713
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
Last edited by peterleinchen; 2014-07-14 at 19:24.
 

The Following 3 Users Say Thank You to peterleinchen For This Useful Post:
codelad is offline codelad
2014-07-15 , 08:35
Posts: 25 | Thanked: 19 times | Joined on Apr 2014
#20
pichlo: I'm unsure if BT is indeed broken, but I can do perfectly well, without it. So its fine if it comes to permanently disabling it. Tried removing bluetooth related programs (did it the dpkg/apt way, since I'm used to it). Managed to successfully remove several UI packages and bt-firmware, but "bluez" lists too many dependencies. I did uninstall them, but was stuck in a reboot loop (it goes as far as the desktop, then reboots). Had to flash the device all over again. I know, I missed the "common-sense" part.

peterleinchen: The blacklist method doesn't appear to work. The module somehow always loads. Also tried unloading "fmtx_si4713" (assuming this is the FM module), and this fails too. lsmod shows the following bluetooth dependencies, which I tried to remove individually:

Code:
bluetooth              53596  3 rfcomm,l2cap,sco,hci_h4p
Was able to unload hci_h4p and sco (after disabling the bluetooth lines in the pulseaudio config file) successfully, but the others won't budge. Succeeded in stopping the bluetoothd service by commenting out lines in /etc/event.d/bluetoothd, but bluetooth still won't unload.

FYI, the FM transmitter works perfectly well (checked again today).

Here is where it stands now. I'm attaching my dmesg output, and this is what powertop shows:

Code:
Powertop 1.13.3
Sleeping for 11 seconds before sampling
Collecting data for 45 seconds
Sample interval was 30m 45s 12546us

C#      | Ratio  | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
     C0 |  97.6% |          |   600 MHz |   0.5% |
     C1 |   1.0% | 1587.1ms |   550 MHz |   0.0% |
     C2 |   0.0% |    6.0ms |   500 MHz |   0.3% |
     C3 |   0.2% |  409.7ms |   250 MHz |  99.2% |
     C4 |   1.2% | 1508.3ms | 

IRQ#    | Activity   | Type           | Name
--------+------------+----------------+---------------------------
     56 |        229 |           INTC | i2c_omap
     57 |         68 |           INTC | i2c_omap
     37 |         67 |           INTC | gp
     11 |         43 |           INTC | prcm
     86 |         16 |           INTC | mmc1
     12 |          5 |           INTC | DMA
    225 |          2 |           GPIO | omap2-onenand

PID#    | Activity   | Name           | Function Entry (Expire)
--------+------------+----------------+---------------------------
      0 |         40 |  <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
     37 |         16D|            awk | cpufreq_governor_dbs (delayed_work_timer_fn)
    699 |         14 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
    699 |          5 |      bme_RX-51 | schedule_timeout (process_timeout)
      0 |          5 |  <kernel core> | hrtimer_start (tick_sched_timer)
      1 |          4D|  <kernel core> | queue_delayed_work (delayed_work_timer_fn)
    663 |          4 |           dsme | __enqueue_rt_entity (sched_rt_period_timer)
    601 |          3 |          mmcqd | queue_delayed_work (delayed_work_timer_fn)
    699 |          3 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    663 |          3 |           dsme | do_nanosleep (hrtimer_wakeup)
   1022 |          2 |        signond | futex_wait (hrtimer_wakeup)
     14 |          1 |        pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
     14 |          1 |        pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
     29 |          1 |          mount | setup_wb_timer (wb_timer_fn)
     14 |          1 |        pdflush | blk_plug_device (blk_unplug_timeout)
    711 |          1 |    dbus-daemon | queue_delayed_work (delayed_work_timer_fn)
    765 |          1 |            mce | schedule_hrtimeout_range (hrtimer_wakeup)
   1355 |          1 |       browserd | futex_wait (hrtimer_wakeup)
   1022 |          1 |        signond | schedule_hrtimeout_range (hrtimer_wakeup)
    977 |          1 |          iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
    672 |          1 |        syslogd | hrtimer_start (it_real_fn)
   1310 |          1 |tracker-indexer | schedule_hrtimeout_range (hrtimer_wakeup)
   1402 |          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: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    per |OFF:   0%|RET:  57%|INA:   0%| ON:  42%| 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:   0%|RET:   0%|INA:   0%| ON: 100%| now:(ON)
   neon |OFF:  50%|RET:   6%|INA:   0%| ON:  42%| now:(ON)
    mpu |OFF:  50%|RET:   6%|INA:   0%| ON:  42%| 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 |         UART2 |
  core3 |       USBTLL
   wkup |          GPT1 |       32KSYNC |         GPIO1 
        |          WDT1 |
  ckgen |          CORE |          PERI |           96M 
        |           48M |           12M |           54M 
        |      EMU_CORE |
    per |         GPIO2 |         GPIO3 |         GPIO4 
        |         GPIO5 |         GPIO6 |

Total wakeups   541,  12.0/s | IRQ  430,   9.6/s | Timers  111,   2.5/s
HW wakeups       43,   1.0/s |     Real gp_timers expired   67,   1.5/s
Thank you.
Attached Files
File Type: gz dmesg_2014071501.txt.gz (5.2 KB, 61 views)
 

The Following User Says Thank You to codelad For This Useful Post:
Reply
Page 2 of 6 1 2 34 Last »

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 01:17.

Contact Us - Home - Archive - Top