You are not logged in.
Hello,
I have the same problem with
(EE) event27 - 2.4G Mouse: client bug: event processing lagging behind by 11ms, your system is too slow
I tried the udev rule and even installing tlp. I'm on a desktop and it has been malfunctioning since September.
Nothing since to change it, the lagging is not permanent though.
If anyone has something that worked for them, please let me know.
Edit:
I may have miss written my udev rule, it seems to work now. To confirmed after a few days.
Edit2:
It didn't work.
Last edited by Akadius (2020-10-23 07:30:46)
Offline
hey,
having similar issue for a long time, though i don't notice any discomfort or noticeable lag on desktop
(EE) event28 - Logitech Performance MX: client bug: event processing lagging behind by 14ms, your system is too slow
(EE) event8 - USB USB Keykoard: client bug: event processing lagging behind by 23ms, your system is too slow
I'm using TLP and according to it USB suspend is off for mouse and keyboard. Also turned off hub, but can see no difference
$ sudo tlp-stat --usb
--- TLP 1.3.1 --------------------------------------------
+++ USB
Autosuspend = enabled
Device whitelist = (not configured)
Device blacklist = 046d:c52b 1a2c:0002
Bluetooth blacklist = disabled
Phone blacklist = disabled
WWAN blacklist = disabled
.... skipped ....
Bus 002 Device 037 ID 1a2c:0002 control = on, autosuspend_delay_ms = 2000 -- China Resource Semico Co., Ltd USB Keykoard (usbhid)
Bus 002 Device 014 ID 046d:c52b control = on, autosuspend_delay_ms = 2000 -- Logitech, Inc. Unifying Receiver (usbhid)
Bus 002 Device 001 ID 1d6b:0002 control = on, autosuspend_delay_ms = 0 -- Linux Foundation 2.0 root hub (hub)
Also i often see warnings like this, though i don't know if it's related
W: awesome: a_glib_poll:437: Last main loop iteration took 0.208950 seconds! Increasing limit for this warning to that value.
Offline
Same here with keyboard & mouse, both USB:
[ 67813.758] (EE) event2 - TypeMatrix.com USB Keyboard: client bug: event processing lagging behind by 16ms, your system is too slow
[ 72900.766] (EE) event5 - DELL Laser Mouse: client bug: event processing lagging behind by 12ms, your system is too slow
I wouldn't have realized that if the xmodmap config weren't erased each time this happens. I have to re-run xmodmap ~/.xmodmaprc each time. Weirdly enough, my setxkbmap config (also executed by my ~/.xsession) is not erased.
Offline
I have similar issues on my P43s laptop (Cinnamon DE). Next to a mouse lagging I also often get doubled characters when typing.
This is what I see in my log, I can sometimes see the new log entry simultaneously with mouse lag, but there are also other lags not logged at all.
I can confirm that this issue is more frequent after wake up from a sleep mode.
[ 4283.278] (EE) event19 - Logitech M705: client bug: event processing lagging behind by 13ms, your system is too slow
[ 4305.456] (EE) event23 - Microsoft Wired Keyboard 600: client bug: event processing lagging behind by 30ms, your system is too slow
[ 5267.482] (EE) client bug: timer event19 debounce: scheduled expiry is in the past (-304ms), your system is too slow
[ 5267.482] (EE) client bug: timer event19 middlebutton: scheduled expiry is in the past (-279ms), your system is too slow
[ 5267.483] (EE) client bug: timer event19 debounce: scheduled expiry is in the past (-157ms), your system is too slow
[ 5267.483] (EE) client bug: timer event19 debounce short: scheduled expiry is in the past (-170ms), your system is too slow
[ 5453.476] (II) event19 - Logitech M705: SYN_DROPPED event - some input events have been lost.
[ 5484.468] (EE) event19 - Logitech M705: client bug: event processing lagging behind by 507ms, your system is too slow
[ 5484.468] (EE) event23 - Microsoft Wired Keyboard 600: client bug: event processing lagging behind by 492ms, your system is too slow
[ 5546.495] (II) event19 - Logitech M705: SYN_DROPPED event - some input events have been lost.
[ 5670.466] (II) event19 - Logitech M705: SYN_DROPPED event - some input events have been lost.
[ 5755.835] (EE) event19 - Logitech M705: client bug: event processing lagging behind by 11ms, your system is too slow
[ 5887.469] (II) event19 - Logitech M705: SYN_DROPPED event - some input events have been lost.
[ 5891.632] (EE) event19 - Logitech M705: client bug: event processing lagging behind by 13ms, your system is too slow
[ 5914.171] (EE) event23 - Microsoft Wired Keyboard 600: client bug: event processing lagging behind by 19ms, your system is too slow
[ 5949.467] (II) event19 - Logitech M705: SYN_DROPPED event - some input events have been lost.
Last edited by xhpohanka (2020-11-26 06:26:51)
Offline
I am also experiencing some issues with lagging. It feels like the mouse is stuck for a second. Also, keys seem to stick as well, resulting in multiple characters being printed. (like keeping the key pressed). This is happening quite often (about every 5-10 sec), but only after resuming from suspend. Only workaround is rebooting. I do not get the entries ("your system is too slow") in the log anymore, but sometimes this:
gnome-shell[2686]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Last edited by ac1dg (2020-12-11 11:37:47)
Offline
Everyone that is posting here, my original problem appears to have solved itself, so I'd recommend starting a new thread.
Offline
Hi,
I have this problem both with Logitech mouse and keyboard. I used MX Anywhere and MK Keyboard first, had stuttering lag, sometimes 1-2s, and the same happens with different Logitech mouse and keyboard.
I initially thought it's nvidia driver, but I tried using open-source driver and problem persists. Basically OS freezes to any input from keyboard mouse for up to 2s sometimes. I have to press key multiple times.
This became noticeable from around mid of last year (could be September). I am using Debian thought. Which suggests this might be kernel issue.
So bottom line is
- Not hardware problem (I tried two keyboards, two mouse)
- Not a GPU driver problem (I tried both open-source and proprietary drivers)
- Not a CPU/GPU/RAM usage problem, I run monitor to see if there is any unusual high spike
- Not a distribution problem (as you guys reported this on Arch and I am Debian user), furthermore my colleague using Ubuntu seems to be having exactly this problem as well
I notice this message with only faster G series mouse/keyboard, I was not having this message with slower MX series keyboard/mouse, however I had lag/stuttering with both models <---- This might indicate message is secondary consequence of something else or regression in the kernel
Jan 16 09:17:18 legion /usr/libexec/gdm-x-session[5839]: (EE) event12 - Logitech G703 LS: client bug: event processing lagging behind by 33ms, your system is too slow
Jan 16 09:17:18 legion /usr/libexec/gdm-x-session[5839]: (EE) client bug: timer event12 debounce: scheduled expiry is in the past (-12ms), your system is too slow
Jan 16 09:17:18 legion /usr/libexec/gdm-x-session[5839]: (EE) client bug: timer event12 debounce short: scheduled expiry is in the past (-25ms), your system is too slow
Jan 16 09:17:23 legion /usr/libexec/gdm-x-session[5839]: (EE) client bug: timer event12 debounce short: scheduled expiry is in the past (-10ms), your system is too slow
Jan 16 09:17:25 legion /usr/libexec/gdm-x-session[5839]: (II) event12 - Logitech G703 LS: SYN_DROPPED event - some input events have been lost.
I would be really grateful if someone could help tracking this issue down.
Please don't post "it solved itself", someone has to figure this out.
Regards
Offline
Everyone that is posting here, my original problem appears to have solved itself, so I'd recommend starting a new thread.
Mods, could you please close this thread?
I am using Debian thought.
This is an Arch board.
Offline
Mods, could you please close this thread?
You can unsubscribe from topics you don't want to follow.
This is an Arch board.
My apologies I was trying to help, contribute with information that this issue is note Arch issue alone, and that it might be kernel issue, based on what I have tested.
Apparently Arch community does not accept help from outside, good to know to ignore this forum in future.
Offline
Salkay wrote:Mods, could you please close this thread?
You can unsubscribe from topics you don't want to follow.
It's more a question of thread hijacking. You'll also get more exposure from a new thread.
My apologies I was trying to help, contribute with information that this issue is note Arch issue alone, and that it might be kernel issue, based on what I have tested.
Apparently Arch community does not accept help from outside, good to know to ignore this forum in future.
Sorry if I misinterpreted, but this statement from you:
I would be really grateful if someone could help tracking this issue down.
Please don't post "it solved itself", someone has to figure this out.
suggested to me that you were looking for help, not contributing help.
Last edited by Salkay (2021-01-16 09:02:28)
Offline
I agree with Salkay, if his issue is solved you - by definition - do not have the same issue.
And yes if you use Debian you shouldn't be asking for help here (... would you not find it weird if someone using Arch Linux came into a debian forum with potentially non applicable information?) you're very likely to have quite different configurations than an Arch Linux system (... e.g. are you also using the 5.10 kernel already? with which configuration? which versions of xorg/libinput? etc.)
Closing.
Offline