I have been having a lot of issues with netreg over the last few weeks. But Sunday when I built a new image I noticed some stack sizes had changed between my sdkconfig and support/sdkconfig.default.hw31. (I normally run with basically the support version but with most vehicles turned off and ) I remember a thread I didn't follow closely about the increasing the size of the stack. Anyway, I built and booted that version (3.3.003-71-g5c873b72). And hadn't had a netreg issue for more than a day across my three active modules. Arriving home a few minutes ago I had a fresh netreg issue (the first with this build). But it turned out to maybe be a crash... Last boot was 521 second(s) ago Time at boot: 2022-11-07 22:53:04 PST This is reset #3 since last power cycle Detected boot reason: Crash (12/12) Reset reason: Exception/panic (4) Crash counters: 3 total, 0 early Last crash: abort() was called on core 1 Current task on core 0: IDLE0, 524 stack bytes free Current task on core 1: OVMS NetMan, 512 stack bytes free Backtrace: 0x400891af 0x40089449 0x40261021 0x4023d1a2 0x40236f4a 0x4023893f 0x40247d73 0x40238c0e 0x40238c39 0x40127340 0x401289ec 0x4012a135 0x4012a65b 0x40126b4e 0x4011b053 0x4011b0f1 Version: 3.3.003-71-g5c873b72-dirty/ota_1/main (build idf v3.3.4-848-g1ff5e24b1 Nov 6 2022 10:35:33) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600 Which decodes as: xtensa-esp32-elf-addr2line -e build/ovms3.elf 0x400891af 0x40089449 0x40261021 0x4023d1a2 0x40236f4a 0x4023893f 0x40247d73 0x40238c0e 0x40238c39 0x40127340 0x401289ec 0x4012a135 0x4012a65b 0x40126b4e 0x4011b053 0x4011b0f1 .../esp/openvehicles-xtensa-esp32-elf/components/esp32/panic.c:736 .../esp/openvehicles-xtensa-esp32-elf/components/esp32/panic.c:736 .../esp/openvehicles-xtensa-esp32-elf/components/esp32/hwcrypto/sha.c:272 .../esp/openvehicles-xtensa-esp32-elf/components/mbedtls/port/esp_sha256.c:349 .../esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 .../esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 .../esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_cli.c:3894 .../esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 .../esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 components/mongoose/mongoose/mongoose.c:1701 components/mongoose/mongoose/mongoose.c:1701 components/mongoose/mongoose/mongoose.c:1701 components/mongoose/mongoose/mongoose.c:1701 components/mongoose/mongoose/mongoose.c:1701 main/ovms_netmanager.cpp:1036 main/ovms_netmanager.cpp:1036 diff'ing my sdkconfig against support/sdkconfig.default.hw31 I was surprised to find that CONFIG_MDNS_TASK_STACK_SIZE was missing from mine; I added it back (again), nuked the build directory and rebuilt... and it was missing again: ice 616 % diff sdkconfig support/sdkconfig.default.hw31 | fgrep -v CONFIG_OVMS_VEHICLE 209c209 < CONFIG_SPIRAM_CACHE_WORKAROUND= --- > CONFIG_SPIRAM_CACHE_WORKAROUND=y 667,684c667,685 --- 687,692c688,693 --- 833a835 > CONFIG_MDNS_TASK_STACK_SIZE=3072 What's the story with CONFIG_MDNS_TASK_STACK_SIZE? Craig