Duet2 ethernet DWC lost connection while printing

burntcrispy

My Duet2 ethernet DWC lost connection while printing.
Refreshing the page in chrome results in: This site can’t be reached jubilee.lan refused to connect.
Can still ping and telnet.
Duet and telnet both giving a lot of: Warning: Driver 1 warning: over temperature warning
The driver warning stopped when print finished, but chrome still can't connect.
I also issued a M122 from telnet see below.
MCU temperature maxed at 47.0

Anything I should try before rebooting it?
What does Error status: 0x14 mean?

Thanks

M122 via telnet, after print complete:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet Ethernet 1.02 or later + DueX5v0.11
Board ID: 0JD0M-9P6B2-NJ4S4-6JKDA-3SJ6P-KB2QK
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 74348 of which 228 recycled
Never used RAM 10108, free system stack 98 words
Tasks: NETWORK(ready,82.8%,212) HEAT(notifyWait,0.2%,307) Move(notifyWait,13.5%,295) DUEX(notifyWait,0.0%,24) MAIN(running,3.4%,360) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 02:02:19 ago, cause: power up
Last software reset at 2022-03-26 18:44, reason: User, GCodes spinning, available RAM 11812, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x14
Step timer max interval 0
MCU temperature: min 24.7, current 44.6, max 47.0
Supply voltage: min 24.0, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/196/176, gc cycles 16
Events: 82454 queued, 82454 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2022-04-30 13:12:15
Cache data hit count 4294967295
Slowest loop: 353.22ms; fastest: 0.12ms
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 5.8ms, write time 221.2ms, max retries 0
=== Move ===
DMs created 83, segments created 28, maxWait 255201ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 506070, completed 506070, hiccups 0, stepErrors 0, LaErrors 0, Underruns [3, 0, 11], 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 -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.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 13, 0.11 reads/min
=== Network ===
Slowest loop: 318.38ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(2), 1 sessions
HTTP sessions: 0 of 8
Interface state active, link 100Mbps full duplex

burntcrispy

Unplugging and replugging the ethernet cable brought it back.