Mesa hm2/hm2_7i96s.0: error finishing read

Depending on what graphical environments are installed on the 5.x debian kernels (eg Bookworm et al), you can select X windows instead of Wayland on the logon screen. If you have auto login set up, just logout to get to this.

We found this to be an issue for remote support via Teamviewer which requires X. So it was good to find such a simple workaround. 

I think the early builds of Bullseye 5.10 did not have this issue when I think back.

I saw that the Kernel 6 Release candidate will become 5.20 so maybe Debian will adopt it. They seem to be incrementing kernels as they are released.

rodw wrote:

I saw that the Kernel 6 Release candidate will become 5.20 so maybe Debian will adopt it.

There's nothing special about the 6.x kernels compared to the 5.x ones. From www.kernel.org/category/releases.html :

"Does the major version number (4.x vs 5.x) mean anything?

No. The major version number is incremented when the number after the dot starts looking "too big." There is literally no other reason."

My test machine exhibits the latency issue on 5.18 kernels and not on 6.0 kernels
so something significant has changed (I have not tried 5.19 yet)

(plus I have tried most of the 5.x range)

I did a bit of basic research and there are a number of tuning parameters for the TCP stack so I wondered if ethernet on Bookworm et all could be improved by chaning some flags. I think a lot can be changed just by editing some text files.

Unfortunately most are written around inproving preformance in a server room.

This article talks about the challenges of usint the TCP stack with real time comms (and preempt_rt
ntrs.nasa.gov/api/citations/20200002393/...oads/20200002393.pdf

This one is interesting too and discusses some of the available flags and how to set them.
cromwell-intl.com/open-source/performance-tuning/tcp.html

Maybe somebody who knows a bit more thanI could explore. I guess a good start would be to compare Debian 10 TCP flags with Debian 12 ones.

 

The Mesa cards use UDP though (according to e.g. the 7i92 manual), so I'm not sure TCP settings are relevant? Maybe there are settings that affect both protocols.

arvidb wrote:

The Mesa cards use UDP though (according to e.g. the 7i92 manual), so I'm not sure TCP settings are relevant? Maybe there are settings that affect both protocols.

That may have been a poor choice of words. Should be networking stack, the nasa document above refers to UDP as well as TCP.