Re: [Announce] kernel-power unstable v49
 

I confirm this problem and there are at least 2 threads about this kernel power problem:
http://talk.maemo.org/showthread.php?t=71127
http://talk.maemo.org/showthread.php?t=72002

This is an age old problem.

Re: [Announce] kernel-power unstable v49
 

I wonder if this is related, as always, to a too undervolted/overclocked/smartreflexed thingy...
Or also, battery patch with a too much downed idle profile

Re: [Announce] kernel-power unstable v49
 

Just to be sure: It is not a problem of the phone restarting, it is a problem that the phone, when we try to restart, will give up at nokia logo and turn off.

KP46 is from far before battery/speed patch, so no.
Undervoltage, Overclocking and Smartreflex are easy to rule out, all is needed is to try on default, same thing happens since forever(at least in my case).

Also, I think that the voltages/clocks are set after the phone starts, which needs the phone to successfully start, which is the problem: The phone doesn't restart. It will give up at nokia logo, will turn off the screen and then the phone itself.

It does not happen with the stock kernel.

Re: [Announce] kernel-power unstable v49
 

I tried:

"sudo reboot"

"root
reboot"

and "sudo gainroot
reboot"

With both keyboard open end closed and with stock kernel, kp48 & kp 49, i did this several time and trying different command but it always did reboot properly...

Sorry but i don't seems to be able to reproduce this issue...

Maybe if you use multiboot, you can try this:
http://talk.maemo.org/showthread.php?t=67866

i use this.

Re: [Announce] kernel-power unstable v49
 

Oh god, please... Few posts ago Temporal clarified, what kind of reboot problem we're talking about (I admit, I should foresee, that most people won't read last page, and starting posting irrelevant sh|t, when asked about "reboot problem"), and we're still getting asnwers like "I got my device running for 235462365127654237 years, and I got no reboots"?

Please, read at least last 2-3 pages, before replying *facepalm*.

/Estel

Ps.

It's quite strange problem, cause - in my case - it appeared with kp48. Still, some people get it at much lower version, or haven't get it at all.

I wonder if it is really kernel related - still, I have no idea what may be causing this. I don't use any s0-called "miracle" speed/battery sh|t patches.

/Estel

Re: [Announce] kernel-power unstable v49
 

I use same kernel as last time (kp49 from 2011-10-06) and i confirm that usb-networking problem still happens (it crashed my phone today during downloading files for updates over USB)
when I will upgrade to latest version of kp49 I will check again.

Re: [Announce] kernel-power unstable v49
 

Add me to the ones, who would love to have this issue fixed. Or at least directed into some kind of "I know whats happening".
Struggling with this (reboot not reliable, whatever kind of command line is used), since installed KP months/years ago.
But hey, its just annoying, but not really a fatal error :(

Re: [Announce] kernel-power unstable v49
 

It's not the same issue as the issue where the device won't finish booting or will enter into a (possibly temporary) reboot loop if you try to power it up with the charger plugged, is it?

Re: [Announce] kernel-power unstable v49
 

My thought exactly - I at least have had both forms of the issue. But correlation and common cause are not guaranteed.

What I noticed was that in both cases the failure was not inevitable, though it did occur the majority of times.

Re: [Announce] kernel-power unstable v49
 

Indeed. Reboot doesn't restart on either of my units, and nor will they get to the white dots 90% of the time with the charger plugged in (usually noticed after a crash.) Removing the charger enables the boot to succeed.

Re: [Announce] kernel-power unstable v49
 

There is a progress on SR bug - I found it. Will need a little more time to tweak SR in such a way that it will be stable on all devices up to 900/600. Hopefully tomorrow will upload a link to fixed kernel binaries, so those who want to test it. Once stability is confirmed I will send a new patch to pali.

Sorry that it took a little bit longer than expected.

Re: [Announce] kernel-power unstable v49
 

No need to say sorry. It's your free time so we (I think that I can say in the name of all of us) are happy that you do it ;)
Thank you!

Re: [Announce] kernel-power unstable v49
 

I also confirm, that bug with rebooting also occur when turning device on, plugged to charger.

It's impossible to turn device with charger plugged in - need to remove plug, turn on past Nokia logo, and plug charger back.

Sorry for writing in bold, but - while indeed, it is not fatal error - may mean something more serious is going wrong.

Any comment on it from kp devs? Even the smallest one, "we don't have f**** clue what is going on"?

/Estel

// Edit

0_o, please read this small, 4 pages thread...

http://talk.maemo.org/showthread.php?t=71127

Voodoo programing?

Re: [Announce] kernel-power unstable v49
 

Amusing stuff - face north, stand on one leg and maintain an angle of 45.46 degrees on your n900 and it will reboot..... :)

Perhaps further comments on this topic should be carried there, as the thread has both specificity and precedence?

Re: [Announce] kernel-power unstable v49
 

I had the same thing last year. For me it happened couple of times after a re-flash if I imported the application catalog from a backup. So instead of importing the apps, I installed them manually with fapman and the problem was gone. Now when I re-flash I never import the application list.

Re: [Announce] kernel-power unstable v49
 

Great news. I'll be looking for the link.

Re: [Announce] kernel-power unstable v49
 

how is the order of the installation files of kernel power v49? thanks a lot :D

Re: [Announce] kernel-power unstable v49
 

The problem of device shutting down on Nokia logo after reboot, is now top 1 "mystical" Maemo/N900 thing on my personal list.. Below is a short X-Archive summarize:

1. It seems, that people started encountering this UFO around kernel 42, but other get it with 46, 47, 48 - like me - or, 49.

2. Removing KP always fix the problem, but it re-appears after installing KP again.

3. The problem seems to be not 100% reproducible - it happens most of the times, but not always. Some claim, that holding N900 in "tablet" position (just like the backcover "leg" is used) make chances of successful reboot bigger. Personally, I can't imagine how such a thing may happen - accelerometer isn't initiated at such early stage of boot (fixme?) - but, this claim comes from trusted members, like handaxe

4. If device is able to reboot successfully once - for example, by means of voodoo from point 3 - it can be reboot many times in line without problem. Then, if You do some other things on it/leave it turned off for a while/etc, problem returns. So, it seems, that some unspecific condition change trigger problem again.

5. The same happens, when You try to turn device on while plugged to charger and charging. In fact, device while charging is ion "act-dead" mode, so, turning it on, mean - in fact - reboot. This is possibly the most painful appearance of problem (affecting USB port wear&tear), cause to solve this, one need to unplug, turn device on, and plug again, preferably on 5 dots (any time after Nokia logo will do).

6. It seems, that reflashing and reinstall same packages as before, result in solving the problem (at least, until it re-appears one day ;) ). Ho ever, reflashing, and restoring rootfs/optfs backup - via backupmenu - brings the problem along restored backup. So, it's definitely something rootfs/optfs related (I wonder, if restoring only rootfs would help to sandbox the issue? I know it's way for broken packages, but just testing reboot, and reflashing + restoring backup proper way, might give us idea if it's something on rootfs or optfs)

7. It's still unsure, if R&D mode affect this problem. This one may be verified easily - one just need to turn R&D on, and check. Mentalist Traceur's CLI R&D flag changer, or qwerty's GUI R&D changer, may help here, if someone don't want to use flasher method.

Any clues/idea? I think restoring only rootfs may be a good start, ho ever, even if we know if it is caused by something in rootfs or optfs, it's still searching a drop of water in baltic sea.

/Estel

Re: [Announce] kernel-power unstable v49
 

here are KP49 .debs with SR (hopefully) working for range 125-900 MHz. I would appreciate if brave souls test it and comment.

There is an additional value in /sys/power called sr_vdd1_voltage. It contains current OPP voltage as calculated by SR. One can compare it and report what are the differences between what SR thinks is optimal and what he thinks is for a particular frequency. I need that info to check if current SR settings in kernel are optimal.

Any additional feedback is welcome too.

Re: [Announce] kernel-power unstable v49
 

hi freemangordon..

i am using ur kernel power...no reboots till now and videos are playing well till now with dsp profile vdd1=1 "d vdd2=1 ... 250-850 Mhz...

thanks a lot genius...

cheers...!

Re: [Announce] kernel-power unstable v49
 

I don't know the solution, but you may find it interesting that I had this same kind of problem prior to PR1.1 using stock Nokia kernel. If I tried to reboot device while plugged into charger (either soft reboot or shutdown -> power on) , it would hang and the only remedy was to remove the battery! Of course, back in those days, the N900 would reboot itself randomly for various reasons, so that was a big problem for me. :)

I haven't tried kp49 yet so I can't comment on the present problem specifically.

Re: [Announce] kernel-power unstable v49
 

@freemangordon
i cant download from your link. can you please upload it to mediafire??
thank you for all the hard work.

Re: [Announce] kernel-power unstable v49
 

@freemangordon

Wow, You calculated SR for 900 mhz? That's incredibly great news! As I understand it, the kp49 You linked is the latest, i.e contain not only updated SR, but all changes like 720p recording etc? I'll test it gladly, after doing full backup.

Hm, in case of "mysterious" bug, one can always turn device off (and on, after that) without any problems. Only rebooting (also automatic reboot, when You turn device on during charging - it's technically going out from act-dead, and booting normally, yep?) cause problems, so, this *might* be unrelated.

Still, it's to mysterious at all, to be sure - so, worth keeping Your note in mind. Thanks.

/Estel

Re: [Announce] kernel-power unstable v49
 

does smart reflex vdd1 saves battery under continue usage ? or only on stand by ?

Re: [Announce] kernel-power unstable v49
 

I don't know what is going on, but ever since I updated to KP49, my N900 can't catch a GPS signal, even with AGPS. N82 is done in 3 seconds.

Re: [Announce] kernel-power unstable v49
 

Patlak, may be unrelated, because problems with supl.nokia.com and supl.google.com seems to appear and disappear randomly. When I tried it few days ago, I was able to catch signal only using 3G (2G wasn't able to catch signal), so I suspect that only cell based assistance was available.

/Estel

Re: [Announce] kernel-power unstable v49
 

@freemangordon..
after using ur sr enabled kp for 12 hrs...
not a single reboot even at 900 MHz but i don't know if this is happening with me only, at some instances mediaplayer plays a video well but at other times the same video while playing normally is suddenly interrupted and a notice pops up saying "unable to play media format unsupported" and then none of the videos are playable....i have to reboot to play videos again...
i am confused...
thanku...

Re: [Announce] kernel-power unstable v49
 

Hm, in case of "mysterious" bug, one can always turn device off (and on, after that) without any problems. Only rebooting (also automatic reboot, when You turn device on during charging - it's technically going out from act-dead, and booting normally, yep?) cause problems, so, this *might* be unrelated.

Still, it's to mysterious at all, to be sure - so, worth keeping Your note in mind. Thanks.

/Estel[/QUOTE]

hello dear,
i have also been facing this problem long time ago...it was even with kp48...but with power 49 sometimes reboot is proper while sometimes phone is unable to go beyond nokia logo...i have to boot it again..

Re: [Announce] kernel-power unstable v49
 

@ Pali / freemangordon

Don't you guys think the kp49 (without SR) is stable enough to be added to repositories? and leave SR patches and other new stuff for kp50 and up, because i feel we'll be stuck in kp49 and most of community would not benefit from the huge improvements it already offers since not all members will follow the thread and update kp49 time to time IMHO.


nkirk

Re: [Announce] kernel-power unstable v49
 

multiboot img please?

Re: [Announce] kernel-power unstable v49
 

@nkirk - I think SR is very close to if not stable, a week or so should not matter.

@knobby - try to lower DSP frequency for 805,850 and 900 from 600 to 430 to see if that helps. Or limit max frequency to 850 or 805.

Re: [Announce] kernel-power unstable v49
 

Uploaded on the same place.

Re: [Announce] kernel-power unstable v49
 

It is the whole range 125-900 which is recalculated. I have no idea why, but with stock calibrations voltages were too high, i.e. for 250 SR voltage was about 28-30 while with re-calculated calibrations it stays 21-22. The same for other frequencies. I also changed lowest voltage limit from 20 to 18. That should affect 125MHz, and will (hopefully) have visible effect on battery life if one sets lower frequency to be 125. If someone give me a hint on what is the lowest voltage for 125 (without SR) I can lower that limit further. Also I would like to have others voltages for 250 (manually undervolted) to tweak SR driver further.

And yes, uploaded debs are based on latest KP with only SR driver modified.

Re: [Announce] kernel-power unstable v49
 

I have used 125:20,90 setting for a long time. Without and with SR enabled (SR last 6 months) and device has been stable.

I use Alarmed to put phone into power safe mode during night times (23:00 - 06:45). Enable freqs are 125MHz and 500MHz. This seems to be a bit more power saving mode than 250MHz & 500MHz or single 250MHz or 500MHz when CPU is awake, idle = 0MHz always.

I could try even lower voltages for 125MHz and check if it is still stable.

I have a general question about OMAP PM:
Is it so that DVFS sets OPP according to CPU power needs (when more calculation power is needed, then frequency will be increased also voltage) and SmartReflex tries to autocompensate VDD1 and VDD2 voltages around used OPP (i.e fine tuning based on different paramenters).

- VDD1 domain control MPU&IVA (ARM, DSP, etc..)
- VDD2 domain control on-chip interconnects

Is it possible to see used (current) voltage values, when SR's are enabled?
/etc/power/ -folder files are not showing any changes w/wo SR.

Uptime ~14h with latest KP without any problems.

EDIT: Now testing 125:18,90 setting and N900 seems to work OK (this editing done with that setting and using single 125M freq)

Re: [Announce] kernel-power unstable v49
 

Why would problems with supl.nokia.com affect N900 only? As I said, N82 has no issues.

Re: [Announce] kernel-power unstable v49
 

@Gusse - sr_vdd1_voltage reflects current VDD1 voltage when SR is enabled, but for 125 it won't go bellow 18 because of hard limit.

Re: [Announce] kernel-power unstable v49
 

sr_vdd1_voltage is showing VDD1 voltage OK. For some reason SR was not enabled when I checked values, my misstake.

18 seems to be OK value at 125M and when SR is enabled voltage seems to stay the same value.

Re: [Announce] kernel-power unstable v49
 

@freemangordon

Hey, I don't get one thing. Before re-calibration, device with 900 mhz as max limit and SR enabled, would instantly turn off - it was always told, that this behavior was due to voltage set too low. Now You're telling us, that stock calibration turns voltage too high. Was that just "urban legend", and in fact, voltage was set too high?

Also, aren't You (due to new re-calibrated values) undervolting too much? I quite don't get idea, why do You want to know "lowest" possible values for some frequencies - on other devices, such values may be set too low. We don't want slow filesystem corruption due to "invisible" over-undervolting (situation, when it doesn't result in reboots, but operations are performed with errors, occasionally, due to voltage set too low), don't we?

Of course, it's quite possible that I've misunderstood something, in such case, just correct me please. And, again, thanks for Your awesome work!

@patlak
Some time ago, it was suggested, that Nokia do "something" to drop support for some devices. I.E, at the same time, N900 was able to ping Nokia supl servers, but wasn't able to get satellite data. Meanwhile, newest devices were able to ping and receive data. Also, on exact same time, supl.google.com was working for both N900 and other device.

Some claim, that this Nokians practice was seen before, with other devices. Ho ever, I'm not sure if all of this isn't just guesswork error, so I'm just relaying opinions from (many) threads about supl.nokia.com problems.

The "ultimate" answer for You, would be to try supl.google.com as server - if You get satellite fix very quickly with it, there is no (technical) reason on N900 side, to not get it from supl.nokia.com.

/Estel

Re: [Announce] kernel-power unstable v49
 

@Estel - ok, I will try to explain the SR situation AIUI

From gathered efuse values (posted here by several users and from my devices) it is pretty obvious that there are only two OPPs which have values calibrated - 125MHz and 250MHz. The other frequencies (500,550 and 600) have one and the same values for all the devices so far. Which does not look like there was any calibration, just a random numbers someone (TI most probably) has decided will be OK for all.

The problem is (and that is why I am saying voltages are too high) that based on that calibration values SR puts voltage for 250 MHz to be around 28-30 on my two devices and on another one i borrow. In the same time those devices work without any issue with a voltages around 21-23 for the same 250 MHz frequency.

So what I have done?

First - 125 MHz and 250 MHz calibration is lowered in such a way that SR calculates voltage to be around 21 - 23 for 250 MHz( it still depends on initial calibration, so "weak" device will get higher voltage). The values for higher OPPs are calculated based on 250MHz re-calculated calibration value, so again "weak" device will receive more juice.

The re-calculation is done in such a way that value for OPP(n) is based on value for OPP(n-1) plus a constant. And if DSP is overclocked an additional voltage is applied too(12.5 mV for 520MHz and 25mV for 600 MHz). Of course without having documentation for SmartReflex I cannot be sure whether re-calibrated values are optimal, but so far it seems that they are at least close to. And one of the reasons I ask for SR calculated voltages for different OPPs is that when we have them one can compare his/her manually undervolted profile with SR undervolted thus checking if they are similar/equal.

The last thing is 125MHz - I have an impression that we can run the device with voltage around 14-16 on that frequency, increasing battery life by several hours. But now hardcoded lower limit for voltage is 18 (was 20). That is why I want as many as possible people to test 125 MHz with values in range 14-18, so I can further lower the hardcoded limit.

BTW there is still a minor issue in SR driver - every time a frequency is switched SR starts AVS from highest possible voltage, which is inefficient. For KP50 I plan to optimize that too. And I will check VDD2 SR too, because if VDD1 calibration is too high it is possible that VDD2 is the same.

Re too much undervolting - TBH creeping filesystem corruption seems like an urban myth to me. If your device is undervolted too much DSP will cry loudly in an instant. Could be that I am wrong of course :) . Anyway, as now I (almost) understand how SR works I can easy fix/tweak any issue that could appear.

EDIT:
There were no calibration values above 600MHz. I such case for frequencies above 600MHz calibration for 600MHz was used. Too low of course. And that is another proof that stock calibrations were set too high - most devices were running 805MHz with calibration for 600MHz.

Re: [Announce] kernel-power unstable v49
 

Could you try lowering it further, i.e. 17-16-... . Sorry that I am not doing it myself here, just need to rest from kernel-development for a while ;)