[Ovmsdev] Repeated WDT crashes after upgrade to 3.3 with 4G

[Stephen Casner]

"cellular setstate PoweredOff" stopped the crashes.  So it appears
that something in the 4G modem support is running away.

                                                        -- Steve

On Wed, 2 Mar 2022, Stephen Casner wrote:

> I installed version 3.3.001-285 from edge on my OVMS v3.1 unit before
> replacing the 3G modem with a 4G modem.  Upon rebooting with the unit
> still on the bench I noticed that the unit was crashing every three
> minutes with a watchdog timeout:
>
> I (112275) gsm-mux: Start MUX
> I (112285) gsm-mux: Channel #0 is open
> I (112295) gsm-mux: Channel #1 is open
> I (112305) gsm-mux: Channel #2 is open
> I (112315) gsm-mux: Channel #3 is open
> I (112325) gsm-mux: Channel #4 is open
> I (113265) cellular: State: Enter NetWait state
> I (122265) housekeeping: System considered stable (RAM: 8b=81540-82392 32b=12344 SPI=3454300-3456824)
> I (122505) webserver: HTTP GET /
> I (122535) webserver: HTTP GET /apple-touch-icon.png
> I (122555) webserver: HTTP GET /status
> I (123265) ovms-server-v2: Send MP-0 h1,0,*-OVM-DebugCrash,0,2592000,3.3.001-285-g601f2a70/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Feb 20 2022 00:04:30),2,Crash,12,12,2,0,abort(),0,,0x4008ddca 0x4008e065 0x400e9608 0x40084176 ,6,Task watchdog,ticker.1,esp32wifi,0,IDLE0,OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM SIM7600
> I (123295) cellular: Network Registration status: RegisteredRoaming
> I (123295) cellular: Network Provider is: AT&T Hologram
> I (123595) ovms-server-v2: Incoming Msg: MP-0 h1
> I (124265) cellular: State: Enter NetStart state
> I (129845) webserver: HTTP POST /status
> I (129845) webserver: HandleLogin: 'admin' logged in, sid c3bb26091e718ad
> I (129875) webserver: HTTP GET /status
> I (130035) webserver: HTTP GET /menu
> W (178175) websocket: WebSocketHandler[0x3f8b19f0]: job queue overflow detected
> OVMS> E (185265) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
> E (185265) task_wdt:  - IDLE0 (CPU 0)
> E (185265) task_wdt: Tasks currently running:
> E (185265) task_wdt: CPU 0: Tmr Svc
> E (185265) task_wdt: CPU 1: IDLE1
> E (185265) task_wdt: Aborting.
> abort() was called at PC 0x400e9608 on core 0
>
> ELF file SHA256: 2d4b51699f53abce
>
> Backtrace: 0x4008ddca:0x3ffb0aa0 0x4008e065:0x3ffb0ac0 0x400e9608:0x3ffb0ae0 0x40084176:0x3ffb0b00
>
> Rebooting...
>
> I was hoping that when I put the module back into the car with all the
> right inputs on its data cable that this problem would not continue,
> but sad to say the crashes remain the same.  I have not heard about
> this issue for others who have upgraded to 3.3 and 4G.  Any
> suggestions?
>
> Here are a couple of examples of the boot status:
>
> auge1> ssh ovms
>
> Welcome to the Open Vehicle Monitoring System (OVMS) - SSH Console
> Firmware: 3.3.001-285-g601f2a70/ota_1/edge
> Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM SIM7600
>
> OVMS# boot
> Last boot was 152 second(s) ago
> Time at boot: 2022-03-02 14:29:11 PST
>   This is reset #1 since last power cycle
>   Detected boot reason: EarlyCrash (12/12)
>   Reset reason: Task watchdog (6)
>   Crash counters: 1 total, 1 early
>
> Last crash: abort() was called on core 0
>   Backtrace:
>   0x4008ddca 0x4008e065 0x400e9608 0x40084176
>   Event: ticker.1 at esp32wifi 0 secs
>   WDT tasks: IDLE0
>   Version: 3.3.001-285-g601f2a70/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Feb 20 2022 00:04:30)
>
>   Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM SIM7600
> OVMS# packet_write_wait: Connection to 192.168.1.74 port 22: Broken pipe
> auge2> ssh ovms
>
> Welcome to the Open Vehicle Monitoring System (OVMS) - SSH Console
> Firmware: 3.3.001-285-g601f2a70/ota_1/edge
> Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1
>
> OVMS# boot
> Last boot was 76 second(s) ago
> Time at boot: 2022-03-02 14:32:18 PST
>   This is reset #2 since last power cycle
>   Detected boot reason: Crash (12/12)
>   Reset reason: Task watchdog (6)
>   Crash counters: 2 total, 0 early
>
> Last crash: abort() was called on core 0
>   Backtrace:
>   0x4008ddca 0x4008e065 0x400e9608 0x40084176
>   Event: ticker.1 at esp32wifi 0 secs
>   WDT tasks: IDLE0
>   Version: 3.3.001-285-g601f2a70/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Feb 20 2022 00:04:30)
>
>   Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1
> OVMS#
> OVMS# packet_write_wait: Connection to 192.168.1.74 port 22: Broken pipe
>
>                                                         -- Steve