Locking up and sometimes crashing 1.3
Hi,
I have been using 0.93 for ever as I had some reliability issues with the versions just after that. I just upgraded to 1.3, and also did a complete reinstall (latest image) on a fresh sd card (due to crashes). Also tried a different pi (pi 4) was using a 3b.
Anyway to cut a long story short, sometimes the pi locks up causing the printers to reset and sometimes the printers just stop (2 prusas mk3s). The latest time I got the following from the trouible shooting and console:
I have been using 0.93 for ever as I had some reliability issues with the versions just after that. I just upgraded to 1.3, and also did a complete reinstall (latest image) on a fresh sd card (due to crashes). Also tried a different pi (pi 4) was using a 3b.
Anyway to cut a long story short, sometimes the pi locks up causing the printers to reset and sometimes the printers just stop (2 prusas mk3s). The latest time I got the following from the trouible shooting and console:
error: Reading serial conection failed: End of file. Closing connection.
[05.07.2022 18:58:29] : error: Reading serial conection failed: End of file. Closing connection.
Recv:18:58:26.093: LCD status changed (3)
Mesg:18:58:28.979: Connection closed by os during print ... trying reconnect for 10 seconds to continue ...
So another wasted print.
It is connected via a powered usb hub and each printer has a usb camera.
Everything was working fine until I upgraded.
PLease help.
I have ordered 2 4 port powered usb hubs for delivery tomorrow to try to separate the printers or the printers and cameras.
Other than that no idea what to do.
Cheers
Richard
So another wasted print.
It is connected via a powered usb hub and each printer has a usb camera.
Everything was working fine until I upgraded.
PLease help.
I have ordered 2 4 port powered usb hubs for delivery tomorrow to try to separate the printers or the printers and cameras.
Other than that no idea what to do.
Cheers
Richard
Comments
What do you understand from this? For us a lock up is that nothing works any more. No response from API so gui is non functional if it even loads. This is normally dead lock but only a full backtrace as described here
https://www.repetier-server.com/knowledgebase/debugging-crashes-hangs-on-linux/
can reveal what is causing it and we can then eventually fix it (if reason is clear) or see that it is fixed for upcoming 1.4.0 already (coming soon).
This means the pi is still accessible so you can login over ssh. If pi crashed completely so linux is not running as well it is unlikely a server issue.
> error: Reading serial conection failed: End of file. Closing connection.
This is quite clear. Linux closed the serial normally when usb is deactivated. Linux does it when it detect EMF or bigger undervoltage. So you should have a look at our gui if you see in the flash menu a hint for undervoltage. If that is the case from experience this often causes random issues on pi including crashes and usb disconnects.
> It is connected via a powered usb hub
You mean there is no designated power source for pi just backpower from hub (which as far as I know should not exist from standard but most hubs have)? As you read everywhere power is the critical part on the pi. You should use a 5.1V power supply.
You might ask what changed - well linux and drivers and pi firmware are newer with newer image. Maybe it is just using more power due to more cpu usage or drivers/linux is more sensitive when they disable things. Hard to say. In general we have no known printing issues in 1.3 except hardware related problems.
With 1.4.0 we also have a new image that will be based on current Raspbian OS bullseye while 1.3 is based on buster. So upgrading image for next update might also help.
Thanks for the response as always. By connected via a usb hub I meant the printers and cameras. I have now connected the two prusas to the two USB 2 ports directly on the pi, and left the cameras on the hub and have so far ran a couple of prints ok (more running now). When the two new hubs arrive I will try them (as I need to connect my 3rd printer again). There are no under voltage on the flash menu.
I will let you know how it all goes.
Thanks
Richard
So managed a couple of 7 hour prints or more on each. Pi has been up for 21 hours.
Then a few minutes ago it disconnected both printers, pi and repetier still running. Printers connected direct to usb 2 ports on the pi 4.
Same error as before. I have pasted the section from the syslog below from when it stopped - 16:49. A copied and pasted in two parts so may have some overlap or a few missing records but they are all the same.
Are you using webcams with mjpg or yuyv encoding? If you have more then one webcam with yuyv apart from mjpg_streamer being very busy with encoding the usb bus will be 100% occupied. At least I see errors from webcam as well at same time so there might be a connection. Can you also provide
lsusb -t
output so it is easier to see which usb devices syslog is reporting for.
There is an option to reconnect usb on disconnection - just written for such cases where normally after disconnect linux reconnects usb quite quickly. Make sure you have it enabled. Could at least make printers continue print so they are not lost. Also of course reason should still be found out, but it is quite surely not server related. Print stop is just a result of linux disconnecting the usb. Next releas eis nearly finished maybe it works better as it also uses newer kernel with more fixes. On the other side if it is overload or communication disturbances it will not change. Anything changed like cables or position of cables, new printer/webcam already connected compared to old solution.
I have just moved the location of the pi, changed the usb hub (new hub) that the cameras are connected too.
Running some prints now. If it happens again I will send the lsusb output. Fast reconnect is on but once the usb's go they are gone until a reboot. Even disconnecting the usb cable and reinserting does nothing.
I will keep trying
Cheers
Richard
That is hard. Normally crashed usb drivers restart on cable reconnect. We even have a function to disconnect usb to force driver to reconnect (USB reconnect on timeout) - normally it should be never. If it is never you might try to enable it but if really only reboot helps it should not help here:-(