WSOD
Andy Green
andy at openmoko.com
Thu Dec 18 11:18:08 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody in the thread at some point said:
|> ok, so i flashed the images above and then did a wget for the kernel
|> opk and then did a opkg install
|>
kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk.
|>
|> again after 5-10 suspend/resume cycles, i got the wsod again. does
|> this mean i did something wrong or that you are mistaken or that i was
|> unlucky enough to get bad hardware?
Well, first confirm with cat /proc/version that you're running what you
think you're running.
Second, WSOD from resume is a bit ambiguous since it can be a more
generic resume failure on 2.6.24. If you disable resume and just let it
do framebuffer blanking for a while, do you ever see the WSOD just from
that?
- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAklKI2AACgkQOjLpvpq7dMp+ZwCfcc08rVov6HwcjRzlUVV1eFtG
iVgAmwfV4YDHAWuoNB3tXw4fOjriSbth
=VPSs
-----END PGP SIGNATURE-----
More information about the community
mailing list