[3.6.0-beta.4] Code 7 halt, m122 Dump

[Notepad]

Hi all, Had my first Code 7 today. Ive attached the M122 for any needed debugging

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.4 (2025-02-11 09:50:40) running on Duet WiFi 1.02 or later
Board ID: 0JD2M-9F8TA-GJ4TJ-6JTF4-3SD6L-16VG6
Used output buffers: 3 of 26 (24 max)
=== RTOS ===
Static ram: 24016
Dynamic ram: 68220 of which 0 recycled
Never used RAM 10264, free system stack 68 words
Tasks: NETWORK(1,ready,15.6%,181) LASER(5,nWait 6,1.5%,214) HEAT(3,nWait 5,0.1%,307) Move(4,invalid,7.0%,239) MAIN(1,running,75.8%,736) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 07:38:49 ago, cause: power up
Last software reset at 2025-02-25 15:15, reason: User, Gcodes spinning, available RAM 12712, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 11.5ms, write time 535.5ms, max retries 0
=== Move ===
Segments created 729, maxWait 1677858ms, bed comp in use: mesh, height map offset 0.000, hiccups added 57/113 (3.51ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 19909.00/20410/-0.49 6675.00/6893/-0.86 15700.00/15693/-0.79
No step interrupt scheduled
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min 0
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 340521, completed 340481, LaErrors 0, Underruns [0, 0, 0]
Segments left 6
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 3
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
=== Network ===
Slowest loop: 537.88ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 39160
MAC address a4:e5:7c:03:da:6c
IP address 192.168.1.174
Signal strength -71dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

[dc42]

@Notepad thanks. For these types of error it's the info in the error message that reported Code 7 that's important, but unfortunately you haven't provided that.

However, I believe I have identified and fixed the cause of Code 7 errors. We expect to release 3.6.0-rc.1 very soon.

[Notepad]

@dc42 Dang, Ill try capture it next time. The code 7 has been incredibly rare for me, this is the first over 12 machines

[dc42]

@Notepad yes, code 7 halts were very rare. The cause I found (supported by debug evidence from two users) only occurred when a particular combination of events occurred. One of those events was the 32-bit step clock counter rolling over to zero within the duration of a move segment in a particular context. That rollover happens once every approx. 95 minutes on Duet 3.

[Notepad]

@dc42 I got sent this from the print farm, unfortunately its not the WebUI full log but this might help be

[dc42]

@Notepad thanks, that has the very large 'd' value that is characteristic of the Code 7 error that I fixed in rc1. I presume you were running beta 4 or earlier when that message was generated.

[Notepad]

@dc42 Yup, this machine is still on beta.4 The rollout of RC1 has been applied to most machines, but ones still ill a production job are still on B4