12-01-2019, 10:02 AM
(11-26-2019, 12:48 PM)ykanello Wrote: I am having network timeouts towards all SoC of the clusterboard.
I have never noticed this. However, due to the other issues the board doesn't see much network traffic. I would suggest checking bandwidth utilization and pinging between the modules. They only have 100Mbit interfaces and saturation causes packet loss.
(11-26-2019, 12:48 PM)ykanello Wrote: After reading the posts with regards to the PSU, I removed two SoC and now is running with 5, but the problem still persists.My problem SoC produce these errors within dmesg. Check if any show it. You may also want to try using an ATX power supply.
Code:
[15507.597377] rcu: rcu_sched kthread starved for 15755 jiffies! g1064201 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
[15507.597380] rcu: RCU grace-period kthread stack dump:
[15507.597384] rcu_sched I 0 10 2 0x00000028
(11-26-2019, 12:48 PM)ykanello Wrote: I do not have the time drift problem (date set to a far future) anymore after I installed the recommended kernel package from the community. [linux-image-next-sunxi64_5.99_arm64.deb]I recently moved to linux-image-current-sunxi64_5.3.9 and the time jumps have ceased. However, now the Ethernet device will shut off.
(11-26-2019, 12:48 PM)ykanello Wrote: I rely heavily on the network of the clusterboard and this timeout issue makes the clusterboard quite useless for me.Not that my research has showed. You could try adding some fans to the case and heatsinks to cool chips. Additional, cooling and an ATX power supply are on my todo list. The clusterboard chips show around 90F when ambient is around 60F.
Does any one have a solid idea on what the problem could be?