[Ovmsdev] Can buses stop after some time

[Mark Webb-Johnson]

I think —tags is missing?

I normally ‘git fetch origin —tags as the first step.

Regards, Mark.

> On 11 May 2018, at 7:47 PM, Robin O'Leary <ovmsdev at caederus.org> wrote:
> 
> On Fri, May 11, 2018 at 10:22:00PM +1200, Tom Parker wrote:
>> I synced up with master about a week ago and since then I've seen both can
>> busses stop working. I still see the 12v battery metric changing, but
>> everything that comes from the car stops. Rebooting the module with "module
>> reset" does not seem to fix it, while make app-flash monitor does fix it. I
>> haven't tried make monitor on it's own.
>> 
>> Is anyone else seeing behavior like this?
> 
> Hmm, not quite the same symptoms, but I have also been seeing some
> instability after an update maybe 2--3 days ago, when only the EV bus
> stopped working, so I wonder if this is related.
> 
> Things got much worse after an update from master this morning: now my
> own build consistently crashes.  The first crash I managed to log was
> a stack overflow abort:
> 
> OVMS# event trace on
> Event tracing is now on
> OVMS# ***ERROR*** A stack overflow in task OVMS Vehicle has been detected.
> abort() was called at PC 0x40092f00 on core 1
> 
> Backtrace: 0x40092cec:0x3ffdb580 0x40092ee7:0x3ffdb5a0 0x40092f00:0x3ffdb5c0 0x4008f306:0x3ffdb5e0 0x40090f90:0x3ffdb600 0x40090f46:0x00000000
> 
> Rebooting...
> 
> That was with some of my own changes on top, so I reverted to a clean
> checkout from master and got a different crash:
> 
> Guru Meditation Error: Core  1 panic'ed (StoreProhibited)
> . Exception was unhandled.
> Core 1 register dump:
> PC      : 0x4021292f  PS      : 0x00060d30  A0      : 0x800e7970  A1      : 0x3ffbf7b0
> A2      : 0x3ffdd218  A3      : 0x3ffdb5ec  A4      : 0x3ffbf7e8  A5      : 0x0000000c
> A6      : 0x00000000  A7      : 0xff000000  A8      : 0xbaad5678  A9      : 0x3ffbf790
> A10     : 0x3ffdd218  A11     : 0x40085228  A12     : 0x00000000  A13     : 0x3ff6b000
> A14     : 0x00000000  A15     : 0x00000001  SAR     : 0x00000004  EXCCAUSE: 0x0000001d
> EXCVADDR: 0xbaad5678  LBEG    : 0x40098c89  LEND    : 0x40098cad  LCOUNT  : 0x800e6d0c
> 
> Backtrace: 0x4021292f:0x3ffbf7b0 0x400e796d:0x3ffbf7d0 0x4012218e:0x3ffbf830 0x40122839:0x3ffbfe60 0x400f3440:0x3ffbfeb0 0x400f357d:0x3ffbff40 0x400ee421:0x3ffbff80 0x400eedf1:0x3ffbffb0 0x400eeef1:0x3ffc0060 0x400eef01:0x3ffc0090
> 
> gdb info symbol decodes these as:
> 
> 0x4021292f std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) + 11 in section .flash.text
> 0x400e796d OvmsMetrics::RegisterListener(char const*, char const*, std::function<void (OvmsMetric*)>) + 241 in section .flash.text
> 0x4012218e OvmsServerV2::OvmsServerV2(char const*) + 554 in section .flash.text
> 0x40122839 OvmsServerV2Init::AutoInit() + 101 in section .flash.text
> 0x400f3440 Housekeeping::Init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*) + 548 in section .flash.text
> 0x400f357d std::_Function_handler<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*), std::_Bind<std::_Mem_fn<void (Housekeeping::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (Housekeeping*, std::_Placeholder<1>, std::_Placeholder<2>)> >::_M_invoke(std::_Any_data const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) + 133 in section .flash.text
> 0x400ee421 std::function<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)>::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*) const + 29 in section .flash.text
> 0x400eedf1 OvmsEvents::HandleQueueSignalEvent(event_queue_t*) + 161 in section .flash.text
> 0x400eeef1 OvmsEvents::EventTask() + 37 in section .flash.text
> 0x400eef01 EventLaunchTask(void*) + 5 in section .flash.text
> 
> I tried the stock auto-ota image files, and both 'main' and 'edge' were OK.
> 
> But now I am a bit confused about versions: the stock images both report
> version 3.1.005, but even after updating, my own build reports 3.1.004.
> Is there something else I need to do to fully update?
> 
> $ git pull --rebase upstream master
> From https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3
> * branch            master     -> FETCH_HEAD
> Already up to date.
> Current branch master is up to date.
> $ git submodule update
> $ git describe
> 3.1.004-194-ge3b0765
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev