Active Topics

 


Reply
Thread Tools
Posts: 197 | Thanked: 101 times | Joined on Dec 2009 @ Netherlands
#21
That is also what I see.

I also ran a strace when hildon-desktop was more or less idle.

I'll post the strcae logs to the bug report created by carsten
 
Posts: 9 | Thanked: 2 times | Joined on May 2010 @ Prague/Czech Republic
#22
I also see (conky/top) that hildon-desktop+xorg ~ (10-14)%cpu, but it's only when the screen is on ... when I lock the device, ssh to N900 and run top the cpu usage by these two processes is gone, so I doubt that this can cause overnight battery drain ... I can also confirm that it's still present even if I remove all widgets ... didn't tried to remove cpumem applet yet ...

[edit] yes, cpumem applet did it in my case, after removing hildon-desktop ~ 0.x %CPU

[edit1] nope, it's back again ... :-/

Last edited by daniel.gazda; 2010-06-04 at 19:02.
 
Posts: 197 | Thanked: 101 times | Joined on Dec 2009 @ Netherlands
#23
CPU usaga was very low last night, but still battery capacity drops like crazy, And the n900 was in offline mode during the night

 
Posts: 197 | Thanked: 101 times | Joined on Dec 2009 @ Netherlands
#24
I updated bug https://bugs.maemo.org/show_bug.cgi?id=10412 with some new
tests again.

I reflashed firmware and emmc hoping this would fix it. At first It looked like it fixed it but after a short whiel the problems occured again. I did not even install new applications and removed almost everything from the desktops.
 

The Following User Says Thank You to mirakels For This Useful Post:
Posts: 122 | Thanked: 17 times | Joined on Jun 2010
#25
heres my battery graph i seem to get alot of cpu usage during idle and pretty bad battery life

running ideal 500 850
starving 250 850 -2g, wifi disabled, no bluetooth, and still has maasive cpu how do i check whats using it...
Attached Images
 
 
Posts: 2,829 | Thanked: 1,459 times | Joined on Dec 2009 @ Finland
#26
in xterminal you can monitor it with "top" command.
 
Posts: 122 | Thanked: 17 times | Joined on Jun 2010
#27
just checked top and nothing out of the ordinary is consuming anything

basicly what the other user has posted but i dont have corky

Xorg: ~6% (4-12%)
hildon-status-m: ~3% (2-4%)
hildon-desktop: ~2% (1-3%)
 
Posts: 2,829 | Thanked: 1,459 times | Joined on Dec 2009 @ Finland
#28
hmm. Normally when no windows are open (only x term) i have experienced ~3 % cpu from Xorg and all the other processes are under 1 %.

So something is not right with your device if that was on idle.

.edit
So from your processes stuff and that image i would say that your processor never sleeps. Some process constantly wakes it up. Maybe widget or some daemon on background.
 
Posts: 395 | Thanked: 165 times | Joined on May 2010 @ TMO
#29
I don't know, I'm just running the calendar widget, the media player widget, and the conversations widget. No battery issues, Xorg usually hovers around 2~3%
 
Posts: 197 | Thanked: 101 times | Joined on Dec 2009 @ Netherlands
#30
I loggedd into the n900 via the network and left the n900 screen locked.
The in the ssh sessiin I run top. When the systems is idel and running ok (e.g. no battery drain) this is the sort of process list you might expect.
A few kernel processes doing some work every now and then and the top and ssh processes.

Note that all the hildon- xxx processes use 0.0% CPU.

Code:
Mem: 230684K used, 14664K free, 0K shrd, 9408K buff, 67884K cached
CPU:  0.3% usr  3.2% sys  0.0% nice 95.9% idle  0.0% io  0.0% irq  0.3% softirq
Load average: 0.00 0.00 0.00
  PID  PPID USER     STAT   RSS %MEM %CPU COMMAND
   27     2 root     RW       0  0.0  1.1 [kondemand/0]
 2327  2318 user     R      740  0.3  0.9 top 
   10     2 root     SW       0  0.0  0.9 [omap2_mcspi]
 2317  2315 user     S     1356  0.5  0.7 sshd: user@pts/0   
  469     2 root     SW       0  0.0  0.1 [wl12xx]
 1778  1275 user     S    18124  7.3  0.0 /opt/BatteryGraph/bin/BatteryGraph 
 1272  1174 user     S    17892  7.2  0.0 /usr/bin/hildon-home                                                       
 1008   682 root     S <  14888  6.0  0.0 /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1 -nolisten tcp -noreset -s 0 -core 
 1681  1315 user     S    12524  5.0  0.0 /usr/sbin/browserd -s 1681 -n RTComMessagingServer 
 1672  1174 user     S    11496  4.6  0.0 /usr/bin/rtcom-call-ui                                                     
 1275  1174 user     S    10704  4.3  0.0 /usr/bin/hildon-desktop                                                    
 1705  1174 user     S    10400  4.2  0.0 /usr/bin/image-viewer                                                      
 1266  1174 user     S    10376  4.2  0.0 /usr/bin/hildon-status-menu                                                
  682     1 root     S <   9552  3.8  0.0 /sbin/dsme -p /usr/lib/dsme/libstartup.so 
 1714  1174 user     S     8924  3.6  0.0 /usr/bin/modest                                                            
                                                        
 1699  1315 user     S     8748  3.5  0.0 /usr/sbin/browserd -s 1699 -n browserui 
 1677  1174 user     S     7540  3.0  0.0 /usr/bin/rtcom-messaging-ui                                                
 1668  1174 user     S     7328  2.9  0.0 /usr/bin/osso-addressbook
Now when hildon-desktop starts behaving badly you might see something like below. Hildon-desktop will be up in the top list constantly using cpu. At this time you will experience battery drain.

Code:
Mem: 230684K used, 14664K free, 0K shrd, 9408K buff, 67884K cached
CPU:  4.3% usr  3.2% sys  0.0% nice 91.9% idle  0.0% io  0.0% irq  0.3% softirq
Load average: 0.00 0.00 0.00
  PID  PPID USER     STAT   RSS %MEM %CPU COMMAND
 1275  1174 user     S    10704  4.3  3.9 /usr/bin/hildon-desktop 
   27     2 root     RW       0  0.0  1.1 [kondemand/0]
 2327  2318 user     R      740  0.3  0.9 top 
   10     2 root     SW       0  0.0  0.9 [omap2_mcspi]
 2317  2315 user     S     1356  0.5  0.7 sshd: user@pts/0   
  469     2 root     SW       0  0.0  0.1 [wl12xx]
 1778  1275 user     S    18124  7.3  0.0 /opt/BatteryGraph/bin/BatteryGraph 
 1272  1174 user     S    17892  7.2  0.0 /usr/bin/hildon-home                                                       
 1008   682 root     S <  14888  6.0  0.0 /usr/bin/Xorg -logfile /tmp/Xorg.0.log -logverbose 1 -nolisten tcp -noreset -s 0 -core 
 1681  1315 user     S    12524  5.0  0.0 /usr/sbin/browserd -s 1681 -n RTComMessagingServer 
 1672  1174 user     S    11496  4.6  0.0 /usr/bin/rtcom-call-ui                                                     
 1705  1174 user     S    10400  4.2  0.0 /usr/bin/image-viewer                                                      
 1266  1174 user     S    10376  4.2  0.0 /usr/bin/hildon-status-menu                                                
  682     1 root     S <   9552  3.8  0.0 /sbin/dsme -p /usr/lib/dsme/libstartup.so 
 1714  1174 user     S     8924  3.6  0.0 /usr/bin/modest
From the same remote login session I can trace hildon-desktop to see what it is doing.
Install the strace package: apt-get install strace

From above top output I get the process id from the hildon-desktop process. In this case process id 1275 and use that to run strace (you need to be root):

strace -t -tt -p 1275

In the first case you get hardly any output. But when you unlock the n900 screen and play around you will get output (note that your device may be a little bit less responsive). When you lock the screen again strcae output will stop (after a short while)

In the second case you will constantly get strace output like:

1276114986.251678 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=14, events=POLLIN}, {fd=15, events=POLLIN}, {fd=19, events=POLLIN}, {fd=13, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLIN}], 11, 0) = 0 (Timeout)
 
Reply


 
Forum Jump


All times are GMT. The time now is 20:02.