krillin/devel-proposed fails to boot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
Critical
|
kevin gunn | ||
| | mir (Ubuntu) |
Critical
|
Unassigned | ||
| | unity8 (Ubuntu) |
Critical
|
Michael Terry | ||
Bug Description
krillin devel-proposed 212
After completing the wizard and when the edge demo starts the phone reboots spontaneously then enters a boot loop. It shows the unity loading screen and reboots when the shell starts.
Error from unity8.log
Signal caught by Mir, stopping Mir server..
[1443685565.781712] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in queueBuffer): /build/
Dynamic exception type: boost::
All logs attached.
| Jean-Baptiste Lallement (jibel) wrote : | #1 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Critical |
| Changed in canonical-devices-system-image: | |
| importance: | Undecided → Critical |
| assignee: | nobody → kevin gunn (kgunn72) |
| milestone: | none → ww46-2015 |
| Changed in unity8 (Ubuntu): | |
| importance: | Undecided → Critical |
| Alan Griffiths (alan-griffiths) wrote : | #2 |
| Changed in unity8 (Ubuntu): | |
| assignee: | nobody → Michael Terry (mterry) |
| Changed in unity8 (Ubuntu): | |
| status: | New → Confirmed |
| Michael Terry (mterry) wrote : | #3 |
This actually started with image 211 (20150930). Here's the manifest delta:
indicator-bluetooth from 0.0.6+15.
qtdeclarative5-
qtdeclarative5-
qtdeclarative5-
qtmir-android:armhf from 0.4.6+15.
unity-system-
unity8 from 8.11+15.
unity8-common from 8.11+15.
unity8-
webapp-container from 0.23+15.
webbrowser-app from 0.23+15.
qtmir/usc/unity8 are presumably suspicious upgrades.
Though there is an even more recent qtmir upgrade that fixes a crasher (bug 1499388). Hasn't made it into an image yet, but will try to see if that fixes things.
| Michael Terry (mterry) wrote : | #4 |
Yup. Upgrading qtmir & unity8 fixed it. I expect this to be fixed in image 213.
| Changed in unity8 (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in mir (Ubuntu): | |
| status: | New → Fix Released |
| Changed in canonical-devices-system-image: | |
| status: | New → Fix Committed |
| Jean-Baptiste Lallement (jibel) wrote : | #5 |
It is still happening with 213 but slightly different symptom.
The phone doesn't reboot immediately after the wizard but after a couple of minutes of activity. The phone spontaneously reboots without any user action (the device was lying on the desk, screen on) then it enters a boot loop and never boots again to the shell.
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Confirmed |
| Changed in mir (Ubuntu): | |
| status: | Fix Released → Confirmed |
| Changed in unity8 (Ubuntu): | |
| status: | Fix Released → Confirmed |
| Jean-Baptiste Lallement (jibel) wrote : | #6 |
logs for devel-proposed/
| Jean-Baptiste Lallement (jibel) wrote : | #7 |
Actually it is a problem with the watchdog and location service crashing.
Oct 2 07:28:51 ubuntu-phablet watchdog: 'ubuntu-
I'll close this bug and file a new one.
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → Fix Released |
| Changed in mir (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in unity8 (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in canonical-devices-system-image: | |
| milestone: | ww46-2015 → ww40-2015 |


The above error from the U8 log really just tells that U8 lost its connection to USC.
Digging around the other logs I didn't find a reason for that.