reason: MemoryProtectionFault mmarValid daccViol

dc42

I can see two faults in that log, both coming from the 6HC: a watchdog timeout that happened shortly before you ran that M122 command, and a memory protection violation that happened on 24 January at 17:45. Were you already running firmware 3.2 on 24 January?

jrockland

@dc42 yess, but the board was on a different machine.
I start having those memory issue since I updated to 3.2 on most of my machine now.
Im getting some sd card ready to go stand alone as plan A, plan B is to go back to 3.1...
But as 3.2 solved soo many issues with the 3hc ill try to keep 3.2 working as long as possible.
The machine in question where that board was the 24 was also running on a pi4b.. if it help..

By chance my duet machines arent our production machines, just dummy's machines where I test parts prototypes. So it wont kill me if they are stopping for no reason.

jrockland

@dc42 WAIT..... Your telling me it is that easy to get the stand alone mode working, and that much faster while using the same user interface ???? Why did I bother looking for rasp bi boards all over the place and why was I trying so hard to get it to work when it work soo much better without it ???

Stand alone all the way !!

dc42

@jrockland, if you get any more unexpected resets, please post the M122 reports taken after the reset.

jrockland

@dc42 had the same error again, I went back to 3.1.1 and Ill give a try

dc42

Did you get another M122 report?

jrockland

@dc42 m122.txt
same error on 3.1.1... Never had that error before last week and now it is happening on all my duet printers.. that make no sense..

jrockland

@jrockland said in reason: MemoryProtectionFault mmarValid daccViol:

@dc42 m122.txt
same error on 3.1.1... Never had that error before last week and now it is happening on all my duet printers.. that make no sense..

****All the printers using 3HC ext boards. not on the one who don't have ext.

jrockland

@dc42 im using mostly SanDisk Ultra 32GB microSDHC UHS-I sd cards, could it be the problem ?

jrockland

@dc42 moved back to 3.2, and still have the same error coming back. here is the latest m122console.txt