Closed Bug 1153976 Opened 10 years ago Closed 10 years ago

[Flame] Device is stuck on black screen after flashing on central Tinderbox KK builds

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-master verified)

VERIFIED FIXED
blocking-b2g 2.5+
Tracking Status
b2g-master --- verified

People

(Reporter: pcheng, Unassigned)

References

Details

(Keywords: regression, smoketest, Whiteboard: [3.0-Daily-Testing])

Attachments

(1 file)

Attached file logcat after flashing
On latest Flame KK Central tinderbox (build ID 20150413030135), device fails to enter FTU and is stuck on black screen after full flashing (for shallow flashing it is stuck on the ThunderSoft screen). Repro rate: 3/3 Base image is v18D-1, memory is 319MB. Attaching a logcat.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [3.0-Daily-Testing]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Contact: ychung
Sorry, it is a regression of Bug 1152135. I am going to backout soon :-(
Blocks: 1152135
Mozilla-inbound Regression Window: Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150412023336 Gaia: 3c68964cb9fdba7cf0f6829b7f44562acaf1f1d7 Gecko: 6562cb71c376 Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150412112436 Gaia: 3c68964cb9fdba7cf0f6829b7f44562acaf1f1d7 Gecko: 29d01ad10d0b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Last Working Gaia First Broken Gecko: Issue DOES reproduce Gaia: 3c68964cb9fdba7cf0f6829b7f44562acaf1f1d7 Gecko: 29d01ad10d0b First Broken Gaia Last Working Gecko: Issue does NOT reproduce Gaia: 3c68964cb9fdba7cf0f6829b7f44562acaf1f1d7 Gecko: 6562cb71c376 http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=6562cb71c376&tochange=29d01ad10d0b Caused by bug 1152135
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Contact: ychung
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
This should have been marked as a smoketest blocker immediately.
Keywords: smoketest
Marking fixed due to comment 6
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
This issue is verified fixed on Flame 3.0 The Flame will flash successfully and place the user in the FTU Environmental Variables: Device: Flame 3.0 (319mb)(Kitkat)(Full Flash) Build ID: 20150414072436 Gaia: c8cb0c0ebb8dd1f5c0c9037e38f8e4b237beb77b Gecko: 388f5861dc7d Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Marking this bug as a 2.5 blocker, so it appears on http://mozilla-b2g.github.io/b2g-dashboard/
blocking-b2g: --- → 2.5+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: