WSOD solutions??

Andy Green andy at
Thu Dec 4 09:37:14 CET 2008

Hash: SHA1

Somebody in the thread at some point said:
| Am Do  4. Dezember 2008 schrieb Andy Green:
|> Somebody in the thread at some point said:
|> | Further plans: modify driver to take down the complete LCM via LDO6
|> instead of
|> | entering deep_suspend. This seems to be the more reasonable
approach for
|> | saving power while LCM disabled anyway, and it might cure WSOD as the
|> LCM is
|> | powered up from suspend-mode the same way as on boot. Side-effects
|> | under investigation (sneak currents, any persistent data lost during
|> power
|> | down, timing issues for LCM coming up)
|> Any reason none of this is on the Trac report?
| We decide on when to post any results to Trac. Emphasis on "results".

Interested parties internal and external likely read either kernel list
or the Trac bug

or both, but not really support list.  For this kind of hard to
reproduce issue, you and the guys that are working on this (Jeremy?)
need to make a "decision" to work both with customers experiencing it
and other folks internal and external who already poke at the same bug.

|> The hard reset line we operate into the LCM should make whether the
|> power to it is up in suspend moot... neither does it explain why the
|> WSOD comes with the blanking changes that are nothing to do with suspend.
| Thanks for concise summary of obvious conclusions resulting from my
| posting.

But I didn't see you mention this "obvious conclusion".

I'm also surprised if there's really nothing to this temperature thing.
~ Several users told it to reliably be the case on their "bad" LCM.

BTW I already removed LCM power at suspend already a couple of days ago
in andy-tracking;a=commitdiff;h=4a116494da4e43fdd8c40c08cc0b2e9cf3fda154

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the support mailing list