Thanks for looking at it and for the suggestion. However IIRC I have also built a 5.13.2 with the same issue.

For now I will try some relatively recent huge kernels found in http://slackware.uk/cumulative/slack...slackware64/k/ (thanks Darren for hosting them!) and check which is the last working here with all ports.

The answer is 5.12.16, as 5.13.2 and 5.13.3 have the same issue as 5.13.5.

I just posted this on the Slint mailing list.

1 members found this post helpful.

Didier,

Excuse me to come back to this, but
You said :
And because of this usb issue, you can't put the stable 5.13.x
So why ship Slint with an EOL kernel instead of an LTS one?

Is that Slint equivalent of slackware-current released as stable?

After all, the Slackware 15.0 may be released with the kernel 5.14.x or even 5.16.x, right?

And how reproducible is that issue?

Is affected only a particular model of laptop, or are many other hardware affected?

I ask this because I have never had (also) problems with mouses and keyboards on the last 15 years, no matter of what Linux distribution I used, and I have a garage full of trashware.

And all boxes works from this POV.

Temporarily, while waiting for better. I am confident that the problem will be solved in the 5.13 branch. If it is not fixed before Slackware 15 is released, I'll take care of it.

that makes sense ;-)
let's hope so

No. Let's call it a semi-rolling distribution. For instance we still ship gcc-5.5 and glibc-2.23, but already python-3.9, the most recent software in the accessibility stack and an up to date Mate desktop.

If the issue is solved in 5.14 I will ship it, no problem. Switching to a new branch is not an issue, I have done that twice already without any user complaint. I really hope this issue will be solved in a matter of days or at most weeks, not months, for the sake of Linux' reputation...

I can't answer, all I know is two other people have reported similar issues in this thread.

Are you telling us that an issue of which you don't suffer personally is not worth taking care of?

Absolutely NOT!

As you have seen what I did regarding those strange issues generated by that shared bind mounting of /var/run, for example.

I have just asked you regarding the (estimated) impact area, considering that I have never had such problems, even I loved to collect various (old) computers. In fact, until recently you do not specified that multiple users are affected, right?

Right now, I have 11 functional computers, and if I will insist a bit, I can bring to life another 5. Everything is trashware, thought - as I already confessed.

My flagship box has an AM3 Athlon x4 605e with TDP of 45W and (mainly) works with a built-in Radeon 4250 graphics. For various reasons, sometimes I mount on it a Radeon HD7450, or an AMD R5 240 or a NVIDIA GeForce 605.

That's the best I have. Imagine the lower ones.

No need to narrow it down to a point version before doing the git bisect. If you already know 5.12.11 is good and 5.12.19 is bad just those as your starting point for git bisect. It will actually be more efficient that way, as git bisect won't restrict itself to first testing 5.12.y tags.

If you can narrow it down to an offending commit for bonus points you can then test all (or as many as you want) of the release branches of the kernel (with and without the offending associated commit) when reporting it to the kernel developers.

5.12.18 is "bad". Now building 5.12.17.

PS meanwhile, listening https://www.youtube.com/watch?v=GKHL8XPeLpE

The text is misleading: Menahem Pressler is 97 years old, not 90.

1 members found this post helpful.

Sorry for the delay - we've been asleep on this side of the world.

I just tried 5.13.5 on the affected machine but the problem is still there.

I'm a little perplexed as to why there are so few reports about this elsewhere - is Slackware so far ahead of other distros that not many working systems in the world have experienced the problem yet?

chris

Same question here. At least Arch is also shipping 5.13.5 currently and it is customary for Arch users to upgrade their packages as soon as possible.

OpenSuse Tumbleweed (LiveCD) is ship with a 5.13.4
Maybe, you could give a try ?