maemo.org - Talk - View Single Post - how to troubleshoot boot sequence?

fanoush	2008-02-04 , 09:59
Posts: 2,152 \| Thanked: 1,490 times \| Joined on Jan 2006 @ Czech Republic	#6

Originally Posted by charlie

Is it possible that a process started by a previous init script has hung and caused the watchdog to restart.

Well, yes, sort of, but not exactly. The hardware (Retu) watchdog reboots device only if kernel hangs completely or dsme dies because then nobody pings the watchdog anymore (Retu watchdog timeout is 63 seconds, dsme pings it every ~5 seconds). Then there is dsme with its policy which is the problem here. DSME tries to startup system services and when startup fails or it starts but exits later and it is considered to be critical (by dsme), dsme gives up and switches to runlevel 6. So perhaps something dies here. Maybe the X server?

One can also boot to usb networking recovery mode, log-in, leave the shell running and then try to continue booting and examine system (via ps or whatever) when it hangs somewhere. This needs modification of bootmenu.sh to not to shutdown usb networking. Here is the change (in bold) for binding it to menu key

Code:

while true ; do
        key=`evkey -u -t 100000 /dev/input/${EVNAME}`
        [ "$key" = "$KEY_ESC" ] && break
        [ "$key" = "$KEY_MENU" ] && break
done
${T2S} -c
if [ "$key" = "$KEY_ESC" ] ; then
killall dropbear
killall utelnetd
#sleep 1
ifconfig usb0 down
umount /dev/pts
rmmod g_ether.ko
fi

Root filesystem gets switched for this shell too so don't be confused, it should still work.

Also if system reboots then one also needs modification to stop doing this (/etc/init.d/minireboot).

__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.

Last edited by fanoush; 2008-09-02 at 07:51.

Quote & Reply |

The Following User Says Thank You to fanoush For This Useful Post:
charlie