The issue became *much* better on my krillin device with OTA-4. Can
anybody comment on what was changed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421455
Title:
Slow wake up time on physical
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: powerd (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421455
Title:
So this bug has to be escalated to the handset or even the chipset
manufacturer, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421455
Title:
Slow wake up time on physical power button
I was monitoring my syslog while pressing the button.
Apr 29 14:37:35 ubuntu-phablet powerd[949]: handle_requestSysState from :1.13 -
ACTIVE (1)
Apr 29 14:37:35 ubuntu-phablet powerd[949]: name_watch_add: looking for :1.13
Apr 29 14:37:35 ubuntu-phablet powerd[949]: watching :1.13 to see when it
Looking at the strace output one can see that powerd gets the power
button press notification, processes it, and then nothing happens for
half a second:
[pid 949] 1430318963.039809 send(3, 31Apr 29 16:49:23 powerd[949]: exiting
suspend, 48, MSG_NOSIGNAL) = 48
[pid 949] 1430318963.040868
Yeah it seems likely that some driver is probably being slow in its
late_resume handler. There may be something in dmesg which shows how
long individual late_resume calls are making, I can't remember (there
may also be some debug option which has to be enabled).
Iirc the reason we have to wait
** Tags added: pm-fail
** Also affects: powerd (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/1421455
Title:
Slow wake up time on physical power
Just a quick follow-up: we are using the backend that blocks on fb state
-- all a device needs is
/sys/power/{state,wake_lock,wait_for_fb_sleep,wait_for_fb_wake}
So I'm feeling confident that's a part of the puzzle here.
--
You received this bug notification because you are a member of Ubuntu
So looking at the powerd code, the only thing that does anything *real*
between exiting suspend and Emitting signal for transition to state
ACTIVE is a call to libsuspend_exit_suspend().
Which -- depending on the backend -- either makes one syscall and
returns, or makes one syscall and waits for
So looking at the powerd code, the only thing that does anything *real*
between exiting suspend and Emitting signal for transition to state
ACTIVE is a call to libsuspend_exit_suspend().
Which -- depending on the backend -- either makes one syscall and
returns, or makes one syscall and waits for
This is close in behavior to bug 1429887.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421455
Title:
Slow wake up time on physical power button pressed
To manage notifications about this bug go
It's unfortunately still unclear what's happening here. The working
assumption is that dbus traffic is high in those instances, causing
messages to get queued and block some parts of the system. Unfortunately
steps to reproduce still unknown :/
** Changed in: unity8 (Ubuntu)
Assignee:
@Szymon, that video link is incorrect?
@Saviq, no, I didn't leave a bug open for it, so this one is fine. It's
not clear whether this is unity8's fault or USC's or powerd's. We'd
need to add debugging to each one, then reproduce. But it's also not
clear how to reliably reproduce.
** Changed
Sorry I pasted wrong link, here is correct one:
http://youtu.be/DypDSYhJV6g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421455
Title:
Slow wake up time on physical power button pressed
To
@Szymon, thanks for the video! Looks painful. So both the greeter
coming on slowly and being slow to log in might both be PAM problems
then...
I'll assign back to myself, but again, I don't really know how to
reproduce this. :(
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) =
It looks like this problem is something escalating to unacceptable
stage, here short video:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421455
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
16 matches
Mail list logo
