The following script reliably puts the ovms into a boot loop: vfs mkdir /store/events vfs mkdir /store/events/system.start vfs rm /store/events/system.start/startmeup vfs append "log level debug" /store/events/system.start/startmeup vfs append "server v2 start" /store/events/system.start/startmeup Press the reset button and it loops with the log below. It can be fixed by "make erase_flash flash" but this obviously erases your config. If you swap the order of the two commands in the script, or if the script only contains on or other of the commands then it doesn't boot loop. ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT) configsip: 156795334, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:4456 load:0x40078000,len:0 ho 12 tail 0 room 4 load:0x40078000,len:12988 entry 0x40078d14 I (168) ovms_main: Set default logging level for * to WARN Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console OVMS > ***ERROR*** A stack overflow in task Housekeeping has been detected. abort() was called at PC 0x4008a824 on core 1 0x4008a824: vApplicationStackOverflowHook at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:572 Backtrace: 0x4008a70c:0x3ffcea70 0x4008a80b:0x3ffcea90 0x4008a824:0x3ffceab0 0x4008791c:0x3ffcead0 0x4008921c:0x3ffceaf0 0x400891d2:0x632e6769 0x4008a70c: invoke_abort at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:572 0x4008a80b: abort at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:572 0x4008a824: vApplicationStackOverflowHook at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:572 0x4008791c: vTaskSwitchContext at /home/ubuntu/esp/esp-idf/components/freertos/./tasks.c:4837 0x4008921c: _frxt_dispatch at /home/ubuntu/esp/esp-idf/components/freertos/./portasm.S:406 0x400891d2: _frxt_int_exit at /home/ubuntu/esp/esp-idf/components/freertos/./portasm.S:206 Rebooting... ets Jun 8 2016 00:22:57