Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2284: After suspend, phone does not ring on
incoming call (Openmoko Public Trac)
2. Re: Openmoko Bug #2284: After suspend, phone does not ring on
incoming call (Openmoko Public Trac)
--- Begin Message ---
#2284: After suspend, phone does not ring on incoming call
----------------------+-----------------------------------------------------
Reporter: airzimmy | Owner: Nytowl
Type: defect | Status: accepted
Priority: normal | Milestone: Om2009
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------+-----------------------------------------------------
Changes (by Nytowl):
* cc: mic...@… (added)
Comment:
From looking through the logs it looks like oeventsd gets out of sync with
requesting and releasing the CPU. Hopefully Mcikey can shed some more
light on this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2284#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2284: After suspend, phone does not ring on incoming call
----------------------+-----------------------------------------------------
Reporter: airzimmy | Owner: Nytowl
Type: defect | Status: accepted
Priority: normal | Milestone: Om2009
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------+-----------------------------------------------------
Comment(by khiraly):
Ok, I examined the log a bit more. I write down my findings.
Im talking about frameworkd-unstable0513-doesnt-suspend2.log.gz
The interesting part is between line 12139-13092.
Interesting lines:
12110, 12134, 12151, 12161 WARNING Untrigger for
'CallListContains(active)' called, but not yet triggered. Not untriggering
12167 WARNING call 1 already registered
12168 DEBUG resuming CPU
12169 DEBUG Enabling CPU
13092 ERROR re org.freedesktop.DBus.Error.NoReply: Did not receive a
reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
Here is my suspicion:
When receive call/sms, first* it puts into CallList the "call event" and
after trigger it, this results two CPU request, and it enables cpu (12168)
on its own.
*: Surely there must be some race-condition, and therefore it does not
happen always.
However I dont know why there is a D-Bus *timeout*, when something busy,
respond with busy.
I cant digg into more without knowing frameworkd internals, so would be
nice some frameworkd expert could pop up here or in irc to discuss a bit
about this issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2284#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
