Openmoko Bug #2126: xserver-xglamo eats 100% cpu time after resume

Openmoko Public Trac bugs at
Wed Nov 19 23:01:12 CET 2008

#2126: xserver-xglamo eats 100% cpu time after resume
    Reporter:  lindi    |        Owner:  openmoko-devel
        Type:  defect   |       Status:  new           
    Priority:  normal   |    Milestone:                
   Component:  unknown  |      Version:                
    Severity:  normal   |   Resolution:                
    Keywords:           |     Haspatch:  0             
   Blockedby:           |    Estimated:                
 Patchreview:           |     Blocking:                
Reproducible:           |  

Comment(by lindi):

 Thanks for your patch. I started a kernel build to test your patch but
 meanwhile the bug occured again.

 X seems to respond to touchscreen, I can move the mouse pointer but there
 is a lag of several seconds before it moves to a new position. X does not
 seem to ever finish redrawing xvkbd buttons (it has drawn the first row of
 letters but nothing new seems to be drawn). This time I don't see BUG
 print from kernel so maybe it is only printed if I try to kill -9 X?
 Before I could issue the kill command try this the device suddenly stopped
 responding to ping over usb network and did not react to anything on the
 touchscreen. I had to remove the battery to make it boot again.

 I have not changed kernel recently. The only major change was upgrading to
 new version of fso-frameworkd and using.

 mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/Usage

 instead of

 mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
 apm -s
 mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device

 to issue suspend (I had to do this since the API changed and the daemon
 itself now wants to do the "apm -s" invocation.)

Ticket URL: <> <>
openmoko trac

More information about the buglog mailing list