Reboot loop / apt-get upgrade / 20 Jun 2006 firmware
 

Hi,

After a look to forum, I solve my mistral-beta problem
and add new repository to my list,
after this I application list give 1 update: ok, no problem.

But "apt-get install ssh" show me 19 applications to upgrade,
apt-get upgrade propose to begin with 17 applications,
I said yes and after a 3mn of download my 770 shutdown ...


Now I'm in infinite boot loop mode with about 30s time usable ...

Since I have enough time to copy a script from mmc card
and start it, I do a ps -ef > /media/mmc1/result.txt

this is result:

PID Uid VmSize Stat Command
1 root 484 S init [2]
2 root SWN [ksoftirqd/0]
3 root SW [watchdog/0]
4 root SW< [events/0]
5 root SW< [khelper]
6 root SW< [kthread]
22 root SW< [kblockd/0]
36 root SW< [omap_uwire]
42 root SW< [khubd]
93 root SW [pdflush]
94 root DW [pdflush]
96 root SW< [aio/0]
95 root SW [kswapd0]
171 root SW< [cqueue/0]
172 root SW< [kseriod]
205 root SW [mtdblockd]
239 root SW< [krfcommd]
248 root SW [mmcqd]
278 root 540 R < dsme -d -l syslog -v 4 -p /usr/lib/dsme/libst
283 root 540 S dsme -d -l syslog -v 4 -p /usr/lib/dsme/libst
284 root 540 S dsme -d -l syslog -v 4 -p /usr/lib/dsme/libst
285 root 312 S /usr/bin/bme
333 root DWN [jffs2_gcd_mtd4]
352 root 416 S < /sbin/udevd --daemon
565 nobody 652 S < /usr/sbin/dnsmasq -k -i lo -a 127.0.0.1 -z
579 messageb 1320 S < /usr/bin/dbus-daemon --system
584 root 1492 S < /sbin/mce
588 messageb 1468 D /usr/lib/gconf2/gconfd-2
594 root 3248 S < /usr/bin/Xomap -mouse /dev/input/mouse0 -mous
618 user 236 S < /usr/sbin/temp-reaper
621 user 1128 S < /usr/bin/dbus-daemon --session
625 user 2628 S < /usr/lib/sapwood/sapwood-server
629 user 2068 S < /usr/bin/matchbox-window-manager -theme defau
640 root 1112 S /usr/sbin/dsp_dld -p --disable-restart -c /li
659 root 1128 S < /usr/sbin/hcid -n
661 root 492 S < /usr/sbin/sdpd -n
690 root 1016 S < /usr/bin/bme-dbus-proxy -N
707 root 1364 S /usr/bin/osso_hss
712 root 632 S /usr/bin/esd
733 root 1220 S < /usr/bin/btcond -l
751 root 1500 S < /usr/sbin/ke-recv
757 root 1288 S < /usr/sbin/wlancond
760 nobody 1056 S < /usr/bin/btpin -l
763 root 1484 S < /usr/sbin/icd
784 user 2112 S /usr/libexec/dbus-vfs-daemon
786 user 1844 S < /usr/bin/maemo-launcher --daemon --quiet
804 user 2112 S /usr/libexec/dbus-vfs-daemon
805 user 2112 S /usr/libexec/dbus-vfs-daemon
838 user 356 S < /usr/bin/maemo_af_desktop
839 user 8748 S < /usr/bin/maemo_af_desktop
845 user 356 S < /usr/bin/osso-connectivity-ui-conndlgs
846 user 4072 S < /usr/bin/osso-connectivity-ui-conndlgs
849 user 356 S /usr/bin/hildon-input-method
851 user 7132 S /usr/bin/osso-xterm
854 user 6172 S /usr/bin/hildon-input-method
857 user 600 S < /usr/bin/clipboard-manager
861 root 1384 S /usr/bin/ias
888 systemui 5040 S < /usr/bin/systemui
889 user 612 S gnome-pty-helper
892 user 708 S sh
893 user 7132 S /usr/bin/osso-xterm
894 user 7132 S /usr/bin/osso-xterm
912 root 1740 S /usr/bin/osso_alarm
919 root 68 S /usr/bin/retutime -s
920 user Z < [osso-media-serv]
921 user 528 S /bin/sh ./t
922 user 620 R ps -ef



Is'it some kill I can do to stop the expected shutdown ?

or someone can send me a script I can start to see mode deeply what arrive ...


without any information, I will flash back to original final 2006,
but it's also time to see what arrive ...


Any idea ???

Thank you,
Laurent.

Hi,

Someone can post his own "ps -ef" result from a fresh booted 770 that I can compare ?
(from 30 Jun 2006)


Thanks,
Laurent.

I had just the same problem i couple of days ago...
I just reflashed the latest firmware to solve the problem. Thats the price to pay sometimes when living on the bleeding edge. :)

Yea ... I know ... but I expect to be more able to trace into the problem :)

Thank you for your list, but that didn't help me,


But I have very very big problem with reflash I didn't expect,
solution was:
export USB_DEVFS_PATH=/dev/bus/usb

I see solution http://l3x.net/imwiki/Wiki.jsp?page=Main

I will a make a post with better explanation.

Good day,
Laurent.

I had this problem yesterday.
I believe it is the maemo-launcher update that causes the problem, mainly because it cannot upgrade properly (as the table reboots when it senses maemo-launcher not running).

flash your 770 like so:
$./flasher-2.0 --set-rd-flags=no-lifeguard-reset

That will keep the 770 from rebooting when something critical has crashed or has been shut down for an upgrade.
You can then use --clear-rd-flags=no-lifeguard-reset to put it back to normal, but I havent at this time.

Now I have more information and I can reproduce my crash/reboot :(

- I flash with 30 June
- add repository maemo-hackers.org/apt mistral main (to install xterm)
- install xterm
- activate R&D mode (to modify /usr/bin/gainroot)
- disable R&D mode
- add some repository
- apt-get update
- apt-get upgrade
upgrade propose 14 update: I said Yes, system crash with libtelepathy install.

this my repository list I copy from some post: (I don't remeber where)

TAKE CARE OR YOU WILL CRASH YOUR SYSTEM, YOU HAVE BEEN WARNED !!!

deb http://repository.maemo.org/contrib/ mistral free non-free
deb http://repository.maemo.org/ mistral free non-free
deb http://only.mawhrin.net/fbreader/maemo/ mistral user
deb http://www.kernelconcepts.de/~fuchs/nokia770/ex_2006/ ./
deb http://www.mulliner.org/nokia770/repository/ maemo2 free
deb http://maemo.org.br/platform/apt/ python python
deb http://zeus.rm-fr.net/~skyhusker/maemo/ mistral user
deb http://www.oakcourt.dyndns.org/maemo/ ./


Thank you for your tips hallgreng,
I will make a new try with it and see if I can have libtelepathy version


asap,
Laurent.

Please post me the output of
$dpkg -l | grep telepathy

my output from a working tablet is as follows:
If you have an earlier version, then it should be upgradable (albeit with a little hassle and that flasher flag).

I am beginning to wonder if I should apt-get from the command line at all any more. I am a hardcore Debian user, so I prefer to use apt command-line tools to do updates, but I have run into problems with maemo-launcher before, apparently libtelepathy (that was in the list of upgraded packages prior to my problems yesterday), and I needed to enable development flags in the firmware to fix them.
I am not against doing heavy lifting, but the 770 is one of those devices that I like to "just work" and not have to fool around with it to do something.

Next ...
 

This is my libtelepathy version before I try to upgrade:
apt-get update & apt-get upgrade before I add my previous repository list
apt-get update & apt-get upgrade after I add my previous repository list

This is update downloaded:
Get:12 http://repository.maemo.org mistral/free libtelepathy 0.0.14-0osso1maemo1 [20.8kB]


and still crash :( :( :(

But reboot looks stable :) and telepathy is updated to:

Final:

Now system looks good now :)
but I can't go out from R&D --set-rd-flags=no-lifeguard-reset mode
cause reboot loop arrive :( :( :(


hallgreng: did you test to go out from R&D to see what appends ?
Cause it's not just an install point problem, it's stability system problem now I guess ...


time for a bug report ?


Good day,
Laurent.

Looks like your situation was the same as mine, I had apt asking about maemo-launcher during upgrade, though I opted to keep the original config file.

I did not disable R&D mode nor have i cleared the no-lifeguard-reset flag.
I may do that tomorrow if necessary to test.

I looked through dmesg and around the end of bootup and this is all that looks interesting:
Namely the "aic23 powering up and down (I dont know what this is or if it is normal behavior)
and the DMA timeout.
Does anyone have any knowledge of these two things? Due to the nature of the device, logs are sparce. dmesg is the best I can think of to gather information in this case...

same issue here
 

I did the exact same steps.. got stuck in the reboot loop once I'd installed (and forced the rest of the install to finish). Popped the battery, rd mode to no lifeguard, and the reboot cycle goes away.. and returns again if I take out of R&D/no lifeguard.

I don't know if it's a symptom of R&D mode ( my understanding is that it doesn't cause any performace differences), or maybe I'm just imagining things.. but the overall system suddenly feels speedier since doing this minor upgrade.