vivid-proposed/krillin - Phone reboots spontaneously

[Jean-Baptiste Lallement]

current build number: 122
device name: krillin
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-02-25 15:06:29
version version: 122
version ubuntu: 20150225
version device: 20150210-95b6a9f
version custom: 20150225

It happened up to 3 times a day, the phone reboots with no apparent reason. syslog doesn't work on the phone but /proc/last_kmsg shows the following message:

[ 793.598710]systemd-logind[16120]: Failed to start user service: Unknown unit: [e-mail]
[ 793.606282]systemd-logind[16120]: Failed to start user service: Unknown unit: [e-mail]
[ 806.517752]systemd-logind[16242]: Failed to start user service: Unknown unit: [e-mail]
[ 806.521333]systemd-logind[16242]: Failed to start user service: Unknown unit: [e-mail]
[ 809.797251]Restarting system.
[ 809.797336][<c0015404>] (unwind_backtrace+0x0/0x104) from [<c07db344>] (dump_stack+0x20/0x24)
[ 809.797366][<c0015404>] (unwind_backtrace+0x0/0x104) from [<c07db344>] (dump_stack+0x20/0x24)
[ 809.797396][<c07db344>] (dump_stack+0x20/0x24) from [<c0014110>] (handle_IPI+0xf4/0x250)
[ 809.797424][<c07db344>] (dump_stack+0x20/0x24) from [<c0014110>] (handle_IPI+0xf4/0x250)
[ 809.797452][<c0014110>] (handle_IPI+0xf4/0x250) from [<c00085bc>] hdo_IPI+0x18/0x1c)
[ 809.797477][<c0014110>] (handle_IPI+0xf4/0x250) from [<c00085bc>] (do_IPI+0x18/0x1c)
[ 809.797502][<c00085bc>] (do_IPI+0x18/0x1c) from [<c07eb9f4>] (__irq_svc+0x34/0xc8)
[ 809.797529][<c00085bc>] (do_IPI+0x18/0x1c) from [<c07eb9f4>] (__irq_svc+0x34/0xc8)
[ 809.797686][<c07eb9f4>] (8e1fac dc+0x34/0xc8) from [<c000f178>] (78 20070013 ffffffff
[ 809.797718][<c07eb9f4>] (__irq_svc+0x34/0xc8) from [<c000f178>] (default_idle+0x2c/0x40)
[ 809.797747][<c000f178>] (default_idle+0x2c/0x40) from [<c000f5a0>defcpu_idle+0xb0/0x10c)
[ 809.797775][<c000f178>] (default_idle+0x2c/0x40) from [<c000f5a0>] (cpu_idle+0xb0/0x10c)
[ 809.797804][<c000f5a0>] (cpu_idle+0xb0/0x10c) from [<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8)
[ 809.797834][<c000f5a0>] (cpu_idle+0xb0/0x10c) from [<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8)
[ 809.797863][<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8) fromsecondary_start0x807d7d8c)
[ 809.797889][<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8) from [<807d7d8c>] (0x807d7d8c)
[ 809.797915][<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8) from [<807d7d8c>] (0x807d7d8c)
[ 809.797964][<c07db344>] (dump_stack+0x20/0x24) from [<c0014110>] (handle_IPI+0xf4/0x250)
[ 809.798009][<c0014110>] (handle_IPI+0xf4/0x250) from [<c00085bc>] (do_IPI+0x18/0x1c)
[ 809.798056][<c00085bc>] (do_IPI+0x18/0x1c) from [<c07eb9f4>] (__irq_svc+0x34/0xc8)
[ 809.798218][<c07eb9f4>] (__irq_svc+0x34/0xc8) from [<c000f178>] (default_idle+0x2c/0x40)
[ 809.798269][<c000f178>] (default_idle+0x2c/0x40) from [<c000f5a0>] (cpu_idle+0xb0/0x10c)
[ 809.798319][<c000f5a0>] (cpu_idle+0xb0/0x10c) from [<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8)
[ 809.798365][<c07d8448>] (secondary_start_kernel+0x1cc/0x1e8) from [<807d7d8c>] (0x807d7d8c)

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1426272

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Jean-Baptiste Lallement (jibel)]

I cannot run that command on a phone

[Víctor R. Ruiz (vrruiz)]

I also experienced this problem, while doing a test I tapped an app icon in the Dash and the device suddenly freezed for a while and finally rebooted. No crash files were available in /var/crash.

[Ricardo Salveti (rsalveti)]

We need at least your syslog here to know what happens, because here I believe that the system is just rebooting because something else crashed.

In vivid we added an upstart watchdog that reboots the phone when a core service crashes for a few times in a row (as we can't really guarantee that the phone is in a proper shape), so this might be just a bad side effect of another service crashing.

I added a new logic that at least disables this if you're using a rw filesystem, as then you're entirely responsible for whatever customization you may add, so this would only apply for ro fs.

[Jean-Baptiste Lallement (jibel)]

I couldn't reproduce this crash on recent builds and there was no syslog on the image I tested due to a bug with the ownership of /var/log.

I'm closing this report because of the lack of information and will re-open if it reproduces.