Your message dated Fri, 11 Nov 2011 18:09:36 +0100
with message-id <20111111170936.GA4926@earth.universe>
and subject line wontfix
has caused the Debian Bug report #647277,
regarding fso-gsmd: RequestResource GSM fails with "Can't open the modem"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
647277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fso-gsmd
Version: 0.5.0+git20110916-1
Severity: important
Dear Maintainer,
I'm running Debian/Sid on the OpenMoko FreeRunner GTA02.
The first time I request the GSM resource, it works well.
Then I release the resource to save battery; after that,
every GSM resource request will fail leaving the resource
unusable. I have to restart fsogsmd to recover.
Here it is the mdbus2 chat I use:
org.freesmartphone.ousaged /org/freesmartphone/Usage
org.freesmartphone.Usage.RequestResource GSM
()
org.freesmartphone.ousaged /org/freesmartphone/Usage
org.freesmartphone.Usage.ReleaseResource GSM
()
org.freesmartphone.ousaged /org/freesmartphone/Usage
org.freesmartphone.Usage.RequestResource GSM
org.freesmartphone.Resource.UnableToEnable: Could not enable resource 'GSM':
GDBus.Error:org.freesmartphone.Resource.UnableToEnable: Can't open the
modem.
The GSM power is turned-off on ReleaseResource, then it remains
turned-on despite the RequestResource failed.
Here it is the fsogsmd.log:
### RequestResource GSM ###
[DEBUG] DBusServiceResource <GSM>: Enabling GSM resource...
[DEBUG] TiCalypsoModem <4C>: Opening the modem device...
[DEBUG] fsogsmd : GLib <fsogsm.lowlevel_openmoko>: plugin.vala:81: --- while
loop ENTER; i = 1
[DEBUG] TiCalypsoModem <4C>: Will open 4 channels...
[WARN] libfsotransport <fd -1>: Create called on already existing transport.
Ignoring
[INFO] libfsotransport <0710:2>: URC: [ "AT-Command Interpreter ready" ]
[DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited
'AT-Command Interpreter ready', ''
[DEBUG] TiCalypsoModem <4C>: Congratulations Madam, it's a channel!
### ReleaseResource GSM ###
[DEBUG] DBusServiceResource <GSM>: Disabling resource DBusServiceResource...
[DEBUG] DBusServiceResource <GSM>: Disabling GSM resource...
[DEBUG] TiCalypsoModem <4C>: Closing the modem device...
[DEBUG] FsoGsmGenericWatchDog <P:|KR:false>: onModemStatusChange
FSO_GSM_MODEM_STATUS_ALIVE_SIM_READY -> FSO_GSM_MODEM_STATUS_CLOSING
[INFO] TiCalypsoModem <4C>: Modem Status changed to
FSO_GSM_MODEM_STATUS_CLOSING
[INFO] libfsotransport <0710:2>: SRC: "@POFF" -> [ "OK" ]
[DEBUG] FsoGsmGenericWatchDog <P:|KR:false>: onModemStatusChange
FSO_GSM_MODEM_STATUS_CLOSING -> FSO_GSM_MODEM_STATUS_CLOSED
[INFO] TiCalypsoModem <4C>: Modem Status changed to FSO_GSM_MODEM_STATUS_CLOSED
[INFO] DBusServiceDevice <>: Modem closed successfully
### RequestResource GSM ###
[DEBUG] DBusServiceResource <GSM>: Enabling GSM resource...
[DEBUG] TiCalypsoModem <4C>: Opening the modem device...
[DEBUG] fsogsmd : GLib <fsogsm.lowlevel_openmoko>: plugin.vala:81: --- while
loop ENTER; i = 1
[DEBUG] TiCalypsoModem <4C>: Will open 4 channels...
[ERROR] libfsotransport <0710:2>: Can't allocate channel #2 from MUX: Channel 2
is already taken.
[ERROR] TiCalypsoModem <4C>: Can't open main channel; open returned false
[ERROR] DBusServiceDevice <>: Can't open modem
[DEBUG] DBusServiceResource <GSM>: Disabling resource DBusServiceResource...
[DEBUG] DBusServiceResource <GSM>: Disabling GSM resource...
[INFO] DBusServiceDevice <>: Modem closed successfully
I have to power down the GSM using omhacks, kill fsogsmd and restart
it; in this way I can re-open the GSM resource.
Let me know if I can help in debugging.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: armel (armv4tl)
Kernel: Linux 2.6.34-20101212.git049b71de
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages fso-gsmd depends on:
ii libc6 2.13-21
ii libfso-glib0 2011.06.01.1-1
ii libfsobasics0 0.9.99+git20110804-1
ii libfsoframework0 0.8.2+git20110805-2
ii libfsoresource0 0.9.0+git20110805-1
ii libfsotransport0 0.9.8+git20110805-1
ii libgee2 0.6.1-3
ii libglib2.0-0 2.28.8-1
ii libgsm0710mux0 0.9.2+git20110805-1
ii libnl2 2.0-1
ii multiarch-support 2.13-21
Versions of packages fso-gsmd recommends:
ii fso-gsmd-openmoko [fso-gsmd-platform] 0.5.0+git20110916-1
fso-gsmd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 647277 wontfix
thanks
Hi,
This is the answer from upstream developers [0]:
> The Problem is a calypso one. It can't break out of MUX mode
> without powercycling (which will only happen when restarting
> fsogsmd). That is what Mickey told me in IRC some month ago.
For now I will close this bug and tag it as wontfix. Feel free to
reopen it, if you find somebody who is interested in - and has the
time - to work around this hardware limitation.
-- Sebastian
[0]
http://lists.linuxtogo.org/pipermail/smartphones-userland/2011-November/003097.html
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
pkg-fso-maint mailing list
pkg-fso-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
