Hi folks,
I just had my 2.0 Roadster in for its annual service. The OVMSv3
module was crucial in allowing me to monitor the car's health
(battery temperature, location, etc.), and direct the service team
to properly take care of the car. (It was very stressful for both
me and the car...). But that's a different story.
I happened to look at the Web Status page this morning, and notice
that there was a crash of the module during the time when the car
was at Tesla. Nothing in the logs correlates to the time of the
crash, and in hindsight, the work on the car was already complete.
I believe the car was sitting indoors in the shop at the time. This
was on a Saturday, and the shop was closed.
Probably a corner case, but thought I would post the log here in
case it shows something the might need to be fixed. The module is
on the currently released "Main" code.
Greg
Last boot was 371239 second(s) ago
Time at boot: 2019-08-17 03:05:08 PDT
This is reset #3 since last power cycle
Detected boot reason: Crash (12/12)
Crash counters: 3 total, 0 early
Last crash: Alloca exception on core 0
Registers:
PC : 0x40008547 PS : 0x00060c34 A0 : 0x8020536c
A1 : 0x3ffd0350
A2 : 0x000001e0 A3 : 0x8f7b94f1 A4 : 0x00000001
A5 : 0x3ffbb2bc
A6 : 0x00000002 A7 : 0x3ffb802c A8 : 0x80008547
A9 : 0x3ffd0340
A10 : 0x8f7b9524 A11 : 0x00000000 A12 : 0x00000078
A13 : 0x401eb688
A14 : 0x401ec93c A15 : 0x3ffb7fac SAR : 0x0000001f
EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000 LBEG : 0x40098d50 LEND : 0x40098d7e
LCOUNT : 0xffffffff
Backtrace:
0x40008547 0x40205369 0x40203974 0x40205309 0x40201ca5 0x401ef1d9
0x401ef235 0x401ef2df 0x401ec8c9 0x401ec8eb 0x401eedb2 0x401eeec2
0x4008a60c
Version: 3.2.002/ota_1/main (build idf v3.1-dev-2835-g1512694 May
12 2019 22:10:06)
Firmware: 3.2.002/ota_1/main (build idf
v3.1-dev-2835-g1512694 May 12 2019 22:10:06)
Running partition: ota_1
Boot partition: ota_1
Factory image: 3.1.001
OTA_O image: 3.2.001
OTA_1 image: 3.2.002