** Changed in: ubuntu-push (Ubuntu)
Status: Confirmed => 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/1435109
Title:
Push-client frequently blocking phone suspend
To manage not
** Changed in: ubuntu-push
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/1435109
Title:
Push-client frequently blocking phone suspend
To manage notifica
** Changed in: ubuntu-push
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/1435109
Title:
Push-client frequently blocking phone suspend
To manage notificat
** Changed in: canonical-devices-system-image
Status: In Progress => 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/1435109
Title:
Push-client frequently blocking phone suspend
T
This bug was fixed in the package ubuntu-push - 0.64.1+15.04.20150331.2
~rtm-0ubuntu1
---
ubuntu-push (0.64.1+15.04.20150331.2~rtm-0ubuntu1) 14.09; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Samuele Pedroni (Canonical Services Ltd.) ]
* [Bret Barker] add a hacky
so the bug with 1.2 is because the futex uses the motonic clock but the
go timer heap was based on realtime futures times,
this was changed in go in 1.3, now the timers heap is using monotic
future timestamps,
this means that sleep/timers created after a suspend will work as
expected, sleep/tim
** Branch linked: lp:~noise/ubuntu-push/busy-sleep-hack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435109
Title:
Push-client frequently blocking phone suspend
To manage notifications about this
This futex behavior is expected, as it counts the relative time and only
the active time.
Did one test with a similar program using futex wait and comparing the
delta between suspends, and you can find the output at:
http://paste.ubuntu.com/10708286/
For it to work the way you expected, you'd nee
go uses relative timeouts with FUTEX_WAIT, which ignores time spent in
suspended state. This causes timers after wake from suspend to be
delayed. We are working around the issue by tricking go's runtime with a
busy sleep loop to reduce the delay to a max 1s.
--
You received this bug notification
pedronis made a c program to test the futex:
c code: https://pastebin.canonical.com/128528/
arm binary: http://people.canonical.com/~pedronis/futex_sleep
fuxex_sleep output: https://pastebin.canonical.com/128538/
push-client log: https://pastebin.canonical.com/128539/
powerd log: https://paste
On Wed, Mar 25, 2015 at 1:29 PM, Samuele Pedroni
wrote:
> pedronis: repro'd the stall
> when i took my phone off USB it must have really slept
Suspend shouldn't really interfere with this bug as once push gets the
sysstate cookie from powerd, that forces powerd to hold a wakelock
(blocking susp
A longer one:
http://pastebin.ubuntu.com/10679542/
http://pastebin.ubuntu.com/10679556/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435109
Title:
Push-client frequently blocking phone suspend
T
Another instance:
http://pastebin.ubuntu.com/10679483/
With associated strace:
http://pastebin.ubuntu.com/10679501/
(lines 40-69 are the activity between the logging)
And here's where we get stuck:
[pid 14764] 17:34:40.030047 futex(0x6579e8, FUTEX_WAIT, 0, NULL
[pid 14760] 17:35:24.991469 <... f
pedronis: repro'd the stall
when i took my phone off USB it must have really slept
https://pastebin.canonical.com/128332/
line 17
time.Sleep(p.times.SessionStateSettle)
is the only thing that happens in-between there
but it took 4 minutes
yah
wtf right?
yes :/
noise: I suppose as first
we merged to our dev branch a attached MP that should address some of
the situations,
we still don't understand the issue in comment #6
** Changed in: ubuntu-push
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: canonical-devices-system-image
Status: Confirmed => 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/1435109
Title:
Push-client frequently blocking phone suspend
To m
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-push (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/1435109
Title:
http://paste.ubuntu.com/10671598/
>From that log it appears that
time.Sleep(p.times.SessionStateSettle)
right after getting the wakelock cookie is taking anywhere from 40-89 seconds,
but should be only 20ms.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: ubuntu-push (Ubuntu RTM)
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/1435109
Title:
Push-client frequently blocking phone suspend
To m
** Branch linked: lp:~pedronis/ubuntu-push/dont-lock-for-long-in-
handleerr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435109
Title:
Push-client frequently blocking phone suspend
To manage noti
** Also affects: ubuntu-push
Importance: Undecided
Status: New
** Changed in: ubuntu-push
Assignee: (unassigned) => Samuele Pedroni (pedronis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
2015/03/23 17:34:13.189361 poller.go:170: DEBUG got woken up; time is
2015-03-23 17:34:13.189247951 -0300 BRT (𝛥: 1.189247951s)
2015/03/23 17:34:13.218912 poller.go:178: DEBUG got wakelock cookie of
f1bfecae-767d-4d04-9ba2-f39cf6c70523
2015/03/23 17:38:02.538146 poller.go:178: ERROR not connected
With the latest available at lp:ubuntu-push/automatic:
2015/03/23 17:26:40.203525 poller.go:178: DEBUG got wakelock cookie of
d3817bb1-b7ec-4204-846b-d1551d9ab487
2015/03/23 17:26:50.709443 networkmanager.go:145: DEBUG got primary connection:
/org/freedesktop/NetworkManager/ActiveConnection/1
201
>From ./.cache/upstart/ubuntu-push-client.log (with debug):
2015/03/23 14:49:51.103334 DEBUG got woken up; time is 2015-03-23
14:49:51.103221076 -0300 BRT (𝛥: 103.221076ms)
2015/03/23 14:49:51.108670 DEBUG got wakelock cookie of
239b6ccb-ea1e-4617-94ff-7569149f8188
2015/03/23 14:52:16.501222 DEB
phablet@ubuntu-phablet:~$ cat /etc/xdg/ubuntu-push-client/config.json
{
"auth_helper": "/usr/lib/ubuntu-push-client/signing-helper",
"session_url": "https://push.ubuntu.com/";,
"registration_url": "https://push.ubuntu.com";,
"connect_timeout": "20s",
"exchange_timeout": "30s",
>From IRC:
Mar 22 23:06:34 ubuntu-phablet powerd[964]: void
{anonymous}::reset_alarm_clock() found 3 remaining wakeup requests
Mar 22 23:06:34 ubuntu-phablet powerd[964]: setting hardware wakeup
time to 2015-03-22 23:09:20 for ubuntu push client
rsalveti: i'm afraid i don't understand what i'm
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => John Lenton (chipaca)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435109
Title:
Push-client frequently blocking phone
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
** Changed in: canonical-devices-system-image
Milestone: None => ww13-ota
--
You received this bug notification because you are a
28 matches
Mail list logo
