Openmoko Bug #2284: After suspend, phone does not ring on incoming call

Openmoko Public Trac bugs at
Fri May 15 11:16:40 CEST 2009

#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: <> <>
openmoko trac

More information about the buglog mailing list