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

Openmoko Public Trac bugs at docs.openmoko.org
Sun Sep 21 16:27:25 CEST 2008


#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  |    Blockedby:                
Reproducible:  always       |     Blocking:                
----------------------------+-----------------------------------------------

Comment(by nicolas.dufresne):

 Hi,

 I'm having this issue too. I'm not adding any dmesg, since they are the
 same as others. Currently, only one reason for this has been proposed by
 Andy, it would be nice to have a bit more status on this.Here's the
 original comment:

 > I have seen two behaviours that give WSOD despite the happy story above
 -- first is during resume, the Glamo's Reset pin is falsely activated by a
 spike.  Because we assume most Glamo registers survive suspend, this kills
 us dead and the partial resume action we do on the registers does not
 succeed to issue any video. So with that problem you get a sticky WSOD
 until you reboot.

 Is this spike theory has been proven ? What would cause this spike ? If we
 know a spike might reset the Glamo, can we detect that in software and
 maybe do a complete reset of the Glamo ? What would be the result of
 always doing a complete reset of the Glamo ? I think we are all ready for
 experiment on this, we just need a OpenMoko god to guide are ignorance
 when hacking the Glamo driver.

 Thanks,
 Nicolas

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


More information about the buglog mailing list