touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #100334
[Bug 1480785] Re: ofono does not start after upgrade (initclt stalls when sending an event)
The ofono job on the Ubuntu phone has the following start rule:
start on started dbus and rild-ready
The rild-ready event will have been emitted as soon as 'initctl emit' is
called, but the command won't return until all jobs depending on it have
finished. If ofono has not started, the cause will be that the 'started
dbus' event has not triggered, rather than that rild hasn't started
correctly.
dbus is 'start on filesystem'. The filesystem event happens late in
boot and requires all the filesystems to have been successfully mounted.
So something is probably blocking one or more filesystem mounts from
completing.
Additional information to gather when this problem occurs:
ps awx|grep mountall
initctl list
status dbus
If this problem is consistently reproducible, modifying
/etc/init/mountall.conf to run mountall with --verbose and capturing
/var/log/upstart/mountall.log would also be helpful.
** Changed in: canonical-devices-system-image
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1480785
Title:
ofono does not start after upgrade (initclt stalls when sending an
event)
Status in Canonical System Image:
Incomplete
Status in upstart package in Ubuntu:
Confirmed
Bug description:
Some times, on first boot after either using ubuntu-device-flash or
upgrading the phone via OTA, some processes do not start because
initctl seems to stall and does not send events that trigger the
launch of those processes. For instance, I see in my arale:
$ ps -ef | grep initclt
root 742 563 1 08:25 ? 00:00:00 initctl emit android
root 1826 746 0 08:25 ? 00:00:00 initctl emit rild-ready OFONO_RIL_DEVICE=mtk OFONO_RIL_NUM_SIM_SLOTS=1
and "ofonod" is not started because "rild-ready" is not emitted.
A second boot solves the issue and I do not see any initctl process
still executing after some seconds.
This bug can certainly scare people when they see that they do not
have telephony just after an OTA.
I have reproduced in
$ system-image-cli -i
current build number: 80
device name: arale
channel: ubuntu-touch/devel-proposed/meizu.en
last update: 2015-08-03 08:24:54
version version: 80
version ubuntu: 20150802
version device: 20150709-8965e37
version custom: 20150716-819-8-42
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480785/+subscriptions
References