Marcel <tan...@googlemail.com> writes: > Am Donnerstag, 6. August 2009 14:49:21 schrieb Paul Fertser: >> Marcel <tan...@googlemail.com> writes: >> >> > That _normally_ works fine for me, too, only ffalarms screws >> >> > suspending. There's indeed some more output about suspending, but >> >> > I cannot find something useful in that messages... Only... What >> >> > about line 36, it's changing the modem from "suspended" to >> >> > "suspending", shouldn't it be some kind of "awake" before being >> >> > "suspending"? >> >> >> >> You might want to post your full log somewhere for more analysis. >> > >> > Oh dammit, I forgot to paste the link... >_< >> > Here it is: http://pastebin.ca/1520436 >> >> This first "TIMEOUT 'AT+CTZU=0' => ???" already fucks up everything :( >> >> AFAIK, FSO handling of such situations is not robust and moreover >> there's even a known case where such a timeout will occur (iirc after >> %CSQ unsol reply the modem can go to sleep immediately and so >> frameworkd command can easily fail as it wakes up the modem explicitly >> only after some time from the last communication passed). > > But what puzzles me is that it happens after I had an ffalarm / atd event. > Seems like fso gets confused by... "not-self-triggered" wakeup. My theory > so far.
The wakeup is _always_ hardware-triggered. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community