ANNOUNCE: Diablo-Turbo first beta available - Page 45 - maemo.org

Active Topics

How many of you still use N900 as main phone? (595)
to Community by deutch1976 - 3 days, 8 hrs ago
Big news (7)
to OS2008 / Maemo 4 / Chinook - Diablo by endsormeans - 4 days, 17 hrs ago
Firefox with Leste (8)
to Maemo 7 / Leste by endsormeans - 4 days, 17 hrs ago
more...

Page 45 of 62

Thread Tools

lma	2011-07-14 , 05:41
Posts: 2,802 \| Thanked: 4,491 times \| Joined on Nov 2007	#441

Originally Posted by GeraldKo

Code:

Linux Nokia-N800-43-7 2.6.21-omap1 #2 PREEMPT Sun Mar 13 23:29:39 CET 2011 armv61 unknown

That date looks right, should be the "update 2" dt kernel.

Was I supposed to actually get "noname" as part of the string (and not get "Nokia-N800-43-7"), or did I get to the new Diablo Turbo correctly?

The 43-7 in that string seems a bit surprising since "About Product" from the control panel says "Version: 5.2010.33-1". (5.2008.43-7 was the code for my pre-CSSU OS.)

"Nokia-N800-43-7" is just the hostname. It's set from the contents of /etc/hostname at boot time, and has nothing to do with (and is useless for identifying) the OS version. The CSSU doesn't change it either, that would be evil since some people prefer to set it to something else, or enter it in DHCP server configurations etc.

Quote & Reply |

The Following User Says Thank You to lma For This Useful Post:
GeraldKo

maacruz	2011-07-14 , 07:04
Posts: 1,101 \| Thanked: 1,184 times \| Joined on Aug 2008 @ Spain	#442

Originally Posted by tso

Sorry, either crash or otherwise shut down.

I have sadly never caught it in the act, because my best indicator is that ASUI stops showing the orange long press indicator on the memory use readout.

It happens to me sometimes, but I think it always happened at boot, the times I checked syslog/dmesg showed nothing, and the last time I checked for /dev/ramzswap0 and it was there, and swapon worked just fine.
I guess that for some reason (may be some af-* script) it gets umounted.
I'll move the rc script to start later in the boot process to see if that fixes it.

Quote & Reply |

lma	2011-07-14 , 07:36
Posts: 2,802 \| Thanked: 4,491 times \| Joined on Nov 2007	#443

Here its start order is S20, but I don't reboot very often. I also don't use ASUI (nothing against it, just never got around to trying it) either, not sure if its scripts and ramzez's have any unintended interractions.

Quote & Reply |

auouymous	2011-07-14 , 12:53
Posts: 875 \| Thanked: 918 times \| Joined on Sep 2010	#444

Originally Posted by GeraldKo

Code:

Linux Nokia-N800-43-7 2.6.21-omap1 #2 PREEMPT Sun Mar 13 23:29:39 CET 2011 armv61 unknown

Last DT kernel was 13mar2011 so you have it installed correctly.

Originally Posted by maacruz

I'll move the rc script to start later in the boot process to see if that fixes it.

Let me know the new levels if you change and release.

Originally Posted by lma

Here its start order is S20, but I don't reboot very often. I also don't use ASUI (nothing against it, just never got around to trying it) either, not sure if its scripts and ramzez's have any unintended interractions.

I don't think he meant ASUI was causing problems, just that swap disappeared and no longer showed in ASUI.

Quote & Reply |

	tso	2011-07-14 , 13:43
	Posts: 4,783 \| Thanked: 1,253 times \| Joined on Aug 2007 @ norway	#445

Originally Posted by lma

Does it happen often enough that running syslogd would be useful?

i have no idea.

__________________
Be warned, posts are often line of thoughts at highway speeds...

Quote & Reply |

	tso	2011-07-14 , 13:45
	Posts: 4,783 \| Thanked: 1,253 times \| Joined on Aug 2007 @ norway	#446

Originally Posted by lma

Here its start order is S20, but I don't reboot very often. I also don't use ASUI (nothing against it, just never got around to trying it) either, not sure if its scripts and ramzez's have any unintended interractions.

i am getting a fair number of forced reboots lately. Not sure if it is my battery that is going bad (causing a certain power management system to crash, thanks Nokia), or if it is Opera that is causing something (usually what is running when it happens).

__________________
Be warned, posts are often line of thoughts at highway speeds...

Quote & Reply |

lma	2011-07-14 , 19:07
Posts: 2,802 \| Thanked: 4,491 times \| Joined on Nov 2007	#447

Originally Posted by tso

i am getting a fair number of forced reboots lately.

Do /proc/bootreason & /var/lib/dsme/stats/lifeguard_resets point to anything specific?

Not sure if it is my battery that is going bad (causing a certain power management system to crash, thanks Nokia)

When I had that it was always rebooting within a minute or two of plugging in, and never when not on the charger.

Quote & Reply |

	tso	2011-07-14 , 19:47
	Posts: 4,783 \| Thanked: 1,253 times \| Joined on Aug 2007 @ norway	#448

Will try to remember checking next time i get one.

Edit: had a look just for a lark (and as a reference point).

bootreason shows: 32wd to

when it comes to lifeguard_reset, i am guessing that the line with a * at the end is the one that was the most recent trigger.

if that's the case, then it was /usr/sbin/dsp_dld that cause the most resent reset event.

__________________
Be warned, posts are often line of thoughts at highway speeds...

Last edited by tso; 2011-07-14 at 19:57.

Quote & Reply |

mcow	2011-07-14 , 22:05
Posts: 86 \| Thanked: 8 times \| Joined on May 2010	#449

That's

Code:

/var/lib/dsme/stats/lifeguard_restarts

(not 'resets')

Quote & Reply |

lma	2011-07-14 , 22:52
Posts: 2,802 \| Thanked: 4,491 times \| Joined on Nov 2007	#450

Both can exist, lifeguard_restarts shows processes that died for whatever reason and were restarted by dsme, while lifeguard_resets shows processes that made dsme trigger a complete reboot.