running on slackware-14.2 & its linux-5.4.198 kernel .

Mouse is connected to a KLau 4Port KVM switch .

The entries shown below can sometimes be upto 10 or more deep causing the mouse & keyboard to not be responsive .

I'd like to get to the bottom of the error's seen below & hopefully get them rectified .

--- The one item is I MUST keep this KVM in place ---

Tho , Which is what I beleive might be causing the difficulty .

Also this symptom has only been observeable in the last 3-5 months , The KVM has been in place for about 3 years .

What is the best way to determine from normal tools found in slackware-14.2 who is the culprit ?

USB is not my best friend most times .

Tia , JimL

Some wild guesses.

The ehci-pci kernel module is for USB 2.0.

If the KVM has been in place for 3 years then unless the KVM has developed a fault:

* Slackware 14.2 came with the 4.4 kernel. Unless a typo, the 5.4.x kernel was installed manually. The ehci-pci module with the 5.4 kernel could be more finicky than the 4.4 kernel module.
* The mouse or keyboard are auto suspending.
* The mouse or keyboard were changed recently.
* The cable or connector on one of the devices has gone bad.
* The mouse or keyboard has gone flaky. Mice are known for doing that.
* The computer or motherboard was replaced recently.
* Another USB device is actually causing the messages, such as a printer or external disk.
* Or some kind of USB-to-Something-Else adapter.

Perhaps the lsusb command will correlate a device number with the messages.

If still needing to use Slackware 14.2, is a newer 5.4 kernel necessary or will the 4.4 kernel suffice? Updating to 5.4 might imply a new motherboard or other hardware, hence part of the recent cause of the messages?

Try to eliminate that the KVM might have faulty USB connectors. Connect the 14.2 system to different KVM USB ports.

Try disconnecting the mouse or keyboard one at a time to see if the messages continue.

Use the powertop tool html dump to find the syntax way to disable autosuspend.

Traditionally, wired keyboards and mice are designed to USB 1.1 specs. That's why most come with "white" connectors. These devices do not need USB 2.0 or 3.x speeds. USB 2.0 and 3.x are backwards compatible with 1.1. Although using a 2.0 or 3.0 port on the motherboard for a mouse or keyboard normally should be fine, a USB 1.1 keyboard and mouse will remain at 1.1 speeds. Possibly the 5.4 kernel module code is designed to think the device is not responding fast enough. So plug keyboards and mice into 2.0 ports and keep the 3.0 ports open for external storage devices.

Possibly try blacklisting the USB 2.0 ehci_hcd kernel module. If the mouse and keyboard are the only USB devices, then USB 2.0 compatibility is not required.

Somebody with gastrointestinal issues and FOMO likely will pipe in and tell you 14.2 is EOL. Just smile.

I hope this helps!

1 members found this post helpful.

@lostintime , It appeared to have been the (supposedly) new mouse .
What an easy fix .
Tnx , JimL

Just in case you need a new mouse, after trying numerous brands over the years, I can't recommend highly enough Steel Series mice, even the cheapest models. Besides being extremely accurate and precise, they REALLY hold up. I've had way too many brands, even those costing just shy of $100, that switches fail and especially the stupid plastic gears for the wheels strip out. I am an avid gamer and severely abuse mice and keyboards. I bought a top of the line programmable Rival 710 Steel Series and after 6 months bought a cheap one (half the price of the Rival 710) from Steel Series for other PCs I run. Both feel like new nearly 6 years later.

1 members found this post helpful.