Closed Bug 975451 Opened 10 years ago Closed 10 years ago

[B2G] Unable to boot device after reset, have to remove and remount battery

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bzumwalt, Unassigned)

References

Details

(Keywords: regression, smoketest)

Attachments

(1 file)

Description:
If user resets device on latest 1.4 build, the boot process freezes at the animated Firefox logo screen. User must remove battery and restart device in order to successfully boot.

Repro Steps:
1) Updated Buri to BuildID: 20140221040202
2) Open settings app
3) Navigate to Device Information>More Information
4) Select Reset Phone

Actual:
After resetting, phone freezes on animated Firefox logo screen.

Expected:
User is able to reset phone without incident.

Environmental Variables:
Device: Buri v1.4 Master Mozilla RIL
BuildID: 20140221040202
Gaia: 35365feace970bfc51276428f40a477c9c86b7bb
Gecko: 7010ab83a06e
Version: 30.0a1
Firmware Version: V1.2-device.cfg

Notes:
Repro frequency: 3/3, 100%
Attached file Logcat
Attached Logcat from time of reset
QA Contact: pfield
the key error is:

02-21 17:40:18.859: I/Gecko(137): !! Creating a dummy channel for system.gaiamobile.org (no appInfo)
This issue started to occur on the Buri 1.4 Tinderbox Build ID: 20140220190028

Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140220190028
Gaia: 35365feace970bfc51276428f40a477c9c86b7bb
Gecko: 3328dfb0d932
Version: 30.0a1
Firmware Version: V1.2-device.cfg

Last working Buri 1.4 Tinderbox Build ID: 20140220121329

Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140220121329
Gaia: 35365feace970bfc51276428f40a477c9c86b7bb
Gecko: b89a9d7b4ca0
Version: 30.0a1
Firmware Version: V1.2-device.cfg
That's this changeset from Mozilla Central: https://tbpl.mozilla.org/?rev=3328dfb0d932

The error message in comment 2 is from: http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/app/AppProtocolHandler.cpp#372

And so, my guess is Marco's patches were messing with what I believe to be appinfo objects, so maybe those patches are at fault?
* https://hg.mozilla.org/mozilla-central/rev/dbd05d2e58a5
* https://hg.mozilla.org/mozilla-central/rev/96eaa0f376ab

That's not much of an analysis, and I may be wrong, Marco what do you think?
Flags: needinfo?(mar.castelluccio)
(In reply to Clint Talbert ( :ctalbert ) from comment #5)
> That's this changeset from Mozilla Central:
> https://tbpl.mozilla.org/?rev=3328dfb0d932
> 
> The error message in comment 2 is from:
> http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/app/
> AppProtocolHandler.cpp#372
> 
> And so, my guess is Marco's patches were messing with what I believe to be
> appinfo objects, so maybe those patches are at fault?
> * https://hg.mozilla.org/mozilla-central/rev/dbd05d2e58a5
> * https://hg.mozilla.org/mozilla-central/rev/96eaa0f376ab
> 
> That's not much of an analysis, and I may be wrong, Marco what do you think?

Fabrice I think we suspecting that https://hg.mozilla.org/mozilla-central/rev/96eaa0f376ab caused this. He is verifying a backout right now.
Yep, that's the offending one. I'm backing it out.
Fixed via backout in bug 961282.
Blocks: 961282
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(mar.castelluccio)
Resolution: --- → FIXED
Verified Fixed.
Not experiencing this issue anymore on 2/24 master build - device boots up w/o issues after flashing and resetting. 

BuildID: 20140224040201
Gaia: ffb527b84594396ed611edf0a8a5a130d60a742f
Gecko: 31113754db3b
Version: 30.0a1
v1.2-devices.cfg
Status: RESOLVED → VERIFIED
Did this problem happen only if you reset B2G? If that's the case, I think I know what's the issue in my patch (but I can't test at the moment because I don't have a b2g device).
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: