On devel-proposed I disabled both watchdogs, the services crashes, but the shell starts and I can make a call or networking is up for example.
Here is what the watchdog noticed and the reason it wopuld have rebooted if it was not disabled:
Oct 2 08:05:47 ubuntu-phablet watchdog: 'ubuntu-espoo-service' (instance '') hit respawn limit but not rebooting
Oct 2 08:05:48 ubuntu-phablet watchdog: 'ubuntu-location-provider-here-posclientd' (instance '') hit respawn limit but not rebooting
Oct 2 08:05:48 ubuntu-phablet watchdog: 'ubuntu-location-provider-here-slpgwd' (instance '') hit respawn limit but not rebooting
Oct 2 08:06:11 ubuntu-phablet watchdog: 'ubuntu-location-provider-here-slpgwd' (instance '') hit respawn limit but not rebooting
A system service crash that would make the device unusable is not worst than rebooting it in a loop.
On devel-proposed I disabled both watchdogs, the services crashes, but the shell starts and I can make a call or networking is up for example.
Here is what the watchdog noticed and the reason it wopuld have rebooted if it was not disabled: espoo-service' (instance '') hit respawn limit but not rebooting location- provider- here-posclientd ' (instance '') hit respawn limit but not rebooting location- provider- here-slpgwd' (instance '') hit respawn limit but not rebooting location- provider- here-slpgwd' (instance '') hit respawn limit but not rebooting
Oct 2 08:05:47 ubuntu-phablet watchdog: 'ubuntu-
Oct 2 08:05:48 ubuntu-phablet watchdog: 'ubuntu-
Oct 2 08:05:48 ubuntu-phablet watchdog: 'ubuntu-
Oct 2 08:06:11 ubuntu-phablet watchdog: 'ubuntu-
A system service crash that would make the device unusable is not worst than rebooting it in a loop.