2.4 450 AP - MPU Data Violation Error

We recently noticed MPU Data Violation error on our 2.4 APs on the eventlog which causes the SMs to drop and reconnect frequently  2.4 APs are running v16.0.1, Board Type P12.    Any idea what's causing it?

03/02/2020 : 22:54:10 MDT : :
Q 0x572cc8
Size: 255, CurrentSize: 255, PutIndex: 33, GetIndex 33, pHiQ: 0x0, HiQPut: 0, End: 255
Array Pointers:
0x0086cb60: 02348000 0287e800 02719800 026af000
0x0086cb70: 025d7800 02811800 02644000 026fb000
0x0086cb80: 027ad800 02786800 02371800 0277b800
0x0086cb90: 024ba000 02316800 023d9800 025e9800
0x0086cba0: 02833000 02746800 0258a800 0242a000
0x0086cbb0: 025cb800 02537000 025f1800 025a6800
0x0086cbc0: 02667800 025e9000 02386800 024d7000
0x0086cbd0: 026b3000 02590800 02610000 027cc000
0x0086cbe0: 027c3800 0265e000 023ac000 0256e800
0x0086cbf0: 02494000 0233f000 02617800 02751000
0x0086cc00: 02662000 02502800 027ca000 024d9000
0x0086cc10: 023c1800 02723000 023f6800 02391800
0x0086cc20: 022df800 0258c000 022b4000 02717800
0x0086cc30: 026b9800 023d7800 02539000 023d1000
0x0086cc40: 022dc000 0274b000 026ec000 02708800
0x0086cc50: 02801000 0255f000 024d3000 02554000
0x0086cc60: 022cc800 0242e000 0246a000 02328800
0x0086cc70: 0257b000 02703800 02701000 024fa800
0x0086cc80: 023c4800 0235f000 0269a000 02744000
0x0086cc90: 026a1800 02842800 025ea800 0287a000
0x0086cca0: 022c4000 02837800 026b1000 026a4800
0x0086ccb0: 023a3000 025d4000 0250c000 02443800
0x0086ccc0: 0243d800 025ce800 02859800 0250a800
0x0086ccd0: 025b9800 025c8800 02475800 02771000
0x0086cce0: 0236b000 02482800 022e6800 02518800
0x0086ccf0: 02803000 0230f800 02476800 023fb800
0x0086cd00: 02842000 026bd000 0270c000 0281f000
0x0086cd10: 0274f800 02623800 0286f000 02640800
0x0086cd20: 0272e800 027c2000 024aa800 02429800
0x0086cd30: 0285c000 0249f800 0285d800 024f4800
0x0086cd40: 026a5800 0270c800 0231a000 02635000
0x0086cd50: 02542800 02857000 02760000 0279c800
0x0086cd60: 025bd000 02753800 023c3000 023b1000
0x0086cd70: 0230b800 023d7000 023ca000 02543800
0x0086cd80: 02768800 02662800 025df800 0262b000
0x0086cd90: 02450800 025f6000 02408800 0264a800
0x0086cda0: 0234a800 023a9000 023cd000 023e9000
0x0086cdb0: 027a3800 02752000 024e3800 02540000
0x0086cdc0: 0285d000 02828800 0283c800 02844000
0x0086cdd0: 02327000 02846000 02424000 0270f000
0x0086cde0: 027e2800 0259c800 022b8800 024c1000
0x0086cdf0: 026c5800 02598800 02347800 02582000
0x0086ce00: 02338800 02590000 02556800 026f0000
0x0086ce10: 02374800 026ae000 02855000 023fd800
0x0086ce20: 026d9000 027bc000 024b2800 0251b000
0x0086ce30: 0283c000 0280a000 025bc800 02726800
0x0086ce40: 02322800 027bf000 023d6000 02778800
0x0086ce50: 023e9800 02487800 02369800 024be000
0x0086ce60: 0253e000 0267a000 02828000 02870000
0x0086ce70: 0276d000 02426800 024f0000 024ca000
0x0086ce80: 0262b800 0241a800 02735000 025f1000
0x0086ce90: 02493000 022bb800 027d4800 022fa000
0x0086cea0: 025be000 025bf800 023ef000 0283e000
0x0086ceb0: 02736800 022ac000 026cd000 02343800
0x0086cec0: 0238d800 024ed000 02710000 024d5000
0x0086ced0: 023ec000 0261e000 02358000 022ad800
0x0086cee0: 02457800 02874000 025e6000 023eb000
0x0086cef0: 022f7000 026cb800 02413800 02465800
0x0086cf00: 02325000 02531000 0249a800 024b3000
0x0086cf10: 025a8800 02804000 024ad000 02877000
0x0086cf20: 02611000 02449000 0262e800 025e8000
0x0086cf30: 024ee800 0264c000 02817000 024da800
0x0086cf40: 02755000 02521000 02546000 02837000
0x0086cf50: 0239a000 02323800 022b7000
03/02/2020 : 22:54:10 MDT : :MPU DATA VIOLATION: addr: 0x000f589c, inst: 0x90000015, code: 17, badaddr: 0x00000000, retaddr: 0x000f68a4
12/31/2015 : 18:00:00 MDT : :
01/01/2016 : 00:00:00 UTC : :Time Set

kent,

I'm not sure from this log if that is something that we have fixed or not. Could you send me the http://<IP>/engineering.cgi from the radio to charlie.galik@cambiumnetworks.com?

I'd highly recommend 16.0.1.1 bug fix release over 16.0.1.

Also 16.1.1.1 is expected to be official early next week, where I would love it if you would try that out.

Charlie

Thank you Charlie for your reply. Issue seems to stop after a reboot and it did not reoccur. We do have a plan to upgrade to 16.0.1.1 but not as of the moment. 

Thanks