3.4.2rc3+ Duet Froze when logged into to webcontrol
-
Was running a 16hr job. on my custom Voron 2 style machine.
I have a Duet 2 wifi with Duex5 expansion
was printing fine, but hen I logged into to webcontrol in chrome to check on its progress it Duet froze and the job was lostHad to physically power off the printer and restart to get to be responsive.
I have updated to RC3 since then. (was on RC2)M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2rc3+ (2022-08-31 12:50:46) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DLM-996RU-N85T0-6JKF2-3SJ6Q-1AVVR Used output buffers: 1 of 26 (22 max) === RTOS === Static ram: 23860 Dynamic ram: 75752 of which 40 recycled Never used RAM 12428, free system stack 182 words Tasks: NETWORK(ready,20.8%,137) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,78.2%,428) IDLE(ready,0.9%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:05:43 ago, cause: software Last software reset at 2022-09-02 09:29, reason: User, GCodes spinning, available RAM 7908, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 33.1, current 33.5, max 35.5 Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-09-04 14:33:36 Cache data hit count 4294967295 Slowest loop: 171.40ms; fastest: 0.18ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 26.8ms, write time 68.5ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1, 0.17 reads/min === Network === Slowest loop: 1107.96ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27beta1 WiFi MAC address 84:0d:8e:b2:f8:6f WiFi Vcc 3.32, reset reason Turned on by main processor WiFi flash size 4194304, free heap 24328 WiFi IP address 192.168.0.195 WiFi signal strength -72dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
undefined Phaedrux moved this topic from General Discussion
-
So is that M122 collected after the freeze? Or did you update firmware etc and then capture an M122?
-
@phaedrux yes M122 was collected after restarting and updating. I realize perhaps not helpful.
-
If it happens again on RC3+ please capture an M122 immediately and post it here.
