bsdlib recoverable error: 3

[perf]

This error always stop the "mqtt_simple" application.

I have tried modem versions 1.0.1 and 1.1.0, SDK versions v1.0.0 and v1.1.0 and added this code to system_nrf9160.c - but nothing seem to fix this bug.

I am running towards a local mqtt server that I have had in operation for years.

    SystemCoreClockUpdate();
	
	#if defined(NRF_TRUSTZONE_NONSECURE)
        *(volatile uint32_t *)0x40005C04 = 0x02ul; 
    #endif
	
}

Typically, the code runs for a while - completing fine a few transactions, and then suddenly error 3 stops it.

The topic the application subscribes to is updated every 5 minutes.

Could it be related to the PSM mode failure with iBasis SIM in Telenor network? 

Regards Per

Terminal output below:

***** Booting Zephyr OS v1.14.99-ncs2 *****
The MQTT simple sample started
LTE Link Connecting ...
LTE Link Connected!
IPv4 Address found 84.52.247.193
[mqtt_evt_handler:166] MQTT client connected!
Subscribing to: r35/temperaturer/ute/UteTemp len 28
[mqtt_evt_handler:216] SUBACK packet id: 1234
[mqtt_evt_handler:181] MQTT PUBLISH result=0 len=3
Received: 0.7
Publishing: 0.7
to topic: r35/iotpubPer/topic len: 19
[mqtt_evt_handler:206] PUBACK packet id: 38950
[mqtt_evt_handler:181] MQTT PUBLISH result=0 len=3
Received: 1.4
Publishing: 1.4
to topic: r35/iotpubPer/topic len: 19
[mqtt_evt_handler:206] PUBACK packet id: 54806
[mqtt_evt_handler:181] MQTT PUBLISH result=0 len=3
Received: 0.8
Publishing: 0.8
to topic: r35/iotpubPer/topic len: 19
[mqtt_evt_handler:206] PUBACK packet id: 4317
[mqtt_evt_handler:181] MQTT PUBLISH result=0 len=3
Received: 0.7
Publishing: 0.7
to topic: r35/iotpubPer/topic len: 19
[mqtt_evt_handler:206] PUBACK packet id: 42946
bsdlib recoverable error: 3

[perf]

I have some additional observations that are rather strange:

The application may run flawlessly for some rounds of sub/pub's, then this error 3 suddenly hits. After that, there are no further output on the terminal emulator (Termite) but the application continues to act on publications and publish its value. The application stops mysteriously (and quietly) after some further sub/pub rounds. I can see this because I have an mqtt client that monitors the publications of the server and the r35/iotpubPer/topic updates after r35/temperaturer/ute/UteTemp is updated.

How can this error 3 shut down printk output?