topic LONG BOOT DELAY: in i.MX Processors

LONG BOOT DELAY:

kiruthikavarada — Tue, 28 Oct 2014 08:51:48 GMT

I am using IMX6 solo (WAND)h/w.

I am seeing a boot delay before file system is mounted . It tried different options to debug the boot delay but could not trace who is causing the boot delay.

Here are the logs.

2.528285] ak4616_initialize,1566,format:4

[ 2.547397] ak4616_initialize,1573,input:10

[ 2.553682] ak4616_probe, 1609: ak4616 initialize done

[ 2.580780] soc-audio soc-audio.0: snd-soc-dummy-dai <-> 2028000.ssi mapping ok

[ 2.605528] soc-audio soc-audio.0: ak4616-hifi-m.2 <-> 2024000.esai mapping ok

[ 2.624358] soc-audio soc-audio.0: ak4616-hifi-s.0 <-> 2024000.esai mapping ok

[ 2.645855] asix 1-1:1.0 eth0: register 'asix' at usb-ci_hdrc.0-1, ASIX AX88772 USB 2.0 Ethernet, 00:80:c8:3b:31:76

[ 2.663221] soc-audio soc-audio.0: ak4616-hifi-s.1 <-> 2024000.esai mapping ok

[ 2.678321] soc-audio soc-audio.0: ak4616-hifi-m.1 <-> 2024000.esai mapping ok

[ 2.695434] soc-audio soc-audio.0: ak4616-hifi-m.2 <-> 2024000.esai mapping ok

[ 2.704857] soc-audio soc-audio.0: ak4616-hifi-m.1 <-> 2024000.esai mapping ok

[ 2.718623] TCP: cubic registered

[ 2.722859] NET: Registered protocol family 10

[ 2.729454] sit: IPv6 over IPv4 tunneling driver

[ 2.737118] NET: Registered protocol family 17

[ 2.745786] 8021q: 802.1Q VLAN Support v1.8

[ 2.753676] Key type dns_resolver registered

[ 2.760139] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

[ 2.773730] usb 2-1: new low-speed USB device number 2 using ci_hdrc

[ 2.785613] audio clock init finished: esai clk is 24.576MHz

[ 2.796559] snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:00 UTC (0)

[ 2.836688] ALSA device list:

[ 2.839683] #0: rochester-audio-ak4616

[ 2.967924] input: Logitech USB Optical Mouse as /devices/soc0/soc.1/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb2/2-1/2-1:1.0/input/input1

[ 2.980891] hid-generic 0003:046D:C05A.0001: input: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-ci_hdrc.1-1/input0

[ 6.386041] kjournald starting. Commit interval 5 seconds [ 6.391686] EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended

[ 6.403886] EXT3-fs (mmcblk0p2): using internal journal

[ 6.412156] EXT3-fs (mmcblk0p2): recovery complete

[ 6.417000] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode

[ 6.424140] VFS: Mounted root (ext3 filesystem) on device 179:2.

There is boot delay from 2.980891 to 6.386041.

Any clues or suggestions on why this boot delay is.

Thanks,

Re: LONG BOOT DELAY:

igorpadykov — Tue, 28 Oct 2014 11:49:09 GMT

Hi kiruthika

one can try to use more fast class SD/MMC card and check below link

Linux Fast Boot on i.MX6 Sabresd Board

~igor

Re: LONG BOOT DELAY:

kiruthikavarada — Tue, 28 Oct 2014 11:57:23 GMT

Hi Igorpadykov,

My MMC device is high speed device.

The same MMC card does not show any boot delay in other freescale h/w.

I have followed the procedure as mentioned in the link and I am able to reduce the boot time to few secs.

But what is unknown to me is who is causing the boot delay.

~Kirthika

Re: LONG BOOT DELAY:

igorpadykov — Wed, 29 Oct 2014 00:50:39 GMT

Hi kiruthika

I think you can remove some drivers and check experimentally what is causing delay.

Another method, add gpio toggle in various places of program and check with oscilloscope

how program is booting.

~igor

Re: LONG BOOT DELAY:

kiruthikavarada — Wed, 29 Oct 2014 06:46:20 GMT

I noticed that filesystem recovery is taking lot of time (4-6 secs) in IMX6 solo (3.10 kernel)

Any suggestions to reduce the filesystem recovery time.

Re: LONG BOOT DELAY:

igorpadykov — Wed, 29 Oct 2014 07:02:30 GMT

For Wand board specific issues please post on Wand board forum,

for general recommendations please check suggestions below

Linux Fast Boot on i.MX6 Sabresd Board

I am not sure what you meant saying

"same MMC card does not show any boot delay in other freescale h/w."

because there is no Freescale reference design with solo.

And for solo and specific wand board configuration one needs

to compile new image. One image can not be used on different boards.

~igor