Re: unreliable resume

2009-12-30 Thread Michael 'Mickey' Lauer
Ok, analyzed your logs. The problem starts w/: 2009.12.15 16:12:36.802 frameworkd.resource DEBUGprocessing command 'resume' for resource 'ogsmd.device.Device at /org/freesmartphone/GSM/Device at 0x455830' (present status=suspending) For some reason it got a new command while it was still in

Re: unreliable resume

2009-12-30 Thread Sebastian Krzyszkowiak
On 12/30/09, Michael 'Mickey' Lauer mic...@vanille-media.de wrote: Ok, analyzed your logs. The problem starts w/: 2009.12.15 16:12:36.802 frameworkd.resource DEBUGprocessing command 'resume' for resource 'ogsmd.device.Device at /org/freesmartphone/GSM/Device at 0x455830' (present

Re: unreliable resume

2009-12-30 Thread Timo Jyrinki
2009/12/14 arne anka openm...@ginguppin.de: i still experience more or less reliable problems with phone functionality (at least, that's what i notice). i resume the fr and i can't make calls. This is why I still use Debian testing's versions of fso-frameworkd and gsm0710muxd, like I reported

unreliable resume

2009-12-14 Thread arne anka
i still experience more or less reliable problems with phone functionality (at least, that's what i notice). i resume the fr and i can't make calls. looking at zhone's cell info tab show only two lines with n/a -- no matter, how long i wait, no dice. furthermore, when suspending i see the

Re: unreliable resume

2009-12-14 Thread Michael 'Mickey' Lauer
Hi Arne, due to the messages in the log (resource can not be set to resume, state resuming or something to that effect) I'd be interested in the complete message and the +-1000 lines surrounding it. - who is responsible to resume the resource? The suspend/resume path is: 1.) Someone