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

[Openmoko Public Trac]

#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):

 I can kill -9 xglamo this time. When I start xglamo again it does not exit
 but I do not see anything on the screen either. Kernel prints the
 following:

 {{{
 Nov 25 15:04:50 ginger user.err kernel: [43325.595000]
 glamofb_update_lcd_controller spin_lock_irqsave
 Nov 25 15:04:50 ginger user.err kernel: [43325.595000]
 glamofb_update_lcd_controller spin_unlock_irqrestore
 Nov 25 15:04:50 ginger user.err kernel: [43325.615000] fbcon_event_notify
 action=1, data=c7269df0
 Nov 25 15:04:50 ginger user.err kernel: [43325.660000]
 glamofb_update_lcd_controller spin_lock_irqsave
 Nov 25 15:04:50 ginger user.err kernel: [43325.660000]
 glamofb_update_lcd_controller spin_unlock_irqrestore
 Nov 25 15:04:50 ginger user.err kernel: [43325.665000] fbcon_event_notify
 action=1, data=c7269df0
 }}}

 Also trying to set the backlight does not work anymore with X or without X
 running:

 {{{
 root at ginger:~# echo 1 > /sys/class/backlight/pcf50633-bl/bl_power
 root at ginger:~# cat /sys/class/backlight/pcf50633-bl/bl_power
 1
 root at ginger:~# echo 63 > /sys/class/backlight/pcf50633-bl/brightness
 root at ginger:~# cat /sys/class/backlight/pcf50633-bl/actual_brightness
 2
 }}}

 Shouldn't backlight be adjustable always like that? (And would mean that
 this is actually a kernel bug and not xglamo bug).

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2126#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac