Re: [Debian/gta02v5] zhone suspend not working anymore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | It isn't the idleclock-around-suspend patch. I tested that a while ago on FSO | without any suspend/resume issues. Sorry but I think we find suspend / resume is so sensitive to even small code changes build by build that there is no rhyme or reason to this at the moment. Literally printk()s in or out is changing behaviours. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjhJGoACgkQOjLpvpq7dModdQCaAkTFf7Fyt6Qiu65NYpgZwKNn fKQAni1yrUMFo2qimyg/+2e0+LQ3XEOD =LPwW -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian/gta02v5] zhone suspend not working anymore
On Monday 29 September 2008 17:38:39 Thomas White wrote: > On Mon, 29 Sep 2008 16:52:48 +0200 > > Fox Mulder <[EMAIL PROTECTED]> wrote: > > Since over a week suspend isn't working anymore for me. > > Perhaps this could be related to the recent re-opening of ticket #80: > https://docs.openmoko.org/trac/ticket/80 - which reports problems with > the wakeup reason stuff? > > I was previously using a (self-compiled) kernel built from the 'stable' > git.openmoko.org kernel branch, revision a1e97c611. Last night I > updated to a kernel built from the latest revision (968c41d0c), and I > had similarly serious suspend problems (didn't seem to wake up at > all). As far as I know, the latest OM kernel is still a1e97c611. > > So, on the (tenuous) assumption that all the problems described here are > the same regression, I suspect either "fix-one-mmc-race.patch" or > "fix-glamo-idleclock-around-suspend.patch" of breaking things. These > are the two commits between a1e97c611 and the revision described in > ticket #80 as causing trouble (ca19d1564). It isn't the idleclock-around-suspend patch. I tested that a while ago on FSO without any suspend/resume issues. Sander ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian/gta02v5] zhone suspend not working anymore
On Mon, 29 Sep 2008 16:52:48 +0200 Fox Mulder <[EMAIL PROTECTED]> wrote: > Since over a week suspend isn't working anymore for me. Perhaps this could be related to the recent re-opening of ticket #80: https://docs.openmoko.org/trac/ticket/80 - which reports problems with the wakeup reason stuff? I was previously using a (self-compiled) kernel built from the 'stable' git.openmoko.org kernel branch, revision a1e97c611. Last night I updated to a kernel built from the latest revision (968c41d0c), and I had similarly serious suspend problems (didn't seem to wake up at all). As far as I know, the latest OM kernel is still a1e97c611. So, on the (tenuous) assumption that all the problems described here are the same regression, I suspect either "fix-one-mmc-race.patch" or "fix-glamo-idleclock-around-suspend.patch" of breaking things. These are the two commits between a1e97c611 and the revision described in ticket #80 as causing trouble (ca19d1564). In either case, when I get the chance, I intend to do a git bisect to isolate my own problems between revision a1e97c611 and the current head. Hoping that this is at least vaguely helpful, Tom -- Thomas White Department of Materials Science and Metallurgy Electron Microscopy Group (PhD Student) University of Cambridge / Downing College ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Debian/gta02v5] zhone suspend not working anymore
Since over a week suspend isn't working anymore for me. I use the latest fso kernel [1] and latest updates for debian until 29.9.08. When i take a look at the zhone.log file everything seems to be fine. After pressing the power button for 1 sec my neo goes into sleep [2]. But than i can't wake it up anymore. Pressing the power button does nothing at all. But suspend was working fine a short while ago. So maybe the actual kernel or some updates did break it. I tried to wake it up with calling my neo and it rings at the callers end but nothing happens at my neo. The only way to get it back is to remove the battery and reboot it. After that i tried it with the latest om kernel and suspend/resume works what was really surprising. But the behaviour when calling the neo when in suspend is also quite surprising. The neo wakes up and it rings and vibrates but zhone doesn't show any caller. After about 30 seconds zhone displays the caller and accept/reject buttons. But pressing any of these buttons does nothing. Even after the caller hung up my neo was happily going on with the ringing and vibrating. Only fso-frameworkd restart stopt the ringtone but not the vibrating. :) This is quite some strange thing i experienced with the latest kernels and zhone. Is there any way to make suspend/resume and phoning work together? Ciao, Rainer [1] uImage-2.6.24+r7+gitrca19d156400f817960efe0d14680324b2ea34171-r7-om-gta02.bin [2] 2008-09-29 13:48:41,047 INFO INPUT EVENT = POWER, pressed, 0 2008-09-29 13:48:42,022 INFO INPUT EVENT = POWER, held, 1 2008-09-29 13:48:42,078 INFO INPUT EVENT = POWER, released, 0 2008-09-29 13:48:42,405 INFO ENTERING SUSPEND ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
