859552 - [Inari] Builds are not booting up correctly after flashing

Status: VERIFIED FIXED

(Firefox OS Graveyard :: GonkIntegration, defect)

Description

[Tony Chung [:tchung]]

+++ This bug was initially created as a clone of Bug #839713 +++

Filing a new bug from 839713.   The current builds from http://pvtbuilds.pvt.build.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g18-inari/latest/ does not successfully flash and boot up.   It gets stuck on the movistar splash screen, and adb devices is not recognized.  it never completes the boot and restart after the timestamp step.

We worked around it with fastbooting a new boot image from mwu.

Terminal output:
host-2-112:b2g-distro tchung$ ./flash.sh 
< waiting for device >
erasing 'cache'...
OKAY [  0.370s]
finished. total time: 0.370s
erasing 'userdata'...
OKAY [  0.977s]
finished. total time: 0.977s
sending 'userdata' (4 KB)...
OKAY [  0.004s]
writing 'userdata'...
OKAY [  0.979s]
finished. total time: 0.983s
sending 'boot' (4042 KB)...
OKAY [  0.347s]
writing 'boot'...
OKAY [  0.812s]
finished. total time: 1.160s
sending 'system' (126264 KB)...
OKAY [ 10.654s]
writing 'system'...
OKAY [ 24.476s]
finished. total time: 35.130s
rebooting...

finished. total time: 0.001s
Attempting to set the time on the device
------

Catlee, rail, can you take a look?

Comment 1

[Michael Wu [:mwu]]

Please make sure the boot image has this md5sum: 770cfc2399bdcb68774fd5102a747312

Comment 2

[Michael Wu [:mwu]]

Judging by the file size, it seems like an otoro boot image was included in this build.

Comment 3

[Chris AtLee [:catlee]]

we're using this boot image:
https://hg.mozilla.org/releases/mozilla-b2g18/file/8565e79f6e54/b2g/config/inari/releng-inari.tt#l8

"size": 4139008,
"digest": "6f65553e882316582b944e46c659915a1b907c4a326104cb31d81356330dddacba757e3eafbd282063da0e670c3c5d6b9a0905ab88da84b47848d810c37571cb",

Comment 4

[Michael Wu [:mwu]]

That's identical to otoro:
https://hg.mozilla.org/releases/mozilla-b2g18/file/8565e79f6e54/b2g/config/otoro/releng-otoro.tt

Comment 5

[Chris AtLee [:catlee]]

D'oh, that's my mistake.

The inari-boot.img I have should sha1sum 7bb0cd49abdc4649d93088208e255a0c1535713a and size 4249600. Is that right?

Comment 6

[Michael Wu [:mwu]]

(In reply to Chris AtLee [:catlee] from comment #5)
> D'oh, that's my mistake.
> 
> The inari-boot.img I have should sha1sum
> 7bb0cd49abdc4649d93088208e255a0c1535713a and size 4249600. Is that right?

Yup. Thanks!

Comment 7

[Chris AtLee [:catlee]]

Attachment: fix manifests for inari builds

Comment 8

[Chris AtLee [:catlee]]

Looks like b2g18-v101 is also affected. The same patch would apply there too.

Comment 9

[Alex Keybl [:akeybl]]

Marking as a NPOTB tef+ bug so that this can land to all active branches up to v1.0.1.

Comment 10

[Chris AtLee [:catlee]]

Comment on attachment 734931 [details] [diff] [review]
fix manifests for inari builds

checked in: https://hg.mozilla.org/releases/mozilla-b2g18/rev/08de0253274c

Comment 11

[Chris AtLee [:catlee]]

https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/140c73ac5572

Comment 12

[Chris AtLee [:catlee]]

fixed?

I have no way of testing. Please re-open if we need to make further adjustments.

Comment 13

[Michael Wu [:mwu]]

tchung will be able to verify.

Comment 14

[Tony Chung [:tchung]]

(In reply to Michael Wu [:mwu] from comment #13)
> tchung will be able to verify.

Yep, verified Inari builds flashing and booting correctly on today's build.  

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/423f7851bdb5
Gaia   c614b3f3c956dc1e1adf93cf4cf41511ce75de80
BuildID 20130410070209
Version 18.0