reason: MemoryProtectionFault mmarValid daccViol

jrockland

Latest issue, m122 attached.. any idea ?
setup is : 6HC+3HC+3HC, on a sbc (pi 3b)...
updated to the last firmware (including ext boards).m122.txt

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D0-3SJ6P-9A0LG
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 63124 of which 44 recycled
Never used RAM 145876, free system stack 200 words
Tasks: Linux(ready,91) HEAT(blocked,296) CanReceiv(blocked,882) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1189) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:13 ago, cause: watchdog
Last software reset at 2021-01-24 17:45, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 146284, slot 2
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x00000001 SP 0x2041fbc0 Task MAIN Freestk 1662 ok
Stack: 2042cae4 ffffffff ffffffff 00000001 00000322 0046b22d 0046c0e0 610f0000 2042ae18 0046b0ff 2042ae18 00000000 0000031f 0000000a 2042ae18 2042c74c 00000000 ffffffff 003fffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 26.1, current 27.4, max 27.4
Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 10882, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 10882, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 10882, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 10882, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 10886, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 10886, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-01-26 16:33:05
Slowest loop: 0.30ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 71, send timeouts 0, received 73, lost 0, longest wait 1ms for reply type 6018, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 0ms ago
RX/TX seq numbers: 62299/504
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 0.38
Maximum length of RX/TX data transfers: 4172/1560

jrockland

@jrockland **Error doesn't come from the 6HC, I swapped the board with another one and still have the same problem. probably come from the SBC.
I'm getting a SD card built for stand alone and Ill check if it happen again.

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