touch-packages team mailing list archive

[Simon Fels <simon.busch@xxxxxxxxxxxxx>]

I tried to reproduce this with two MX4:

- First one running rc-proposed, the newer kernel with upgraded bluetooth stack and  bluez4.
- Second one running rc-proposed, the newer kernel with upgraded bluetooth stack and bluez5.

Pat was running the first combination. I saw similar kernel suspend
aborts due to the wakeup source MT662x being still active but not such a
huge battery drain as Pat had. My battery only lost around 15-20% in
~20h where I just plugged it into my laptop for a few min to fetch a
recent syslog in between. The rest of the time the phone was just laying
around being paired and connect to a bluetooth device, being connected
to a WiFi network and got a GPS fix before I turned the screen off.

Statistics look like this:

Resume wakeup causes:
  EINT,                             909  100.00%

Suspend failure causes:
  tasks freezer abort               536  99.81%
  devices failed to suspend           1   0.19%

Suspends:
  588 suspends aborted (39.28%).
  909 suspends succeeded (60.72%).
  total time: 10361.993895 seconds (87.08%).
  minimum: 0.400780 seconds.
  maximum: 74.526359 seconds.
  mean: 11.399333 seconds.
  mode: 14.000000 seconds.
  median: 13.158011 seconds.

Time between successful suspends:
  total time: 1537.561435 seconds (12.92%).
  minimum: 0.897107 seconds.
  maximum: 11.649660 seconds.
  mean: 1.693350 seconds.
  mode: 1.000000 seconds.
  median: 1.030588 seconds.

** Attachment added: "syslog-mx4-bluez5-new-kernel-reproduced"
   https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4517989/+files/syslog-mx4-bluez5-new-kernel-reproduced

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1505241

Title:
  Phone does not suspend

Status in Canonical System Image:
  Invalid
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar behavior
  According to the logs they are not able to suspend due to active wakeup sources.
  (I am running a BT test kernel on the MX4 3.10.35+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+subscriptions