Mesa hm2/hm2_7i96s.0: error finishing read

More
2 years 11 months ago - 2 years 11 months ago #285517 by PCW
For a ping test it's better to do many:

ping -c 5 -i .2 10.10.10.10
(to update arp cache)
then:
sudo chrt 99 ping -i .001 -q 10.10.10.10

(then control C after a minute or so)

I have a 800G1 (a bit older) and it is OK Ethernet wise
but has a I217 rather than I219 MAC

It did seem to get better with more recent kernels (running 6.6-rt12 now)

Another thing to try is pinning the Ethernet IRQ to CPU 3
Last edit: 2 years 11 months ago by PCW. Reason: typos
The following user(s) said Thank You: spumco

Please Log in or Create an account to join the conversation.

More
2 years 11 months ago #285523 by spumco
PCW - will do.

I did see an older post of yours describing pinning the Eth IRQ to a core number, but when I tried to duplicate I got a 'permission denied' error despite using sudo.

When you mentioned 'must use root', I'm guessing that means something other than 'sudo ...' in terminal?

A copy-paste for me to pin the Eth IRQ would be helpful.

Please Log in or Create an account to join the conversation.

More
2 years 11 months ago #285524 by PCW
You can find the Ethernet IRQ by:

first do this as root so

sudo -i

then

grep eno1 /proc/interrupts

then cd to /proc/irq/#

Where # is the number in the first column of the grep result

then

echo '8" > smp_affinity

then

(and control D to go back to normal user)
The following user(s) said Thank You: spumco

Please Log in or Create an account to join the conversation.

More
2 years 11 months ago #285539 by Unlogic

[Rather than starting a new thread, I'll continue here...]

Starting to commission a new build and I'm getting the error finishing read problem crop up within seconds of starting LCNC and could use some help diagnosing.

PC: HP elitedesk 800 G2 mini
NIC: Intel i219LM
LCNC: 2.9 from ISO on LCNC home page
Kernel: 6.1.0-13 (haven't messed with this)

etc/network/interfaces:
auto lo
iface lo inet loopback
auto eno1
iface eno1 inet static
address 10.10.10.1
hardware-irq-coalesce-rx-usecs 0

Grub:
isolcpus=3 intel_pstate=disable processor.max_cstate=0 idle=poll cpufreq.default_governor=performance i915.enable_dc=0 ahci.mobile_lpm_policy=1 irqaffinity=0 nomodeset quiet

Good latency after fiddling with grub.  Just copied the above from the latency thread, don't really understand the backstage stuff.

 


LCNC terminal output:
Warning: Spoiler!


Ping times
Warning: Spoiler!


Would trying a later kernel (6.3,6.4,etc.) help?  I did see mention elsewhere here that there is a recently fixed bug related to Intel i219LM NICs...but don't know if that's related or when the fix will make it to kernels appropriate for LCNC.

ThxI
I had major issues with this exact Elitedesk setup recently that I made a post about in my build thread here on the forum: forum.linuxcnc.org/12-milling/50559-opti...nc-conversion#284497

In short there are some nasty bugs in the driver for that network card which made their way into the kernel and the fix for them hasn't been included in the Debian 6.1/6.3 kernel yet from what I can see.

I ended up moving to an older hardware setup for now.
The following user(s) said Thank You: spumco

Please Log in or Create an account to join the conversation.

More
2 years 11 months ago #285543 by spumco
@Unlogic - thank you.  Your thread was what I referenced earlier about the kernel bug.

I'm hoping either
  • New LAN cable, or (slim hope, but easy)
  • PCW's suggestion to pin the IRQ, or
  • PCW seems to be on 6.5... maybe that would help if I can figure out how to do it.  

Really, really don't want to deal with installing another PC in my console.  Again.

Please Log in or Create an account to join the conversation.

More
2 years 11 months ago #285545 by Unlogic
If you figure out a workaround, please post an update.

I've been working with Linux since the late 90's and I couldn't get the Intel i219LM to work stable for any length of time with the current 12.2 Debian kernels.

Applying the patch from Intel manually and compiling a custom kernel would probably have done the job but I wanted to able to use the reqular "apt dist-upgrade" updates without any fuzz so I opted to not go that route.

Please Log in or Create an account to join the conversation.

Moderators: PCW, jmelson
Time to create page: 0.293 seconds
Powered by Kunena Forum