Your log is actually fine from powerd's perspective (powerd is indeed trying to suspend and releasing everything it can), but in your case it seems the usb device is blocking suspend: Feb 19 16:01:04 ubuntu-phablet kernel: [ 5926.373385] usb 1-1: abort suspend Feb 19 16:01:04 ubuntu-phablet kernel: [ 5926.373446] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Feb 19 16:01:04 ubuntu-phablet kernel: [ 5926.373477] PM: Device 1-1 failed to suspend async: error -16
The interesting piece is that you disconnected the usb cable right in the beginning of the log file. IIRC mako talks with the modem via USB, which might explain why it's failing to suspend. The problem is that this is probably a bug in mako's kernel, as our userspace is indeed behaving as expected (and probably why we can't reproduce this bug with krillin). ** Summary changed: - Phone does not deep suspend after incoming call + [mako] phone does not deep suspend after incoming call -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420387 Title: [mako] phone does not deep suspend after incoming call To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420387/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
