** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
** Changed in: bluez (Ubuntu)
Status: Invalid => Won't Fix
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Status: Fix
** Changed in: canonical-devices-system-image
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage
Device part 20160106-6a15a0b
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not
** Changed in: canonical-devices-system-image
Status: Fix Released => Fix Committed
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is the log from Pat which shows the actual problem together
with some verbose logging.
>From the log the reason for the continous hold wakelock MT662x are therm
events we're receiving from the WiFi/BT/.. combo chip. They start to
flood at one point which will keep the device awake. One
With the latest kernel with fix for temperature controller reports
things are much improved.
Resume wakeup causes:
EINT,2903 94.47%
CLDMA_MD 85 2.77%
CLDMA_MD, 85 2.77%
Suspend failure causes:
tasks
I think I long ago added a bug on that, when plugged in to a charger we
should certainly suspend, its not an active USB data connection so we
should not hold the wakelock in that case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Latest log
Suspend blocking wakelocks:
None
Resume wakeup causes:
EINT, 170 98.84%
CLDMA_MD1 0.58%
CLDMA_MD, 1 0.58%
Suspend failure causes:
tasks freezer abort 783 99.87%
devices
syslog with phone plugged in and charging for several hours, then unplugged,
then charging again. All raidios on but did not connect to BT.
suspend-blocker is no longer able to parse the log output so unsure the suspend
success.
** Attachment added: "syslog"
@Pat: Does it print out something like:
Suspend blocking wakelocks:
None
Resume wakeup causes:
None
Suspend failure causes:
None
Suspends:
0 suspends aborted (0.00%).
0 suspends succeeded (0.00%).
total time: 0.00 seconds (0.00%).
minimum: 0.00 seconds.
maximum:
I looked through the code in the mx4 kernel now a bit more and the
reason for the hold wakelock is that there is simply data flowing. What
triggers the data flow or what data is actually flowing is not clear yet
but I don't see any HCI frames receiving on the bluetooth stack side so
far when this
I went through Pats log file and it looks basically like this: The
system doesn't go into sleep mode as their is still ongoing data flowing
over the transport to the BT/WiFi/GPS combo chip. If that is real or a
bug isn't clear yet. I am currently going through the responsible
driver and see how
Log with debugging kernel, pretty high fail to suspend rate
Suspends:
262 suspends aborted (38.93%).
411 suspends succeeded (61.07%).
total time: 7293.604631 seconds (84.86%).
minimum: 0.319212 seconds.
maximum: 1359.032827 seconds.
mean: 17.745997 seconds.
mode: 6.00 seconds.
The attachment "0001-Add-STP-MT662x-wakelock-traces.patch" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad
If somebody else wants to do this too the used boot.img for arale is
attached here.
** Attachment added: "boot.img"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4526228/+files/boot.img
--
You received this bug notification because you are a member of
Added some debug statements to the arale kernel and now waiting for the
problem to reappear here to find out more details.
** Patch added: "0001-Add-STP-MT662x-wakelock-traces.patch"
** Tags added: bluetooth-ota9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage notifications about this bug go to:
** Attachment added: "syslog"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4525282/+files/sl3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
On my MX4 after half a day of use
Suspends:
6826 suspends aborted (99.53%).
32 suspends succeeded (0.47%).
Battery dropped 50% overnight
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
My test MX4 did suspend reasonably over a period of several hours,
trying my daily driver now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage
Have a MX4 being active now for more than 3 days and not getting this
problem with rc-proposed (which has BlueZ 5 merged) again
simon@nirvana ...-bluez5-upgrade/suspend-problem-arale %
~/Work/ubuntu2/suspend-blocker/suspend-blocker syslog
syslog:
Suspends:
421 suspends aborted (13.66%).
2661
@Pat: Are you running rc-proposed? If yes, did you see anything over the
weekend which looks like this is still happening with bluez5 being
merged?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marked as In-Progress for system-image now too as BlueZ5 has landed in
the overlay ppa.
** Changed in: canonical-devices-system-image
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From the syslog in comment #2,
Suspend blocking wakelocks:
None
Resume wakeup causes:
EINT, 553 97.88%
CLDMA_MD6 1.06%
CLDMA_MD, 6 1.06%
Suspend failure causes:
tasks freezer abort
Generally I see aborted suspends because of the MT662x wakeup source
also on rc-proposed with its current kernel but not in such a high
frequency as Pat or I saw them before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
QA did a test run and measure power usage on an MX4 device. Results are
stored at http://people.canonical.com/~platform-qa/power-
results/?Chttp://people.canonical.com/~platform-qa/power-
results/?C=M;O=D=M;O=D Test run number is 166.
According to QA they don't show anything significant
@Julia yes there could be a bug still on BQ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage notifications about this bug go to:
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
Worth to mentioned but doesn't prove anything yet: When turning
bluetooth off
Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696811]
[HCI-STP][I]hci_stp_close:hdev(0xd91de000)
Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696829]
[HCI-STP][I]hci_stp_flush:done
Nov 13 06:06:18 ubuntu-phablet
Disabling WiFi as next step lets the device suspend (but being woken up
by EINT shortly afterwards again).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To
@Pat you mentioned a testing kernel on the MX4, but not on the BQ. If
this happens in the BQ as well running a stable kernel that means we're
still chasing this bug, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage notifications about this bug go to:
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
To manage notifications about this
35 matches
Mail list logo
