nRF9160 intermittent LTE-M connection loss, strange modem traces

We are seeing LTE-M communication dropouts on the nRF9160 with firmware 1.3.6

This has occurred several times with multiple devices. The devices are registered on the same cell, but the connection problems don't happen at the same time.

In each case, a previously established, long-lived TCP/IP connection stalls (no more incoming data). Our application detects this and tries to re-open the connection. This requires a DNS lookup (getaddrinfo) which repeatedly fails with EAI_SYSTEM errno=116 (timeout).

We have enabled LTE and IP modem traces. I have attached the textual log files we recorded which contain the modem traces as hexdumps, among other information. I have converted the modem traces to the binary format, which I also attached.

What is strange is that the Cellular Monitor tool fails to convert the problematic time range.
There are about a thousand trace packets in each file, but only fewer than 100 show up in Wireshark. This seems to indicate some kind of abnormal behaviour of the modem. Is this a known issue?

/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-211f2da449e54ea4920286dd12ad3125/trace3.bin

/cfs-file/__key/communityserver-discussions-components-files/4/2654.trace2.log

/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-211f2da449e54ea4920286dd12ad3125/trace2.bin

/cfs-file/__key/communityserver-discussions-components-files/4/3225.trace1.log

/cfs-file/__key/communityserver-discussions-components-files/4/0523.trace3.log

/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-211f2da449e54ea4920286dd12ad3125/trace1.bin

We are aware that a newer firmware version 1.3.7 exists, but we are currently shipping 1.3.6 in our products. The release notes for 1.3.7 don't seem to contain anything related to this, but I may be mistaken.

Parents
  • Hello, 

    Thanks for providing the attachments. Unfortunately the modem traces, i.e. .bin files, do not have have any usable data. I am not able to open in Wireshark from the Cellular Monitor. Can you please retry?

    Looking at the trace log, e.g. trace1.log I see the following issue multiple times: srv_lte: getaddrinfo error: EAI_SYSTEM errno=116 indicating there was a DNS issue where the query timed out.

    What version of the nRF Connect SDK are you developing in? 

    Kind regards,
    Øyvind

  • Hi Øyvind,

    Thanks for the quick response. It looks like the *.bin files got corrupted when I created or edited the post. I'll attach all the files as a zip archive.

    1537.trace.zip

    We are using version 2.8.0 of the nRF Connect SDK.

    Best regards,
    --Stephan Walter

Reply Children
Related