WSOD (ticket #1841) (unofficial) survey question

Andy Green andy at openmoko.com
Fri Nov 14 18:43:33 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| On Thursday 13 November 2008 09:14:01 grslmpf wrote:
| ...
|>> Mayby the Glamo will work only partly caused by a bad reset?
| I've experienced the WSOD about three times in the last six months on
| a Neo 1973. It only appears if I use an X server (I've never seen in on
| Qtopia). Since the 1973 doesn't have Glamo, the source of the problem
probably
| lies elsewhere.

There has been more than one problem flying around... WSOD is typically
caused by unconfigured or misconfigured jbt6k74 ASIC inside the LCM,
which takes an SPI connection on both GTA01 and GTA02.

On the stable-tracking branch now you should be able to recover from a
WSOD by this:

~  echo 1 > /sys/bus/spi/drivers/jbt6k74/spi2.0/reset

If you're interested to try it on GTA02 anyway you can get an image here:

http://people.openmoko.org/andy/uImage-moredrivers-GTA02_stable-tracking_35e59a5529403296-GTA02.bin

You'll probably need Qi to start it unless you want to meddle with
U-Boot env (DFU this into U-Boot partition, you can use NOR U-Boot to
replace or update it)

http://people.openmoko.org/andy/qi-s3c2442-andy_589233efbd0792b8.udfu

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkkduMUACgkQOjLpvpq7dMoxHQCfT8uJa4pWoAmFxNlzZP5QPkRn
mgIAnR4p4orOrcDaEy0+6ajEDo90DwtT
=MFsp
-----END PGP SIGNATURE-----




More information about the community mailing list