-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Am Mi 18. Juni 2008 schrieb Andy Green: |> Somebody in the thread at some point said: |> | Andy, |> | |> | I've now confirmed it is from GSM wakeup. If I do not initialize the GSM |> | then the phone never locks up. |> |> EXCELLENT, thanks a lot. |> |> Mike can this plug into the serial resume problems? |> |> How can one provoke GSM wakes then? Although I am in runlevel 3 I do | |>>> Unexpected wake from suspend can be provoked by carrying around the |>>> device, *only* IF registered to GSM. So to me it's very clear some msg |>>> from GSM (probably associated to cell reselect or signal quality) is a |>>> source for unexpected wake. (OM-sw) | | Hmm, seems you don't read my posts :-/
Unexpected wake itself isn't the problem, it is resume crashing that is the issue. GSM interrupts are expected as wake source whenever it feels like it, it shouldn't die in resume then is the point. I asked about it because as I explained I left my phone in suspend all night and it did not wake at all, this is with a SIM and gsmd up. So for whatever reason I didn't get these wakes. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkhZirwACgkQOjLpvpq7dMpm0wCfftXYfOYxcSJZHT1Eg55Jtp3K sa0AnRqS0I7KH9LAehph8/wU10yK3KoR =9mkT -----END PGP SIGNATURE-----
