Ticket #566 (new defect)
Incoming SMS message is lost and no diagnostic message is output anywhere
| Reported by: | PaulFertser | Owned by: | mickey |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | cornucopia/fsogsm | Version: | milestone5.5 |
| Keywords: | Cc: |
Description
2010-06-14T08:03:36.149968Z [INFO] TiCalypsoModem <4C>: Modem Status changed to FSO_GSM_MODEM_STATUS_SUSPENDED 2010-06-14T08:03:36.155157Z [INFO] DBusServiceDevice <>: Modem suspended successfully 2010-06-14T08:03:59.643650Z [DEBUG] libfsotransport <Serial /dev/ttySAC0@115200 (fd 30)>: read 109 bytes 2010-06-14T08:04:00.866174Z [DEBUG] DBusServiceResource <GSM>: Resuming resource DBusServiceResource... 2010-06-14T08:04:00.935490Z [DEBUG] DBusServiceResource <GSM>: Resuming GSM resource... 2010-06-14T08:04:00.982324Z [DEBUG] FsoGsmGenericWatchDog <P:|KR:true>: onModemStatusChange FSO_GSM_MODEM_STATUS_SUSPENDED -> FSO_GSM_MODEM_STATUS_RESUMING 2010-06-14T08:04:00.984404Z [INFO] TiCalypsoModem <4C>: Modem Status changed to FSO_GSM_MODEM_STATUS_RESUMING 2010-06-14T08:04:00.994054Z [DEBUG] FsoGsmGenericWatchDog <P:|KR:true>: onModemStatusChange FSO_GSM_MODEM_STATUS_RESUMING -> FSO_GSM_MODEM_STATUS_ALIVE_REGISTERED 2010-06-14T08:04:01.073144Z [INFO] TiCalypsoModem <4C>: Modem Status changed to FSO_GSM_MODEM_STATUS_ALIVE_REGISTERED 2010-06-14T08:04:01.107801Z [INFO] DBusServiceDevice <>: Modem resumed successfully 2010-06-14T08:04:01.366238Z [DEBUG] libfsotransport <0710:2>: Wrote '+CSQ'. Waiting for answer... 2010-06-14T08:04:01.448050Z [DEBUG] libfsotransport <Serial /dev/ttySAC0@115200 (fd 30)>: read 32 bytes 2010-06-14T08:04:01.481684Z [INFO] libfsotransport <0710:2>: SRC: "+CSQ" -> [ "+CSQ: 23,99 ", "OK" ] 2010-06-14T08:04:01.551010Z [DEBUG] TiCalypsoModem <4C>: Did receive a valid response for FsoGsmPlusCSQ 2010-06-14T08:04:01.598787Z [DEBUG] libfsotransport <0710:2>: Wrote '+CREG?'. Waiting for answer... 2010-06-14T08:04:01.613148Z [DEBUG] libfsotransport <Serial /dev/ttySAC0@115200 (fd 30)>: read 30 bytes 2010-06-14T08:04:01.616622Z [INFO] libfsotransport <0710:2>: SRC: "+CREG?" -> [ "+CREG: 0,1", "OK" ]
That's with sim_buffers_sms = false, and i never see this message anywhere, apparently.
Change History
Note: See
TracTickets for help on using
tickets.
Stracing helps:
restart_syscall(<... resuming interrupted call ...>) = 1 read(30, "~\r\357\r\n+CMT: ,33\r\n5~~\r\357\r\n07919730071111F10414D04937BD2C7797", 4095) = 57 gettimeofday({1276504987, 848877}, NULL) = 0 write(29, "2010-06-14T08:43:07.848877Z [DEBUG] libfsotransport <Serial /dev/ttySAC0@115200 (fd 30)>: read 57 bytes\n", 104) = 104 poll([{fd=7, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}], 3, -1) = 1 ([{fd=30, revents=POLLIN}]) read(30, "E9D3E6140008016041210483610A00740065007300740033\r\n5~", 4057) = 52 gettimeofday({1276504987, 892364}, NULL) = 0 write(29, "2010-06-14T08:43:07.892364Z [DEBUG] libfsotransport <Serial /dev/ttySAC0@115200 (fd 30)>: read 52 bytes\n", 104) = 104 poll([{fd=7, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}], 3, -1 <unfinished ...>