Rootserver Sponsor

webtropia"

Donations

Please support your operating system's further development:

donate"

Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
finottiOffline
Post subject: [SOLVED] Keyboard/Mouse  PostPosted: 13.02.2018, 15:13



Joined: 2010-09-12
Posts: 476

Status: Offline
I've just DUed and updated to the new Plasma (5.12), KDE Frameworks (5.42) and kernel (4.15.0-2.slh.2-aptosid-amd64). (I think my previous update wasn't too long ago, maybe a couple of weeks.)

On reboot, the mouse and keyboard (USB) were unresponsive. I tried booting with the previous kernel (4.14.0-14.slh.1-aptosid-amd64, I think) and had the same results. Booting in rescue mode the keyboard was working. (I can't tell if the mouse was...)

Now after a new reboot, I tried pluging in another USB mouse. It did not work. After one more (I tried the usual mouse and keyboard, and still did not work), I tried the same second mouse at a different port, and it worked, but then the usual mouse and keyboard started working again.

I haven't tried to replicate the problem yet, as it is my work computer, and I was afraid I would not be able to make it work again.

I am not sure if pluging in the new mouse helped, or if the usual mouse and keyboard just needed some extra time to start to work...

In any event, here is the errors I get:

      Code:

]# journalctl -b -p err                                                                                 
-- Logs begin at Tue 2018-02-13 09:45:34 EST, end at Tue 2018-02-13 09:52:23 EST. --                                                 
Feb 13 09:45:34 finottim83 kernel: tpm tpm0: A TPM error (6) occurred attempting to read a pcr value                                 
Feb 13 09:45:34 finottim83 kernel: tpm tpm0: A TPM error (6) occurred attempting to read a pcr value                                 
Feb 13 09:45:35 finottim83 rsyslogd[793]: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.32.0 try http://
Feb 13 09:45:38 finottim83 kernel: usb 3-4: device descriptor read/64, error -110
Feb 13 09:45:53 finottim83 kernel: usb 3-4: device descriptor read/64, error -110
Feb 13 09:45:59 finottim83 kernel: usb 3-4: device descriptor read/64, error -110
Feb 13 09:46:15 finottim83 kernel: usb 3-4: device descriptor read/64, error -110
Feb 13 09:46:27 finottim83 kernel: usb 3-4: device not accepting address 8, error -62
Feb 13 09:46:38 finottim83 kernel: usb 3-4: device not accepting address 9, error -62
Feb 13 09:46:38 finottim83 kernel: usb usb3-port4: unable to enumerate USB device
Feb 13 09:47:04 finottim83 /hp-systray[2254]: hp-systray[2254]: error: option -s not recognized
Feb 13 09:47:06 finottim83 spice-vdagent[2431]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0


The USB errors were appearing when I was in rescue mode, and when I turned off the computer (with the physical buttom, that triggered the shutdown) every time.

Here is some info:

      Code:

# lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 011: ID 17ef:6019 Lenovo
Bus 003 Device 010: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 003 Device 005: ID 0461:4e04 Primax Electronics, Ltd
Bus 003 Device 003: ID 2109:2811 VIA Labs, Inc. Hub
Bus 003 Device 004: ID 17ef:a000 Lenovo
Bus 003 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


      Code:

# inxi -v3
System:    Host: finottim83 Kernel: 4.15.0-2.slh.2-aptosid-amd64 x86_64 bits: 64 gcc: 7.3.0
           Desktop: KDE Plasma 5.10.5 Distro: aptosid 2013-01 Ἑσπερίδες - kde-full - (201305050307)
Machine:   Device: desktop System: LENOVO product: 10ANS0BH00 v: ThinkCentre M83 serial: MJ01YGQ0
           Mobo: LENOVO model: SHARKBAY v: SDK0E50510 WIN serial: N/A UEFI: LENOVO v: FBKTA1AUS date: 10/22/2014
CPU:       Quad core Intel Core i7-4790 (-MT-MCP-) arch: Haswell rev.3 cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28732
           clock speeds: max: 4000 MHz 1: 1161 MHz 2: 1780 MHz 3: 1776 MHz 4: 1742 MHz 5: 1779 MHz 6: 1224 MHz
           7: 1784 MHz 8: 1725 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) driver: intel Resolution: 1920x1200@59.95hz, 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel Haswell Desktop version: 4.5 Mesa 17.3.3 Direct Render: Yes
Network:   Card: Intel Ethernet Connection I217-LM driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 44:39:c4:8f:0a:41
Drives:    HDD Total Size: 1012.2GB (67.5% used)
           ID-1: model: WDC_WD5000AAKX
           ID-2: model: Crucial_CT512M55
Info:      Processes: 274 Uptime: 19 min Memory: 2604.0/31969.5MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.181) inxi: 2.3.56


Hmm... Maybe I am not in Plasma 5.12 after all.... Here is the result of 'cat /var/log/dpkg.log | grep installed | grep -v half-installed ': https://pastebin.com/53pqt9Vg

Any help would be greatly appreciated.


Last edited by finotti on 16.02.2018, 18:55; edited 1 time in total
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: Keyboard/Mouse  PostPosted: 13.02.2018, 15:34



Joined: 2010-09-12
Posts: 476

Status: Offline
OK, so the update was not for 5.12, but a new one now seems to have done it:

      Code:

# inxi -v3
System:    Host: finottim83 Kernel: 4.15.0-2.slh.2-aptosid-amd64 x86_64 bits: 64 gcc: 7.3.0
           Desktop: KDE Plasma 5.12.0 Distro: aptosid 2013-01 Ἑσπερίδες - kde-full - (201305050307)
Machine:   Device: desktop System: LENOVO product: 10ANS0BH00 v: ThinkCentre M83 serial: MJ01YGQ0
           Mobo: LENOVO model: SHARKBAY v: SDK0E50510 WIN serial: N/A UEFI: LENOVO v: FBKTA1AUS date: 10/22/2014
CPU:       Quad core Intel Core i7-4790 (-MT-MCP-) arch: Haswell rev.3 cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28735
           clock speeds: max: 4000 MHz 1: 1536 MHz 2: 1409 MHz 3: 1591 MHz 4: 1529 MHz 5: 1801 MHz 6: 1796 MHz
           7: 1436 MHz 8: 1527 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) driver: intel Resolution: 1920x1200@59.95hz, 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel Haswell Desktop version: 4.5 Mesa 17.3.3 Direct Render: Yes
Network:   Card: Intel Ethernet Connection I217-LM driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 44:39:c4:8f:0a:41
Drives:    HDD Total Size: 1012.2GB (67.5% used)
           ID-1: model: WDC_WD5000AAKX
           ID-2: model: Crucial_CT512M55
Info:      Processes: 311 Uptime: 11 min Memory: 6047.9/31969.5MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.181) inxi: 2.3.56


And indeed, it was just a matter of waiting for the mouse and keyboard to start working.

On the other hand, with the new reboot I had to manually start the network connection... (With 'ifup eth0'.)

So, not a big deal, of course, but it is an annoying issue....
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Keyboard/Mouse  PostPosted: 13.02.2018, 22:35



Joined: 2010-08-25
Posts: 953

Status: Offline
If I understand you correctly, you're seeing the same issues both with the old (4.14, previously working) and the new (4.15) kernel, that would rule out a kernel regression. The TPM errors shouldn't be a problem, as you probably don't have TPM hardware to begin with (there could be timeout problems caused by this, but that would delay the whole boot, not just USB).

I have seen USB errors like yours, which can cause the USB subsystem to fail completely - the rest of the system boots completly though (so it is accessible via network, the power button works (it's not USB based), a PS/2 keyboard/ mouse would work, etc.). To me personally it looks as if 'something' manages to confuse a USB device (a USB kvm switch in my case) up to a point where the kernel can't reset it properly anymore (this means all systems connected to said kvm switch are affected, not just one). Powering off all involved devices (USB devices in particular; it's sufficient to physically unplug the kvm switch to power it off (drain the current) and reconnect it) sorts out the situation for me.

If you still have issues after a complete power-off - and assuming that your USB keyboard comes alive after a few minutes, it would be interesting to time how long that takes, "systemd-analyze blame" and (full) dmesg may help with that.
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: Re: RE: Keyboard/Mouse  PostPosted: 14.02.2018, 17:29



Joined: 2010-09-12
Posts: 476

Status: Offline
First, again, thanks slh for the great support, as usual!

      slh wrote:
If I understand you correctly, you're seeing the same issues both with the old (4.14, previously working) and the new (4.15) kernel, that would rule out a kernel regression. The TPM errors shouldn't be a problem, as you probably don't have TPM hardware to begin with (there could be timeout problems caused by this, but that would delay the whole boot, not just USB).


Indeed, I've been seeing that error for a long time.

      slh wrote:

I have seen USB errors like yours, which can cause the USB subsystem to fail completely - the rest of the system boots completly though (so it is accessible via network, the power button works (it's not USB based), a PS/2 keyboard/ mouse would work, etc.). To me personally it looks as if 'something' manages to confuse a USB device (a USB kvm switch in my case) up to a point where the kernel can't reset it properly anymore (this means all systems connected to said kvm switch are affected, not just one). Powering off all involved devices (USB devices in particular; it's sufficient to physically unplug the kvm switch to power it off (drain the current) and reconnect it) sorts out the situation for me.

If you still have issues after a complete power-off - and assuming that your USB keyboard comes alive after a few minutes, it would be interesting to time how long that takes, "systemd-analyze blame" and (full) dmesg may help with that.


OK, so I just tried it now. From the moment I pressed ENTER in Grub to the mouse to start to work was about 1 min and 11 secs. (BTW, this time network started automatically, as usual, but unlike last boot, when I had to manually start it.)

Then, right after logging in KDE:

      Code:

# systemd-analyze blame
           674ms apt-daily.service
           510ms udisks2.service
           494ms systemd-fsck@dev-disk-by\x2duuid-560fb5ca\x2db968\x2d4948\x2d9063\x2d7b2570580b6a.service
           281ms loadcpufreq.service
           278ms libvirtd.service
           274ms apache2.service
           256ms sshguard.service
           236ms gpm.service
           231ms distmp3.service
           216ms thermald.service
           214ms avahi-daemon.service
           212ms systemd-logind.service
           207ms lm-sensors.service
           206ms console-kit-log-system-start.service
           198ms atopacct.service
           198ms pppd-dns.service
           195ms alsa-restore.service
           194ms rsyslog.service
           191ms data3.mount
           186ms systemd-fsck@dev-disk-by\x2duuid-56dd655a\x2dc181\x2d48a8\x2d95ae\x2dc70fefa279b1.service
           180ms systemd-fsck@dev-disk-by\x2duuid-d31c605d\x2d8a89\x2d4031\x2d9448\x2d0081c87e29ec.service
           176ms dev-sda2.device
           134ms systemd-modules-load.service
           116ms data.mount
            86ms keyboard-setup.service
            69ms upower.service
            68ms systemd-timesyncd.service
            60ms data2.mount
            57ms systemd-udev-trigger.service
            54ms kdm.service
            49ms lvm2-monitor.service
            40ms systemd-journald.service
            40ms ssh.service
            36ms networking.service
            34ms polkit.service
            33ms wpa_supplicant.service
            33ms systemd-tmpfiles-setup-dev.service
            32ms user@114.service                                                                                                   
            27ms systemd-remount-fs.service                                                                                         
            27ms ifplugd.service                                                                                                     
            27ms systemd-udevd.service                                                                                               
            21ms boot-efi.mount                                                                                                     
            20ms user@1000.service                                                                                                   
            17ms ebtables.service                                                                                                   
            12ms dev-mqueue.mount                                                                                                   
            11ms systemd-tmpfiles-setup.service                                                                                     
            10ms libvirt-guests.service                                                                                             
             9ms sys-kernel-debug.mount                                                                                             
             9ms rc-local.service                                                                                                   
             9ms systemd-user-sessions.service                                                                                       
             8ms cpufrequtils.service                                                                                               
             8ms dev-disk-by\x2duuid-6fe16d4b\x2dc084\x2d48aa\x2d9902\x2df46d057b1752.swap                                           
             8ms systemd-journal-flush.service                                                                                       
             8ms console-kit-daemon.service                                                                                         
             8ms blk-availability.service                                                                                           
             6ms dev-hugepages.mount                                                                                                 
             6ms systemd-random-seed.service                                                                                         
             5ms kmod-static-nodes.service                                                                                           
             5ms systemd-update-utmp.service                                                                                         
             4ms dns-clean.service                                                                                                   
             4ms console-setup.service                                                                                               
             3ms systemd-backlight@backlight:acpi_video0.service                                                                     
             3ms sddm.service                                                                                                       
             3ms systemd-update-utmp-runlevel.service                                                                               
             3ms systemd-sysctl.service                                                                                             
             2ms resolvconf.service


If I'm reading this correctly, all took less than a second, so maybe nothing wrong there...

Here is the full output of dmesg (right after logging in KDE): https://pastebin.com/FbKB1Gs6

Again, if I am reading this correctly, the problem seems to happen here:

      Code:

[snip]
[    7.761160] usb 3-4: device descriptor read/64, error -110
[   23.634834] usb 3-4: device descriptor read/64, error -110
[   23.850816] usb 3-4: new high-speed USB device number 7 using xhci_hcd
[   29.269664] usb 3-4: device descriptor read/64, error -110
[   45.146947] usb 3-4: device descriptor read/64, error -110
[   45.248955] usb usb3-port4: attempt power cycle
[   45.876915] usb 3-4: new high-speed USB device number 8 using xhci_hcd
[   51.176965] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[   56.808998] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[   57.016847] usb 3-4: device not accepting address 8, error -62
[   57.130905] usb 3-4: new high-speed USB device number 9 using xhci_hcd
[   62.440980] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[   68.072932] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[   68.280927] usb 3-4: device not accepting address 9, error -62
[   68.280991] usb usb3-port4: unable to enumerate USB device
[snip -- USB stuff (with no errors) happens in less than a second...]


It seems it takes about a minute to get the USB going, matching my timing.

Here is what is connected:

      Code:

# lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 011: ID 17ef:6019 Lenovo
Bus 003 Device 010: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 003 Device 005: ID 0461:4e04 Primax Electronics, Ltd
Bus 003 Device 003: ID 2109:2811 VIA Labs, Inc. Hub
Bus 003 Device 012: ID 03f0:0a2a Hewlett-Packard
Bus 003 Device 004: ID 17ef:a000 Lenovo
Bus 003 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


So, I have a printer (HP), an external HD, an external hub (with nothing plugged in it), two monitors with USB connections/hubs (one has a Lenovo sound bar connected, the other has nothing), keyboard and mouse. (The card reader is internal.)

Again, thanks for the help! If slh or anyone has any suggestions, it would be great, but I can live with it if not.
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Re: RE: Keyboard/Mouse  PostPosted: 14.02.2018, 20:27



Joined: 2010-08-25
Posts: 953

Status: Offline
Hmm, there's definately something amiss with one device connected to your USB3 port. I'd try to disconnect all devices that aren't crucial for booting and reconnect them (with a reboot inbetween) one by one - ideally connect mouse/ keyboard to a USB2 port, so we can narrow down which device causes your issues.
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: Re: RE: Re: RE: Keyboard/Mouse  PostPosted: 15.02.2018, 22:51



Joined: 2010-09-12
Posts: 476

Status: Offline
      slh wrote:
Hmm, there's definately something amiss with one device connected to your USB3 port. I'd try to disconnect all devices that aren't crucial for booting and reconnect them (with a reboot inbetween) one by one - ideally connect mouse/ keyboard to a USB2 port, so we can narrow down which device causes your issues.


Thank you for your suggestion. It was the external HD, using a USB "docking station". Disconnecting the mouse and keyboard were working right away.

Does that mean that the docking station has some hardware problem?

Anyway, thanks again, slh, for your help!
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Re: RE: Re: RE: Keyboard/Mouse  PostPosted: 16.02.2018, 01:15



Joined: 2010-08-25
Posts: 953

Status: Offline
More like a firmware problem of that device, so yes, basically a hardware issue (assuming that there is no newer/ fixed firmware version).
 
 View user's profile Send private message  
Reply with quote Back to top
finottiOffline
Post subject: RE: Re: RE: Re: RE: Keyboard/Mouse  PostPosted: 16.02.2018, 18:54



Joined: 2010-09-12
Posts: 476

Status: Offline
Thanks! I will mark it as solved.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio