Steve, I haven't seen any lockups like yours recently. A single report on a forum about 4 weeks ago was due to a corrupted config store partition, and I'm not sure that was already with the new WolfSSL code. I've just scanned the current crash reports on my server (updated hourly: https://dexters-web.de/f/firmware/developer/crashreport.csv) for anything WolfSSL related and found only one crash clearly originating within WolfSSL (decoded backtrace attached). That seems to be unlocking a mutex from the wrong task. What's more often now is the abort from the failed assertion in lock_acquire_generic, which seems to be caused by an ESP_LOG call from within a critical section. According to this info… https://github.com/espressif/esp-idf/issues/4412#issuecomment-559208996 …that could be the source for our primary issue of unexplained WDTs. But I think that can only either trigger the dog or trigger an abort immediately, not freeze the module. So… sorry, no clue here. Regards, Michael Am 28.03.21 um 04:31 schrieb Stephen Casner:
On Thu, 25 Mar 2021, Stephen Casner wrote:
Since updating my in-car OVMS with a build from the master branch after my WolfSSL update I've experienced a couple of instances where connectivity from app was lost. The first time I needed a quick resolution so I just reset OVMS. It happened again during the night while charging, and this time I connected to the console to check conditions before resetting. What I found was that the async console was not responding at all. Since I have OVMS configured to drop into gdb on a crash, I should have seen something. I've turned on logging to file to see if that sheds any light. I had another apparent crash today, now with file logging enabled. This occurred while on a drive, so away from the home wifi. The last log messages indicate that the crash happened when bringing up networking via the modem connection:
2021-03-27 12:48:39.688 PDT I (176007218) netmanager: MODEM up (with WIFI client down): starting network with MODEM 2021-03-27 12:48:39.698 PDT I (176007228) time: Starting SNTP client 2021-03-27 12:48:39.708 PDT I (176007238) webserver: Launching Web Server 2021-03-27 12:48:39.708 PDT I (176007238) webserver: Binding to port 80 (http) 2021-03-27 12:48:39.708 PDT I (176007238) webserver: Binding to port 443 (https) 2021-03-27 12:48:39.768 PDT I (176007298) telnet: Launching Telnet Server 2021-03-27 12:48:39.768 PDT I (176007298) ssh: Launching SSH Server 2021-03-27 12:48:39.788 PDT I (176007318) ovms-server-v2: Status: Network is up, so attempt network connection
The last logged activity is to start server v2, and I do have TLS enabled, so this may indicate a problem with the new WolfSSL integration. Does this sound similar to any of the other crashes seen recently?
-- Steve _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26