Openmoko Bug #1315: xglamo: Performance decreases after a while

Openmoko Public Trac bugs at
Sun Aug 17 23:45:12 CEST 2008

#1315: xglamo: Performance decreases after a while
    Reporter:  zecke at        |        Owner:  openmoko-devel
        Type:  defect                   |       Status:  new           
    Priority:  highest                  |    Milestone:                
   Component:  Xfbdev (kdrive), Xglamo  |      Version:  Om2008.8      
    Severity:  critical                 |   Resolution:                
    Keywords:                           |    Blockedby:                
Reproducible:                           |     Blocking:                

Comment(by denver):

 Here are some more details on the specific problem I am encountering:

 When running a recently-updated 2007.2 build, the device becomes
 unresponsive to touchscreen taps after a few hours of being on (the exact
 number of hours varies).  This seems to occur at random; it even occurs
 when there is no apparent activity on the unit (screen has not been
 updated and touchscreen has not being pressed for several minutes).  The
 unit still responds to SSH while unresponsive to the touchscreen.  Running
 top shows that Xglamo is consuming a lot of CPU (presumably spinning).
 After a few minutes (about 5), Xglamo stops consuming CPU.  The unit will
 then respond with an audible click when pressing the touchscreen (and the
 screen turns on if dimmed), but Xglamo immediately starts hogging the CPU
 again and the screen becomes unresponsive.  After a few minutes, Xglamo
 stops hogging the CPU again and the cycle continues.

 Even if one does not press the touchscreen once Xglamo stops hogging the
 CPU, Xglamo can start spinning again at random.  Again, it will stop
 hogging the CPU after a few minutes but starts spinning immediately after
 the touchscreen is pressed.

 The problem can be corrected by stopping and starting the X server.
 However, you must either send Xglamo a SIGKILL or wait for it to stop
 spinning (at which point it exits) following "/etc/init.d/xserver-nodm

 Attaching to Xglamo with gdb while it's spinning tends to show Xglamo in
 gettimeofday or GLAMOEngineWait, much like in the gdb output of comment 6.

Ticket URL: <> <>
openmoko trac

More information about the devel mailing list