Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Wed, 20 May 2009, Joerg Reisenweber wrote: Am Mi 20. Mai 2009 schrieb Chris Jenks: Apparently the qi version hosted there is mislabeled as 2.6.28, since I checked what got installed and it is indeed 2.6.29-rc2. Errr, Qi-version, kernel version??? /j Ouch! Yes, I meant kernel. I also just switched back to u-boot after getting the WSOD with the current Qi and current kernel. The new GSM updater that boots and runs from uSD is very nice. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Thu, 14 May 2009, Angus Ainslie wrote: On May 13, 2009 03:11:36 pm einstein wrote: i have the same problem. i switch to uboot back so i can use the suspend. where i can find the 2.6.29 kernel? with the 2.6.29 kernel the problem is fixed? If you installed the kernel from http://downloads.openmoko.org/distro/testing/NeoFreerunner/ Then you have the 2.6.29-rc2 kernel. To verify uname -a Angus Apparently the qi version hosted there is mislabeled as 2.6.28, since I checked what got installed and it is indeed 2.6.29-rc2. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
Am Mi 20. Mai 2009 schrieb Chris Jenks: Apparently the qi version hosted there is mislabeled as 2.6.28, since I checked what got installed and it is indeed 2.6.29-rc2. Errr, Qi-version, kernel version??? /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Mon, 23 Feb 2009, Jeffrey Ratcliffe wrote: 2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com: The only other thing I did around the same time was to replace uBoot with Qi. To test this, I booted into NOR, thereby using uBoot, and then booted the 2.4.24 image again (which I had reflashed). Resume then works without WSOD. i.e. Qi, for me at least, causes WSOD. [...] I've been playing with the beta Om 2009 consisting of fso-paroli-image, uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume properly. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
2009/5/13 Chris Jenks ch...@jenks.us: I've been playing with the beta Om 2009 consisting of fso-paroli-image, uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume properly. Although, from what I understand, 2.6.28 uboot don't suspend properly. I have Qi and 2.6.29 in flash, which works fine, and 2.6.28 on an SD, which gives me WSOD - i.e. the kernel is really at fault, not Qi. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
Chris Jenks wrote: On Mon, 23 Feb 2009, Jeffrey Ratcliffe wrote: 2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com: The only other thing I did around the same time was to replace uBoot with Qi. To test this, I booted into NOR, thereby using uBoot, and then booted the 2.4.24 image again (which I had reflashed). Resume then works without WSOD. i.e. Qi, for me at least, causes WSOD. [...] I've been playing with the beta Om 2009 consisting of fso-paroli-image, uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume properly. i have the same problem. i switch to uboot back so i can use the suspend. where i can find the 2.6.29 kernel? with the 2.6.29 kernel the problem is fixed? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On May 13, 2009 11:11pm, einstein mailingl...@freeyourphone.de wrote: i have the same problem. i switch to uboot back so i can use the suspend. where i can find the 2.6.29 kernel? with the 2.6.29 kernel the problem is fixed? I use the 2.6.29 kernel from SHR-testing, and with that and Qi, suspend/resume works properly. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qi causes WSOD (was Re: [2008.testing] WSOD)
2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com: The only other thing I did around the same time was to replace uBoot with Qi. To test this, I booted into NOR, thereby using uBoot, and then booted the 2.4.24 image again (which I had reflashed). Resume then works without WSOD. i.e. Qi, for me at least, causes WSOD. The suspend process seems different, too - with uBoot, the fade to black is gradual, but with Qi, it is more or less instantaneous, with a click, as if a relay was switching. I'll get the friend of mine to redo the SD/GPS fix to make sure that has nothing to do with it, but I doubt it. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com: | The only other thing I did around the same time was to replace uBoot with Qi. | | To test this, I booted into NOR, thereby using uBoot, and then booted | the 2.4.24 image again (which I had reflashed). Resume then works | without WSOD. | | i.e. Qi, for me at least, causes WSOD. | | The suspend process seems different, too - with uBoot, the fade to | black is gradual, but with Qi, it is more or less instantaneous, with | a click, as if a relay was switching. Suspend and resume on 2.6.24 only works by luck, it's not telling us much. But on community list, I see people reporting the same thing with 2.6.28-rc4. Why are people shipping 2.6.28-rc4 and not 2.6.29-rc2 in our stable branch? No idea. However, Qi works perfectly fine with suspend and resume here on recent andy-tracking and worked fine ever since the original WSOD fixes. | I'll get the friend of mine to redo the SD/GPS fix to make sure that | has nothing to do with it, but I doubt it. I wouldn't bother, I doubt it has anything to do with it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmjTgAACgkQOjLpvpq7dMoATQCfQY7omEOzkfdC/eL0zijzkIjD GiAAmwRr5XH+oz2z9yBASdrLh8d2EVWI =Wg2b -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Feb 24, 2009 2:31am, Andy Green a...@openmoko.com wrote: Suspend and resume on 2.6.24 only works by luck, it's not telling us much. OK. You are saying that with uBoot+2.6.24, it wasn't suspending properly, hence resume worked, but with Qi+2.6.24, suspend worked, but resume is broken. Why does Qi/uBoot affect this? What distro do I need to flash to test this properly (ie which diistro is using 2.6.28 or 2.6.29)? FSO? I understand that I can't simply flash 2.6.29 onto 2008.12 as the userspace file structure is different. Which kernel is Debian using 2.6.24? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Feb 24, 2009 2:31am, Andy Green a...@openmoko.com wrote: | Suspend and resume on 2.6.24 only works by luck, it's not telling us | much. | | OK. You are saying that with uBoot+2.6.24, it wasn't suspending | properly, hence resume worked, but with Qi+2.6.24, suspend worked, but | resume is broken. What I mean is that it's known 2.6.24 kernel stuff is broken for suspend / resume in a deep way, if it happens to work it's basically chance. So hearing that it doesn't work properly under some conditions don't give a good clue, since it can break under different timing or interrupts or whatever happening. 2.6.28+ stuff has this fixed, so misbehaviour on resume means a smaller set of possibilities and we can start to imagine what can be happening. | Why does Qi/uBoot affect this? I think it's to do with the sequencing of power / init to the LCM. In U-Boot, we bring up the Glamo and LCM to show the boot logo. In Qi, we do not bring up the Glamo LCD controller nor program the LCM until the Linux drivers start. We know that the guts of the LCM are not entirely under control since the last WSOD business, there's some people reporting monochrome display after resume as well. But it varies by physical LCM, I run Qi for months every build and I don't see any of it on my test GTA02. | What distro do I need to flash to test this properly (i.e. which diistro | is using 2.6.28 or 2.6.29)? FSO? I understand that I can't simply flash | 2.6.29 onto 2008.12 as the userspace file structure is different. | | Which kernel is Debian using 2.6.24? This FSO v5 thing, really anything with 2.6.28 should also work well with 2.6.29 stuff. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmjkhAACgkQOjLpvpq7dMrDUACfR+WZ2Xfw8r2Xwa4RURhD/n2o Fs4An0t1vpnXqVj5n6SVqz6LeFZKwv2w =+82c -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[2008.testing] WSOD
My FR suffers from the buzzing problem, and so I got a friend of mine who does that sort of soldering every day as part of his job to do the big-C fix, and whilst he was at it, the SD/GPS fix. Ever since the fixes were done, my FR gets the WSOD, i.e. on resume, the screen goes white, and then fades to black, starting in the middle. Without the SD card, the white screen take much longer to fade, and then to vertical light grey stripes of various widths, a bit like a faded barcode. I assume that the big-C fix can have nothing to do with this, but I wondered if the SD/GPS fix could. Removing the 10pF cap, however made no difference, I still never get the FR to come out of resume properly. The only other thing I did around the same time was to replace uBoot with Qi. To see if a more recent kernel would make a difference, I flashed uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin, but resume problems remain. Any ideas what I can do to sort this out? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
