Random blocking issue with getaddrinfo function

RE: Random blocking issue with getaddrinfo function

Hakon — Wed, 29 May 2024 12:25:45 GMT

That's weird. Maybe it's because the log contains no packet transmissions, just internal modem activity? Are you sure that you have established a connection to a remote host when the trace was done?

RE: Random blocking issue with getaddrinfo function

V1incentC — Wed, 15 May 2024 15:38:47 GMT

I managed to capture the trace with rtt like in this issue:
How to capture nrf9160 modem traces using RTT?

But when I try to open it in wireshark I get this error:

devzone.nordicsemi.com/.../modemtraces_5F00_stuck_5F00_in_5F00_addressinfo.bin

RE: Random blocking issue with getaddrinfo function

Hakon — Tue, 14 May 2024 12:17:11 GMT

Yes, it just enters idle mode. I read about it, and it should return with a timeout if the DNS server is not reached. So this behavior is not expected. Can you do a modem trace and reproduce the issue?

RE: Random blocking issue with getaddrinfo function

V1incentC — Tue, 07 May 2024 18:01:47 GMT

I caught it at this part:
    /* Enter low power state */
   _sleep_if_allowed wfi

   /*
   * Clear PRIMASK and flush instruction buffer to immediately service
   * the wake-up interrupt.
   */
   cpsie   i
   isb

   bx   lr

Then I let the program run and paused it a few times and it mostly jumps around timeout.c, thread.c and timer.c.

These are the last lines on the serial log:
[00:04:01.572,967] <inf> livehub_api: lcd:Server ping

[00:04:01.572,998] <inf> http_client: Sending HTTP POST request from server_sender_thread

[00:04:01.573,364] <inf> http_client: Getting address info

[00:04:03.166,351] <inf> modem_control: RRC mode: Idle

As you can see in my http_client_send_request function I posted the execution stops at getaddrinfo(), according to LOG prints.

RE: Random blocking issue with getaddrinfo function

Hakon — Tue, 07 May 2024 15:39:40 GMT

Hello,

have you tried running it in the debugger to see what part of the code it hangs at?