Re: Re:

On Thu, 2013-05-16 at 18:31 +0200, Aleksander Morgado wrote:
On 05/16/2013 06:21 PM, Dan Williams wrote:
Would love to see those logs, wherever they are :)

OMG, I'm sure I had attached the log file (also I thought I had
written the email subject too) :-S

Hopefully this time arrives the attachment.

So, yeah, seen this already I think:

May 16 10:42:21 localhost ModemManager[20771]: <debug>
[1368693741.528368] [mm-iface-modem-messaging.c:762]
load_initial_sms_parts_ready(): Couldn't load SMS parts from storage
'sm': 'Couldn't list messages: QMI protocol error (17): 'MissingArgument''
I've seen that on the ADU-960s with 2010-era QMI:

revision: 'M9600B-SCAQDAFD-1.0.32T  1  [Aug 17 2010 02:00:00]'

ModemManager[9163]: [/dev/cdc-wdm1] QMI Device supports 8 services:
ModemManager[9163]: [/dev/cdc-wdm1]    ctl (1.4)
ModemManager[9163]: [/dev/cdc-wdm1]    wds (1.9)
ModemManager[9163]: [/dev/cdc-wdm1]    dms (1.3)
ModemManager[9163]: [/dev/cdc-wdm1]    nas (1.2)
ModemManager[9163]: [/dev/cdc-wdm1]    qos (1.2)
ModemManager[9163]: [/dev/cdc-wdm1]    wms (1.2)
ModemManager[9163]: [/dev/cdc-wdm1]    pds (1.3)
ModemManager[9163]: [/dev/cdc-wdm1]    uim (1.4)

ModemManager[9163]: <debug> [1368720595.009652] [mm-broadband-modem-qmi.c:5847] 
messaging_check_support(): Messaging capabilities supported by this modem
ModemManager[9163]: <debug> [1368720595.009808] [mm-iface-modem-messaging.c:1113] 
load_supported_storages_ready(): Supported storages loaded:
ModemManager[9163]: <debug> [1368720595.009868] [mm-iface-modem-messaging.c:1114] 
load_supported_storages_ready():   mem1 (list/read/delete) storages: 'sm, me'
ModemManager[9163]: <debug> [1368720595.009934] [mm-iface-modem-messaging.c:1115] 
load_supported_storages_ready():   mem2 (write/send) storages:       'sm, me'
ModemManager[9163]: <debug> [1368720595.009996] [mm-iface-modem-messaging.c:1116] 
load_supported_storages_ready():   mem3 (reception) storages:        'sm, me'

ModemManager[9163]: [/dev/cdc-wdm1] Sent message (translated)...
<<<<<< QMUX:
<<<<<<   length  = 20
<<<<<<   flags   = 0x00
<<<<<<   service = "wms"
<<<<<<   client  = 1
<<<<<< QMI:
<<<<<<   flags       = "none"
<<<<<<   transaction = 2
<<<<<<   tlv_length  = 8
<<<<<<   message     = "List Messages" (0x0031)
<<<<<< TLV:
<<<<<<   type       = "Message Mode" (0x12)
<<<<<<   length     = 1
<<<<<<   value      = 01
<<<<<<   translated = gsm-wcdma
<<<<<< TLV:
<<<<<<   type       = "Storage Type" (0x01)
<<<<<<   length     = 1
<<<<<<   value      = 00
<<<<<<   translated = uim
ModemManager[9163]: [/dev/cdc-wdm1] Received message...
  length = 20
  data   = 01:13:00:80:05:01:02:02:00:31:00:07:00:02:04:00:01:00:11:00
ModemManager[9163]: [/dev/cdc-wdm1] Received message (translated)...
  length  = 19
  flags   = 0x80
  service = "wms"
  client  = 1
  flags       = "response"
  transaction = 2
  tlv_length  = 7
  message     = "List Messages" (0x0031)
  type       = "Result" (0x02)
  length     = 4
  value      = 01:00:11:00
  translated = FAILURE: MissingArgument
ModemManager[9163]: <debug> [1368720630.557661] [mm-iface-modem-messaging.c:762] 
load_initial_sms_parts_ready(): Couldn't load SMS parts from storage 'sm': 'Couldn't list messages: QMI 
protocol error (17): 'MissingArgument''

The error happens for all storages.

What's bizarre is that a Gobi 1k with really, *really* old QMI (2009)
works just fine with the exact same command sequence.  So it can't
really be related to old vs. new QMI version, just that some devices
with some versions of WMS perhaps want a specific TLV?

The only TLV that we don't pass to List Messages is the one specifying
which message tags you want to query (e.g. I want only
QMI_WMS_MESSAGE_TAG_TYPE_MT_READ). When that TLV is not set, the modem
should return all messages. Maybe the modem really wants that TLV, and
if so, we would need to loop querying for all 4 known tags for each
message store.

Yeah, that's the problem.  Setting that TLV makes the command return
"Success" on the ADU960s, but I'm not able to actually *see* any
messages using MT_READ or MT_NOT_READ.  Also, when sending an SMS, all I
get from the ADU960s is the "Transfer Route MT Message" indication,
which MM currently ignores.  That data looks like it contains the PDU,
right?  Maybe this firmware simply can't store the message to NV so it
indicates it to the host and then discards it, and that's why it doesn't
show up in SM/NV storage?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]