Warning: Can't synchronize with repository "(default)" (No changeset 96d22ec3fa3ef6de3ea8dc0d7d398adc9aa071cf in the repository). Look in the Trac log for more information.

Ticket #177 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

GSM call release hangs on FSO milestone 3

Reported by: iztok, s52d Owned by: mickey
Priority: major Milestone: milestone5
Component: framework/ogsmd Version: milestone3
Keywords: framewrokd call.Release Cc:

Description

For testing, I tried to generate a lot of unanswered calls. All attemps hangs in an hour (maximum 50 calls), with frameworkd GSM modem access completely dead.

code:

while (i<200):

i += 1

#put real number here, count unanswered calls

xxkcall= gsmcall.Initiate("+1234567890","voice") print xxcall,' ',i time.sleep(15) try:

gsmcall.Release(xxcall) #gsmca..Release(all) does not work

except : pass time.sleep(25)

I tried with modified zhone as well, same result. Once dbus_object.gsm_call_iface.Release(self.xxcall ) was removed, it works fine few hours (with too long time spend calling).

zhone reported:

checking for unsent messages IDLE STATE = IDLE_DIM did not receive any unsent messages: org.freesmartphone.GSM.Device.Failed: command AT+CMGL=2 failed Traceback (most recent call last):

File "ecore.c_ecore_timer.pxi", line 29, in ecore.c_ecore.timer_cb (ecore/ecore.c_ecore.c:789) File "ecore.c_ecore_timer.pxi", line 91, in ecore.c_ecore.Timer._exec (ecore/ecore.c_ecore.c:1357) File "/usr/bin/zhone", line 318, in call

self.xxcall=dbus_object.gsm_call_iface.Initiate("+1234567890","voice" )

File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in call

keywords)

File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 622, in call_blocking

message, timeout)

DBusException: org.freedesktop.DBus.Error.NoReply?: Did not receive a reply. Possible causes include: the remote applicatio checking for unsent messages checking for unsent messages checking for unsent messages checking for unsent messages checking for unsent messages checking for unsent messages did not receive any unsent messages: org.freedesktop.DBus.Error.NoReply?: Message did not receive a reply (timeout by messa checking for unsent messages did not receive any unsent messages: org.freedesktop.DBus.Error.NoReply?: Message did not receive a reply (timeout by messa checking for unsent messages did not receive any unsent messages: org.freedesktop.DBus.Error.NoReply?: Message did not receive a reply (timeout by messa checking for unsent messages did not receive any unsent messages: org.freedesktop.DBus.Error.NoReply?: Message did not receive a reply (timeout by messa checking for unsent messages did not receive any unsent messages: org.freedesktop.DBus.Error.NoReply?: Message did not receive a reply (timeout by messa checking for unsent messages ... repeating forever

zhone was dead (on GSM part), frameworkd/ gsm0710muxd had to be restarted or moko rebooted.

I have not recognized any fix in latest Changelogs indicating this issue was addressed.

Best regards, Iztok, s52d

Change History

comment:1 follow-up: ↓ 2 Changed 5 years ago by mickey

  • Milestone changed from milestone4 to milestone5

Can you retry this without running zhone? Please also submit debug logs.

comment:2 in reply to: ↑ 1 Changed 5 years ago by anonymous

Replying to mickey:

Can you retry this without running zhone? Please also submit debug logs.

Hi! Yes, same. (first guess was they interact somehow), but then I modified zhone in order to have all initialization done properly.

gsmcall.Release(xxcall) just blocks it.

BR Iztok

comment:3 Changed 5 years ago by mickey

We have just released milestone4, please test again with this version.

comment:4 Changed 5 years ago by jluebbe

  • Version set to milestone3

comment:5 Changed 4 years ago by daniel

  • Status changed from new to closed
  • Resolution set to fixed

I think this was actually Bug #211 which was worked around. Since there has been no activity from the reporter for 7 weeks I'm closing this. Please reopen and attach frameworkd DEBUG logs.

I have also managed to make over 500 calls (answered though) when verifying #211 fix.

Note: See TracTickets for help on using tickets.