[Ovmsdev] Modem link-drop crash

[Mark Webb-Johnson]

I’ve been rock solid for three days here, and a couple of network reconnects in that time.

But my tcp/is stack size is 4096bytes. Can you check yours in menuconfig, component config, LWIP, tcp/ip task stack size? My tiT task grows to 2472/4096 bytes.

Regards, Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1.png
Type: image/png
Size: 716410 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20171227/0e2b5294/attachment-0002.png>
-------------- next part --------------


> On 27 Dec 2017, at 7:02 PM, Tom Parker <tom at carrott.org> wrote:
> 
>> On 27/12/17 15:11, Mark Webb-Johnson wrote:
>> 
>> Weird. Looks like the MUX has failed…
> 
> I took it for a short drive with a laptop logging. The network communication was not great with quite often a lot of lag to updates in the app. However I couldn't reproduce exactly the state that I "normally" see. What I did find was a stack overflow with a fairly disappointing stack trace:
> 
> D (1254884) gsm-mux: ProcessFrame(CHAN=2, ADDR=09, CTRL=ff, FCS=45, LEN=51)
> D (1254884) gsm-mux: ChanProcessFrame(CHAN=2, ADDR=09, CTRL=ff, LEN=48, IFP=3)
> D (1254884) SIMCOM ppp rx: 7e 21 45 00 00 28 4f 63 40 00 2d 06 24 44 bc 8a ~!E..(Oc at .-.$D..
> D (1254884) SIMCOM ppp rx: 4b e5 0a aa c7 0f 1a d3 06 b0 75 8a b6 66 00 00 K.........u..f..
> D (1254894) SIMCOM ppp rx: 33 ba 50 10 7b 88 d8 f4 00 00 43 51 7e          3.P.{.....CQ~
> D (1254894) SIMCOM ppp tx: 7e 21 45 00 01 36 00 5b 00 00 ff 06 e0 3d 0a aa ~!E..6.[.....=..
> D (1254894) SIMCOM ppp tx: c7 0f bc 8a 4b e5 06 b0 1a d3 00 00 33 ba 75 8a ....K.......3.u.
> D (1254894) SIMCOM ppp tx: b6 66 50 18 16 60 01 71 00 00 49 78 52 41 58 64 .fP..`.q..IxRAXd
> D (1254894) SIMCOM ppp tx: 57 66 6d 47 64 43 4f 62 6d 75 79 6e 35 45 4e 36 WfmGdCObmuyn5EN6
> D (1254894) SIMCOM ppp tx: 70 46 31 31 7a 64 59 4f 63 33 69 54 2b 38 4e 46 pF11zdYOc3iT+8NF
> D (1254894) SIMCOM ppp tx: 44 48 45 78 37 42 33 34 49 72 54 74 34 47 54 4e DHEx7B34IrTt4GTN
> D (1254894) SIMCOM ppp tx: 71 43 61 6f 51 39 65 4e 55 38 58 6a 33 65 53 69 qCaoQ9eNU8Xj3eSi
> D (1254894) SIMCOM ppp tx: 61 66 4e 54 6a 4f 5a 57 5a 70 62 41 3d 3d 0d 0a afNTjOZWZpbA==..***ERROR*** A
> stack overflow in task tiT has been detected.
> abort() was called at PC 0x40088838 on core 1
> 
> Backtrace: 0x40088720:0x3ffcf170 0x4008881f:0x3ffcf190 0x40088838:0x3ffcf1b0 0x40086571:0x3ffcf1d0 0x4008
> 7b40:0x3ffcf1f0 0x40087afa:0x00000040
> 
> Rebooting...
> ets Jun  8 2016 00:22:57
> 
> Full logs are attached. The first couple of reboots (it didn't connect to the network properly) and the last reboot (it didn't appear to be talking to the network after the second stack overflow) were due to me pressing the button. There was another stack overflow shortly after the one quoted above (look for the timestamps to reset).
> <2017-12-27-2-drive.txt.bz2>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev