krillin/devel-proposed fails to boot

Bug #1501639 reported by Jean-Baptiste Lallement on 2015-10-01
6
This bug affects 1 person
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/mir-MEFZIJ/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169): Throw in function virtual MirWaitHandle* {anonymous}::ExchangeSemantics::submit(const std::function<void()>&, mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >

All logs attached.

Jean-Baptiste Lallement (jibel) wrote :
Changed in mir (Ubuntu):
importance: Undecided → Critical
kevin gunn (kgunn72) on 2015-10-01
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 :

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.

Michael Terry (mterry) on 2015-10-01
Changed in unity8 (Ubuntu):
assignee: nobody → Michael Terry (mterry)
Michael Terry (mterry) on 2015-10-01
Changed in unity8 (Ubuntu):
status: New → Confirmed
Michael Terry (mterry) wrote :

This actually started with image 211 (20150930). Here's the manifest delta:

indicator-bluetooth from 0.0.6+15.10.20150915-0ubuntu1 to 0.0.6+15.10.20150929-0ubuntu1
qtdeclarative5-qtmir-plugin:armhf from 0.4.6+15.10.20150923-0ubuntu1 to 0.4.6+15.10.20150925-0ubuntu1
qtdeclarative5-ubuntu-ui-extras-browser-plugin:armhf from 0.23+15.10.20150922-0ubuntu1 to 0.23+15.10.20150928-0ubuntu1
qtdeclarative5-ubuntu-web-plugin:armhf from 0.23+15.10.20150922-0ubuntu1 to 0.23+15.10.20150928-0ubuntu1
qtmir-android:armhf from 0.4.6+15.10.20150923-0ubuntu1 to 0.4.6+15.10.20150925-0ubuntu1
unity-system-compositor from 0.1.2+15.10.20150922-0ubuntu1 to 0.1.3+15.10.20150925.1-0ubuntu1
unity8 from 8.11+15.10.20150922.1-0ubuntu1 to 8.11+15.10.20150925-0ubuntu1
unity8-common from 8.11+15.10.20150922.1-0ubuntu1 to 8.11+15.10.20150925-0ubuntu1
unity8-private:armhf from 8.11+15.10.20150922.1-0ubuntu1 to 8.11+15.10.20150925-0ubuntu1
webapp-container from 0.23+15.10.20150922-0ubuntu1 to 0.23+15.10.20150928-0ubuntu1
webbrowser-app from 0.23+15.10.20150922-0ubuntu1 to 0.23+15.10.20150928-0ubuntu1

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 :

Yup. Upgrading qtmir & unity8 fixed it. I expect this to be fixed in image 213.

Michael Terry (mterry) on 2015-10-01
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 :

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 :

logs for devel-proposed/krillin.en 213

Jean-Baptiste Lallement (jibel) wrote :

Actually it is a problem with the watchdog and location service crashing.

Oct 2 07:28:51 ubuntu-phablet watchdog: 'ubuntu-espoo-service' (instance '') hit respawn limit - rebooting

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers