Openmoko Bug #1841: white screen of death (WSOD) after resume
Openmoko Public Trac
bugs at docs.openmoko.org
Sun Nov 23 21:53:07 CET 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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by nicolas.dufresne):
I've seen the hard reset that has been added in the jbt driver in stable-
tracking so I've tested it. I've got the same problem too, but I've tested
only once and did not try to sleep it again to see if reset help
recovering (I will try to find time later to do this test).
I've been reading the jbt driver source code today. I have a feeling that
locking is too weak. I think it only protects the registry cache.This
makes me think there is a larger problem. As the resume process implies
multiple reg_write (and the locking is done inside this function) it means
that registry could be written during a suspend or resume sequence or
registry write, which I don't think it is a good idea. But I might also be
totally wrong.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:65>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list