Openmoko Bug #1841: white screen of death (WSOD) after resume

[Openmoko Public Trac]

#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
    Reporter:  Rorschach    |        Owner:  openmoko-devel
        Type:  defect       |       Status:  new           
    Priority:  highest      |    Milestone:                
   Component:  unknown      |      Version:  GTA02v5       
    Severity:  critical     |   Resolution:                
    Keywords:  wsod,resume  |     Haspatch:  0             
   Blockedby:               |    Estimated:                
 Patchreview:               |     Blocking:                
Reproducible:  always       |  
----------------------------+-----------------------------------------------

Comment(by andy):

 Is it ever the case that once you had a WSOD, by making it right
 temperature or anything else, that we ever recover from it during the same
 session?

 On current andy-tracking there is a /sys node

 /sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.9/glamo3362.0/glamo-
 spi-gpio.0/spi2.0/reset

 if you echo 1 in there (take care about spaces, echo 1 > /sys...) it
 should reset the jbt6k74 asic in the LCM.


 Nicolas: About the locking, yes it can make trouble because the
 framebuffer blanking action that calls through to jbt6k74 code now is
 async to resume action in jbt6k74.  But if this was the problem, a
 subsequent use of that reset /sys node should clear it, since that reset
 code does a physical hard reset of the LCM similar to boot init, and we
 NEVER see WSOD on boot.  But I get the feel this WSOD thing is super
 sticky and the only thing that impresses it is reboot which is knows about
 somehow.

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