WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:478 dev_watchdog+0x398/0x3a0 NETDEV WATCHDOG: eth0 (r8152): transmit queue 0 timed out On arm64 build I have beeen able to get some dmesg traces: Raspberry Pi Zero 2 W, 4GB, 32GB/64GB microSD cards, with and without Ethernet hat. Not relevant, happens even when there is no printer connected. Tried latest nightly 64-bit (as there seems to be no official 64-bit build available yet) where I could reproduce the issue as well ( ). It almost seems like jumbo frames are crashing the network stack and causing it to be restarted. It also happens regardless of using an USB LAN or the built-in WLAN interface. The issue also happens when trying SSH logon while using jumbo frames on LAN interface. Did the same happen when running OctoPrint in safe mode?ĭoes not matter in which mode. After a while the situation seems to recover slightly and OctoPi starting to respond on ICMP ping again but keeps "dying" when sending large frames again. Not even ICMP ping is responded any more. OctoPi stopping to respond on network interface. Try to fetch the OctoPrint web interface.Use a LAN client and Switches with jumbo frames (e.g.
0 Comments
Leave a Reply. |