Duet crash when refreshing WebGUI

krzaku

David, are there any news on this?

dc42

I'm sorry for the delay in responding. I read your messages on a portable device, so it wasn't easy to flag them for looking into.

The status report shows that it spent too long in the spin loop in the Network module, so the software watchdog timed it out. Do you have the USB port connected to anything?

krzaku

No, I never used the USB port.

dc42

I am putting some more debug into the next 1.20 beta release to help pin this down. I have tried to reproduce it, without success.

krzaku

Thanks, will try it and report back.

krzaku

I've been away from 3d printing for a while, I've just come back and I tried reproducing this bug again, and it's still there. Although I can't see any additional debug info you're talking about in the M122 output: https://pastebin.com/9GYuUWFF

dc42

Thanks for your report. The critical part of the pastebin report is:

[[language]]
RepRapFirmware for Duet WiFi version 1.20RC1 running on Duet WiFi 1.0
...
Last reset 00:00:16 ago, cause: software
Last software reset reason: Stuck in spin loop, spinning module Network, available RAM 7944 bytes (slot 0)
Software reset code 0x4041, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f80f, BFAR 0xe000ed38, SP 0x2001f92c
Stack: 0042c809 00008196 0043bffb 00008196 ffffffe9 00001000 00081111 40080000 00008196 20002dfc 00436fff 0043a914 610f0200 407042a1 00000000 3edb6db7 b7254200 3e178897

I have it on my list to look into next week. However, as nobody else has reported this issue, it may indicate a hardware problem.

dc42

Are you able to reproduce this if you refresh the web interface while a print is running in simulation mode?

dc42

I've looked at the stack trace, and it suggests that the processor was waiting forever for the SD card interface to become ready. Please confirm that you are not using an SD extender cable. I suggest you try a new SD card.

krzaku

Using a new SD card seems to have fixed it, I'm not 100% sure though because of the semi-random nature of this problem. Let's say it's resolved for now, if I encounter it again with the new card I'll report it. Thanks for the help in debugging this.