Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Kernel resets mouse - X unusable on mouse wheel rotate
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Nheghathivhistha
n00b
n00b


Joined: 18 Jan 2014
Posts: 9

PostPosted: Thu Nov 07, 2019 7:48 am    Post subject: Kernel resets mouse - X unusable on mouse wheel rotate Reply with quote

It looks like that after some of latest updates on ~amd64 I am not able to use KDE any more.
Sddm starts and shows greeter. Then screen goes blank and at next moment sddm greeter is visible again. When I type my password it is accepted and KDE session seems to be starting in the background.
When sddm is stopped (/etc/init.d/xdm stop) and X started using startx it works until mouse wheel is rotated to scroll some started application window content (xfreerdp was the case in the morning) or mouse is moved faster. Then screen goes blank and then goes back with content scrolled like nothing bad happened. Left click and right click are not causing troubles, slower mouse cursor moves not too.

There is not so much in logs of Xorg and Sddm but kernel resets mouse:
Code:
Nov  7 06:18:28 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:19:49 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:20:32 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:21:23 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:22:38 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:23:11 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:26:15 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:27:11 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:27:33 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:29:10 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:29:12 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:29:42 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:29:53 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:30:39 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:31:46 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:33:21 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Nov  7 06:33:36 srv5 kernel: usb 3-3: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd

etc.

Kernel is 5.3.7-gentoo, I will try the latest available and earlier versions in the evening.

Xorg.0.log:
Code:
[  4543.663] (II) UnloadModule: "libinput"
[  4543.663] (II) UnloadModule: "libinput"
[  4543.663] (II) UnloadModule: "libinput"
[  4543.663] (II) UnloadModule: "libinput"
[  4543.663] (II) UnloadModule: "libinput"
[  4543.663] (II) UnloadModule: "libinput"
[  4543.663] (II) UnloadModule: "libinput"

/var/log/sddm.log:
Code:
[06:14:35.541] (WW) DAEMON: Signal received: SIGTERM
[06:14:35.541] (II) DAEMON: Greeter stopping...
[06:14:35.541] (II) DAEMON: Socket server stopping...
[06:14:35.541] (II) DAEMON: Socket server stopped.
[06:14:35.541] (II) DAEMON: Display server stopping...
[06:14:35.548] (II) DAEMON: Display server stopped.
[06:14:35.548] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[06:14:35.549] (II) DAEMON: Greeter stopping...
[06:14:35.549] (WW) DAEMON: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
[06:14:45.885] (II) DAEMON: Initializing...
[06:14:45.889] (II) DAEMON: Starting...
[06:14:45.890] (II) DAEMON: Console kit interface found
[06:14:45.890] (II) DAEMON: Adding new display on vt 7 ...
[06:14:45.890] (II) DAEMON: Loading theme configuration from ""
[06:14:45.890] (II) DAEMON: Display server starting...
[06:14:45.890] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{3bc687b0-973e-46a8-b1b7-b3371de8476e} -background none -noreset -displayfd 17 -seat seat0 vt7
[06:14:46.268] (II) DAEMON: Setting default cursor
[06:14:46.271] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[06:14:46.273] (II) DAEMON: Display server started.
[06:14:46.273] (II) DAEMON: Socket server starting...
[06:14:46.273] (II) DAEMON: Socket server started.
[06:14:46.273] (II) DAEMON: Loading theme configuration from ""
[06:14:46.273] (II) DAEMON: Greeter starting...
[06:14:46.274] (II) DAEMON: Adding cookie to "/var/run/sddm/{3bc687b0-973e-46a8-b1b7-b3371de8476e}"
[06:14:46.278] (II) HELPER: [PAM] Starting...
[06:14:46.278] (II) HELPER: [PAM] Authenticating...
[06:14:46.278] (II) HELPER: [PAM] returning.
[06:14:46.279] (II) DAEMON: Greeter session started successfully
[06:14:46.302] (II) DAEMON: Message received from greeter: Connect
[06:15:05.237] (WW) DAEMON: Signal received: SIGTERM
[06:15:05.237] (II) DAEMON: Greeter stopping...
[06:15:05.237] (II) DAEMON: Socket server stopping...
[06:15:05.237] (II) DAEMON: Socket server stopped.
[06:15:05.237] (II) DAEMON: Display server stopping...
[06:15:05.243] (II) DAEMON: Display server stopped.
[06:15:05.243] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[06:15:05.245] (II) DAEMON: Greeter stopping...
[06:15:05.245] (WW) DAEMON: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
[06:22:40.722] (II) DAEMON: Initializing...

Can it be newest kernel problem? I will try older and newest kernel and will test to replace mouse.
Thank you.

----------------

Tested new mouse - sddm greeter is shutting down and starting up the same way as before, the same USB reset messages from kernel.
Rebooted to =sys-kernel/gentoo-sources-5.3.8 and all is fine.

[Moderator edit: Moved poster's self-response into main post, then deleted that self-response to return the thread to the unanswered list.

OP: Generally, if post length permits, you should edit extra information into your first post instead of replying to it. Some users run a canned search for threads with zero replies as a way of finding posts to answer. When you replied to yourself, you removed your thread from that list, even though you were not replying to announce that the thread was solved. Thus, they would no longer see your thread on the list of unanswered threads.
-Hu]
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum