Stuck in spin loop
-
Since installing the FW 2.04RC1 I have been experiencing freezing on occasions when starting the GUI interface. The card is a genuine Duet 2 Maestro.
The browser I use is google chrome. It only happens when accessing the GUI on some occasions and every time up till now is when I'm printing.
Ive been running a few diffrent versions of the FW but never had any freezing before. It's happened about 5 or 6 times over a few weeks, my printhead just stops, I lose contact through the browser and I have to restart the printer. I take it this is a bug??
The Web interface version 1.22.6.Thoughts or possible fixes to try would be appreciated.
Here is the M122 diag which I ran immediately after a reboot ....
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 2.04RC1 running on Duet Maestro 1.0Used output buffers: 3 of 24 (7 max)
=== RTOS ===
Static ram: 19664
Dynamic ram: 94352 of which 0 recycled
Exception stack ram used: 332
Never used ram: 16724
Tasks: NETWORK(ready,660) HEAT(blocked,1276) MAIN(running,3908) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:03:32 ago, cause: power up
Last software reset at 2019-08-10 19:43, reason: Stuck in spin loop, spinning module GCodes, available RAM 16396 bytes(slot 3)
Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f80f BFAR 0xe000ed38 SP 0x20000da4 Task 0x5754454e
Stack: 0044412b 00447c02 61000000 00000000 00000004 00447ded 20003fd4 00000001 20000758 10000000 00000004 2000783c00008ea0 00000004 0044441d 00000004 00000000 00000001 0041a69f 20000e24 01e05fff 00000000 00403101
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest block write time: 13.9ms, max retries 1
MCU temperature: min 33.1, current 35.1, max 35.8
Supply voltage: min 0.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, read errors 0, write errors 0, ifcount 8, reads 8472, timeouts 0
Driver 1: standstill, read errors 0, write errors 0, ifcount 8, reads 8472, timeouts 0
Driver 2: ok, read errors 0, write errors 0, ifcount 8, reads 8472, timeouts 0
Driver 3: standstill, read errors 0, write errors 0, ifcount 6, reads 8469, timeouts 5
Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 8474, timeouts 0
Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 8480
Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 8479
Date/time: 2019-08-10 19:48:22
Slowest loop: 137.87ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 168, MinFreeDm: 166, MaxWait: 120262ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 38, completed moves: 37, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Segments left: 0
Stack records: 3 allocated, 0 in use
Movement lock held by file
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 33
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
lcd is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 114.22ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex -
What firmware were you running before you upgraded to 2.04RC1?
-
I was Running 2.02 and then 2.03.
The problem is very intermittent, if there is anything more I can do for you diagnostically to enable a better trace of the problem then let me know and I will try to reproduce it and maybe give you more information what I discover?
