[maemo-developers] N800 shuts down after 364 seconds in initfs
From: Frantisek Dufka dufkaf at seznam.czDate: Tue Sep 18 23:10:57 EEST 2007
- Previous message: Maemo 4.0 beta SDK installer & Connection reset by peer
- Next message: Onboard compilers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello, as already mentioned here I have implemented USB networking recovery mode in bootmenu. It works fine with 770 but unfortunately N800 doesn't like staying in initfs too long. After few tests it looks like the device shuts down exactly 6 minutes and 4 seconds after linux kernel is booted. Possibly this is exactly 6 minutes after dsme or bme is started. Here is kernel log. I tried it few times and the timing is always the same. <4>[ 3.872497] VFS: Mounted root (jffs2 filesystem). <6>[ 3.872833] Freeing init memory: 92K <4>[ 8.175262] ether gadget: using random self ethernet address <4>[ 8.175384] ether gadget: using random host ethernet address <6>[ 8.192687] usb0: Ethernet Gadget, version: May Day 2005 <6>[ 8.192779] usb0: using musb_hdrc, OUT ep1out IN ep1in STATUS ep2in <6>[ 8.192840] usb0: MAC c2:5c:98:eb:81:21 <6>[ 8.192901] usb0: HOST MAC 66:33:7e:ee:63:da <6>[ 8.192932] usb0: RNDIS ready <4>[ 8.195648] drivers/usb/musb/tusb6010.c musb_platform_enable: dma not reactivated <7>[ 16.637207] musb_stage2_irq 628: SUSPEND, devctl 99 <7>[ 17.777954] musb_stage0_irq 530: BUS RESET <7>[ 17.782806] musb_stage0_irq 530: BUS RESET <7>[ 18.019683] musb_hdrc periph: enabled ep2in for int IN, dma, maxpacket 16 <7>[ 18.019744] musb_hdrc periph: enabled ep1in for bulk IN, dma, maxpacket 512 <7>[ 18.019775] musb_hdrc periph: enabled ep1out for bulk OUT, dma, maxpacket 512 <6>[ 18.019989] usb0: high speed config #2: 100 mA, Ethernet Gadget, using RNDIS <6>[ 364.809326] tahvo: Registering interrupt 7 for device <6>[ 364.809844] retu: Registering interrupt 8 for device <6>[ 364.810760] retu: Registering interrupt 1 for device <6>[ 364.811157] tahvo: Registering interrupt 1 for device Connection to 192.168.11.1 closed by remote host. Connection to 192.168.11.1 closed. Anyone can explain what (dsme? bme?) does it and why? Can I suppress this somehow? My idea is that it is some safety mechanism detecting that device did not boot properly. Please note tahvo and retu interrupts right before shutdown. Can I somehow let the device know that everything is OK? Thanks. Frantisek
- Previous message: Maemo 4.0 beta SDK installer & Connection reset by peer
- Next message: Onboard compilers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]