Network and restarting Issues with 3.5.0-RC3

gloomyandy

@cbusillo Please post the full M122 output as that will contain build details and other information that may be of use in identifying the problem.

cbusillo

@gloomyandy

M122 output

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+ (2024-02-13 13:33:37) running on Duet Ethernet 1.02 or later
Board ID: 08DAM-9K9K2-NGNSN-6J9DL-3S46Q-9RSBJ
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 68232 of which 0 recycled
Never used RAM 21656, free system stack 204 words
Tasks: NETWORK(1,ready,23.1%,220) HEAT(3,nWait 5,0.1%,326) Move(4,nWait 5,0.0%,359) MAIN(1,running,73.6%,743) IDLE(0,ready,3.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:27 ago, cause: software
Last software reset at 2024-02-16 13:20, reason: HardFault undefInstr, none spinning, available RAM 21192, slot 0
Software reset code 0x4073 HFSR 0x40000000 CFSR 0x00010000 ICSR 0x00400003 BFAR 0xe000ed38 SP 0x2001ff98 Task NETW Freestk 29864 ok
Stack: 200036c0 00000004 00004000 400e1400 ffffffff 0041bd09 00459000 010f001f 21000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
MCU temperature: min 28.4, current 29.6, max 30.1
Supply voltage: min 24.4, current 24.5, max 24.6, 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: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2024-02-16 13:21:23
Cache data hit count 1076937391
Slowest loop: 1.68ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
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 -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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) 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
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 0 clear 101141
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 6.08ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
Socket states: 5 2 2 2 2 2

cbusillo

To be clear, RC3 printed fine, but it only loaded the css file once in maybe 100 tries. RC3+ reboots while idle. I know at least once in 30 minutes, probably more since I wasn't in the room.

gloomyandy

@cbusillo One for @DC42 to take a look at. HardFault undefInstr are not a good thing. Also the free stack space looks a little suspect?

cbusillo

@gloomyandy anything more you want me to provide? I need to flash it back in a bit for a couple of prints, but I can collect whatever info you need.

droftarts

@cbusillo I think you're seeing the same issue that was seen in this thread: https://forum.duet3d.com/topic/34804/3-5-0-rc3-cannot-connect-to-dwc

Duet 2 Ethernet and Duet 2 Maestro (also Ethernet) were having problems after an update to the network code. This has been fixed, and you should be able to use any of the 3.5.0-rc3+ versions of the firmware on the forum, or use the one @dc42 linked to in the thread here https://forum.duet3d.com/topic/34804/3-5-0-rc3-cannot-connect-to-dwc/40

Ian

cbusillo

@droftarts Hi!

With rc3+ I had reboots. Is there more than one rc3+?

droftarts

@cbusillo Sorry, I've read your first post again, and realise now you had already found the rc3+ I linked. There are new firmware builds at https://www.dropbox.com/scl/fo/p0136wx04h8xf6ejwdnn9/h?rlkey=efrfwyb6o5tqid11gustz3uvy&dl=0

Though I'm not aware of any further changes for Duet 2 Ethernet since the last rc3+. If you could try it, and have the same problem, we really need a full M122 following a reboot, and a description of what happens (ie how long between resets, what it's doing etc). Could you flash it to your Duet and do that, please? I'll flag it up to @dc42 then.

Ian

cbusillo

@droftarts I will after this 1-2 hour print finishes. I flashed it twice and both times it restarted within 30 minutes (I was out of the room so it might have restarted multiple times. Just to be clear, I'm not asking for troubleshooting help as I am fine with downgrading to RC2, I just want DC to be aware of the problem. I'll follow up shortly with M122 logs again. It reboots while doing nothing, just sitting there idle. I only noticed because the fan turn on like they do at power up

droftarts

@cbusillo Okay, thanks. Can you post your config.g? I have a Duet 2 Ethernet I can set up here, would be good to replicate your setup, just in case something in config is causing it. Also daemon.g if you use it.

Ian

dc42

@cbusillo unfortunately I no longer have the .map file for that build of RRF so I can't investigate the hard fault in your M122 report. Please try the latest firmware at https://www.dropbox.com/scl/fo/p0136wx04h8xf6ejwdnn9/h?rlkey=efrfwyb6o5tqid11gustz3uvy&dl=0 and post another M122 report if it happens again.

This type of fault can be caused by electrostatic discharge from the hot end metalwork to the thermistor; so please make sure that the hot end metalwork is connected to Duet ground, either directly or through a resistor.

cbusillo

@dc42 Testing new version now. Sorry for not doing this sooner, I had too much going on.

ESD doesn't make much sense to me since it only happened on RC3+. I'll check the ground anyway. Grounds can cause so many flakey issues, right? :). Thank you for all you do.

cbusillo

@dc42 The problems seems to have gone away with the new RC3. Thank you for whatever was fixed