This issue is well known and was introduced to the Debian kernel with Bullseye (Kernel 5.10). It is caused by excessive kernel network latency and is nothing to do with 2.9.2 Building a kernel from pristine kernel.org sources mostly solves it. It has been slowly improving with successive versions of the kernel so I am surprised that Bookworm made it worse. We need more info to help much. CPU, number of cores, NIC manufacturers and model. Older 2 core PCs may not cut it today.
If it's an Intel nic, be sure to add the coalescing settings as advised in man hm2_eth My guess is that you probably have realtek NIC's that get the wrong driver (R8169) installed. If this is the case, you need to install a dkms driver. (r8168-dkms or r8125-dkms) I have a document in Google drive that outlines the way forward (under the heading optional steps) https://docs.google.com/document/d/1jeV_4VKzVmOIzbB-ytcgsW2I_PhCm1x7oiw8VcLFdiY/edit?usp=sharing This has solved the issue for hundreds of users. One or 2 of them were using a 2 core PC but I have never had anything less than 4 cores So in summary, I would 1. Install the Linux 2.9.2 ISO 2. Pick up on step 36 of my Document and install my 6.3 kernel. There is an instructions document if you wish to try your hand at building a later version (say 6.6) 3. Install the correct Realtek DKMS driver 4. Enjoy using linuxcnc! Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Sat, 3 Feb 2024 at 00:14, Peter Wallace <p...@mesanet.com> wrote: > On Fri, 2 Feb 2024, Marius wrote: > > > Date: Fri, 2 Feb 2024 10:32:54 +0200 > > From: Marius <mar...@mastercut.co.za> > > Reply-To: EMC developers <emc-developers@lists.sourceforge.net> > > To: Alec Ari via Emc-developers <Emc-developers@lists.sourceforge.net> > > Subject: Re: [Emc-developers] Repositories for buildbot on bullseye > > > > More information regarding this issue > > > > This is the max timings at startup of linuxcnc running Gmoccapy > > > > Parameters: > > Owner Type Dir Value Name > > 56 s32 RW 32713 comp.0.tmax > > 56 s32 RW 21741 comp.1.tmax > > 56 s32 RW 21649 comp.2.tmax > > 56 s32 RW 15801 comp.3.tmax > > 56 s32 RW 6484 comp.4.tmax > > 36 s32 RW 0 hm2_7i96s.0.read-request.tmax > > 36 s32 RW 937642 hm2_7i96s.0.read.tmax > > 36 s32 RW 79396 hm2_7i96s.0.write.tmax > > 29 s32 RW 35491 motion-command-handler.tmax > > 29 s32 RW 80781 motion-controller.tmax > > 39 s32 RW 22747 pid.b.do-pid-calcs.tmax > > 39 s32 RW 32665 pid.c.do-pid-calcs.tmax > > 39 s32 RW 36771 pid.s.do-pid-calcs.tmax > > 39 s32 RW 35744 pid.x.do-pid-calcs.tmax > > 39 s32 RW 32242 pid.y.do-pid-calcs.tmax > > 39 s32 RW 45865 pid.z.do-pid-calcs.tmax > > 30 s32 RW 1022059 servo-thread.tmax > > > > Then this is the max timings right after the crash > > > > Parameters: > > Owner Type Dir Value Name > > 56 s32 RW 93620 comp.0.tmax > > 56 s32 RW 21866 comp.1.tmax > > 56 s32 RW 30257 comp.2.tmax > > 56 s32 RW 21831 comp.3.tmax > > 56 s32 RW 22149 comp.4.tmax > > 36 s32 RW 0 hm2_7i96s.0.read-request.tmax > > 36 s32 RW 941321 hm2_7i96s.0.read.tmax > > 36 s32 RW 163732 hm2_7i96s.0.write.tmax > > 29 s32 RW 52368 motion-command-handler.tmax > > 29 s32 RW 152143 motion-controller.tmax > > 39 s32 RW 45604 pid.b.do-pid-calcs.tmax > > 39 s32 RW 46064 pid.c.do-pid-calcs.tmax > > 39 s32 RW 93254 pid.s.do-pid-calcs.tmax > > 39 s32 RW 37166 pid.x.do-pid-calcs.tmax > > 39 s32 RW 48941 pid.y.do-pid-calcs.tmax > > 39 s32 RW 45865 pid.z.do-pid-calcs.tmax > > 30 s32 RW 1031395 servo-thread.tmax > > > > > > Take note of the motion controller and the hm2_7i96s.0.read.tmax threads. > > > > > What is the CPU clock speed? > > Peter Wallace > Mesa Electronics > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
