Reply
Thread Tools
brontide's Avatar
Posts: 868 | Thanked: 474 times | Joined on Oct 2007 @ Capital District, NY, USA
#51
After digging and finding that diablo's arm kernel does not provide reliable futex commands I'm wondering if this is a kernel bug that is being tripped up in specific cases. Modest seems to be doing it in some cases, but I wonder what's causing the meltdown here?

I would ask the simple question... does the problem reoccur when you are in offline mode? I know there should be no difference, but I still keep thinking that it could be a bug in the ICD.

here is the Modest bug for reference.

https://bugs.maemo.org/show_bug.cgi?id=3357
 

The Following User Says Thank You to brontide For This Useful Post:
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#52
Originally Posted by Seb Per View Post
Could it be that this is a learning process to adjust consumption?
No, these batteries don't work like that. (single-stack lion, not multi-stack like a laptop battery)
 
Posts: 23 | Thanked: 1 time | Joined on May 2008
#53
Originally Posted by vinc17 View Post
As usual, my N810 charged during the night and I took it in the morning; it was fully charged. But after about 5 hours, when I took my N810 out of my pocket, it was quite hot and the battery was almost empty! This is surprising as I didn't have any problem the previous days. The CPU indicator was saying the N810 was idle. I only had two open applications:
  • X Terminal (with no running jobs in it). This is not the first time (I use X Terminal very often). So, I doubt this is the problem.
  • Notes (perhaps the first time I let it open under diablo).
Also, no wifi, no bluetooth. Any idea? Could there be a problem with some software taking CPU time only when the tablet is locked?
Could be you have Wifi on search intervals.
 
Posts: 227 | Thanked: 53 times | Joined on Feb 2008 @ Lyon, France
#54
Originally Posted by caped View Post
Could be you have Wifi on search intervals.
What do you mean?
 
Posts: 227 | Thanked: 53 times | Joined on Feb 2008 @ Lyon, France
#55
The battery drain problem occurred once again last evening. I had been logging system information every 15 minutes with "sar -A -u 900 8000" since the afternoon. Here's a summary of what I did:
  • At about 19:45, I plugged out the charger cable.
  • Then I used the N810 a little around 20:15, 21:55 (the N810 was warm, but the battery was full) and 22:15-22:35 (I ran a CPU-intensive task for several seconds).
  • At 22:35, the battery was still full.
  • At 01:50, the battery was almost empty (less than 20 hours when idle, less than 1 hour when in use).
The sar output shows that the N810 was constantly idle (but a very little loaded). So, my battery drain problem does not come from a task that would take much CPU time.
Code:
19:48:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
20:03:24          all      1.22      0.00      1.32      0.00      0.00     97.46
19:48:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
20:03:24            0       113      0.44      0.30      0.19
20:03:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
20:18:24          all      4.69      0.00      1.79      0.15      0.00     93.37
20:03:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
20:18:24            0       118      0.69      0.39      0.26
20:18:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
20:33:24          all      1.98      0.00      0.96      0.02      0.00     97.05
20:18:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
20:33:24            0       116      0.08      0.12      0.16
20:33:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
20:48:24          all      0.07      0.00      0.73      0.00      0.00     99.19
20:33:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
20:48:24            0       116      0.16      0.16      0.16
20:48:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
21:03:24          all      0.10      0.00      0.87      0.00      0.00     99.03
20:48:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
21:03:24            0       116      0.07      0.08      0.10
21:03:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
21:18:24          all      0.08      0.00      0.80      0.00      0.00     99.11
21:03:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
21:18:24            0       116      0.22      0.14      0.10
21:18:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
21:33:24          all      0.15      0.00      0.79      0.00      0.00     99.06
21:18:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
21:33:24            0       116      0.22      0.15      0.10
21:33:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
21:48:24          all      0.08      0.00      0.79      0.00      0.00     99.13
21:33:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
21:48:24            0       116      0.25      0.14      0.10
21:48:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
22:03:24          all      0.49      0.01      1.15      0.00      0.00     98.36
21:48:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
22:03:24            0       116      0.17      0.17      0.14
22:03:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
22:18:24          all      0.36      0.00      1.12      0.00      0.00     98.51
22:03:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
22:18:24            0       116      0.23      0.30      0.22
22:18:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
22:33:24          all     12.16      0.00      1.97      0.18      0.00     85.69
22:18:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
22:33:24            0       118      0.31      0.46      0.36
22:33:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
22:48:24          all      1.35      0.00      0.81      0.00      0.00     97.84
22:33:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
22:48:24            0       118      0.17      0.17      0.22
22:48:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
23:03:24          all      0.09      0.00      0.76      0.00      0.00     99.14
22:48:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
23:03:24            0       118      0.25      0.16      0.16
23:03:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
23:18:24          all      0.08      0.00      0.74      0.00      0.00     99.18
23:03:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
23:18:24            0       118      0.10      0.09      0.09
23:18:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
23:33:24          all      0.16      0.00      0.82      0.00      0.00     99.02
23:18:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
23:33:24            0       118      0.07      0.12      0.09
23:33:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
23:48:24          all      0.07      0.00      0.81      0.00      0.00     99.12
23:33:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
23:48:24            0       118      0.08      0.11      0.09
23:48:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
00:03:24          all      0.19      0.00      0.85      0.00      0.00     98.97
23:48:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
00:03:24            0       118      0.14      0.10      0.09
00:03:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
00:18:24          all      0.08      0.01      0.81      0.00      0.00     99.11
00:03:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
00:18:24            0       118      0.10      0.08      0.08
00:18:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
00:33:24          all      0.09      0.00      1.59      0.00      0.00     98.32
00:18:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
00:33:24            0       118      0.07      0.14      0.10
00:33:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
00:48:24          all      0.08      0.00      1.28      0.00      0.00     98.64
00:33:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
00:48:24            0       118      0.29      0.25      0.17
00:48:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
01:03:24          all      0.10      0.00      1.37      0.00      0.00     98.52
00:48:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
01:03:24            0       118      0.11      0.18      0.17
01:03:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
01:18:24          all      0.08      0.00      1.35      0.00      0.00     98.57
01:03:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
01:18:24            0       118      0.22      0.19      0.18
01:18:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
01:33:24          all      0.11      0.00      1.42      0.00      0.00     98.47
01:18:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
01:33:24            0       118      0.17      0.19      0.18
01:33:24          CPU     %user     %nice   %system   %iowait    %steal     %idle
01:48:24          all      0.08      0.00      1.35      0.00      0.00     98.57
01:33:24      runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15
01:48:24            0       118      0.23      0.15      0.16
 

The Following 2 Users Say Thank You to vinc17 For This Useful Post:
Posts: 833 | Thanked: 124 times | Joined on Nov 2007 @ Based in the USA
#56
Originally Posted by sjgadsby View Post
That incantation is:
  1. Go to InternetTabletTalk main page.
  2. Locate the "Google Custom Search" box under the heading "Search" at the top of the right hand column.
  3. Type likely keywords in the aforementioned search box.
  4. Press "Enter" or tap/click the "Go" button according to your preference.
Thanks for the detailed instructions, I had thought my statement
A simple google search on battery drain in the forums
would be understood as a search such as you described.

I constantly overestimate the audience.
__________________
N810, iGo bt kb, Diablo, 10Gb storage onboard instead of a Thinkpad
OTG w/ unlimited storage!!
Put a penguin in your pocket!!
PLEASE use the Wiki
 
Posts: 269 | Thanked: 4 times | Joined on Feb 2007 @ Finland
#57
ok this is what my friend in Nokia R&D said. No guarantees that 1) he knows exactly what is going on - he s not in N810 specifically 2) I did understand and deliver exactly what he said :-)

He mentioned a few leads:

- As General Antilles said, the battery is single stack so there is no adjustment of power consumption. However there are algorithms to optimize relationship between physical memory, consumption, and performance
- Introducing a new OS causes disruptures in the way the packages are installed because - according to him- the physical memory is not "blank". This can generate a "chaotic" usage of power until things get optimized.
- in stand by mode ( no application running, screen dimmed off) there are still a few things running. Did not say what.
- processor activity, Wifi and BT are the main causes of power drain.
- the battery time indicator in the status bar is not 100% reliable.
- he did not like the "heating up" symptom. Suggests a bug in the new OS that could/should be fixed by an update.

My n810 had again a seizure last evening. a few days in stand-by mode evaporated suddenly in a few hours. Found it in "coma", charged it up . Now showing 10 days, 7 hours.
 
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#58
@vinc: Isn't the interval between sar gathering data too big?
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
 
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#59
Xterm is a known timer offender (i.e. dyntick won't be able to slow the tick speed) - there was a way of fixing this, but I can't remember it off the top of my head. Anyone?
 
Posts: 883 | Thanked: 980 times | Joined on Jul 2007 @ Bern, Switzerland
#60
I have the same issue as the original poster. Since I upgraded to Diablo, battery usage has become inacceptable (but then I'm used to that from my N82....grrrrrrr!). Might be because I backuped/restored before/after the upgrade, and got into lots of troubles with the Application Manager being unable to resolve things, so something might be screwed up.

Will reflash to Chinook and report back, but there IS an issue.
 
Reply

Tags
battery drain


 
Forum Jump


All times are GMT. The time now is 07:07.