Opened 4 years ago

Last modified 2 months ago

#11793 new bug

EHCI: USB KVM Switch: Loss of mouse and keyboard after switching, error: 0x00088141

Reported by: vidrep Owned by: mmlr
Priority: normal Milestone: R1
Component: Drivers/USB/EHCI Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

I recently installed a StarTech 2/4 Port USB KVM switch to share a single keyboard and mouse between two PC's. After switching to "Computer 1" and back again to "Computer 2", I lose all mouse and keyboard functions, and must reboot to recover. This was tested with hrev48720 x86_gcc2, hrev48718 x86_64, and Aplha 4.1.

Attachments (19)

listdev (2.1 KB) - added by vidrep 4 years ago.
listusb (692 bytes) - added by vidrep 4 years ago.
syslog (406.0 KB) - added by vidrep 4 years ago.
previous_syslog (115.0 KB) - added by vidrep 4 years ago.
syslog.2 (294.2 KB) - added by vidrep 4 years ago.
listusb_verbose (10.7 KB) - added by vidrep 4 years ago.
syslog.3 (6.5 KB) - added by vidrep 4 years ago.
IMG_0208.JPG (2.6 MB) - added by vidrep 4 years ago.
syslog_x86_64 (132.4 KB) - added by vidrep 4 years ago.
listusb_xw9400 (9.1 KB) - added by vidrep 4 years ago.
a2_syslog (236.7 KB) - added by vidrep 3 years ago.
IMG_20181004_133811689_BURST001.jpg (2.7 MB) - added by roiredxsoto 7 months ago.
KDL screen capture when Wacom Graphire4 A6 is plugged into the Ryzen box (hrev52379 x64)
20181004-previous_syslogKDL (193.1 KB) - added by roiredxsoto 7 months ago.
Previous Syslog. Presumed, when landing on KDL after plugging Wacom
20181004-syslogAfterNewBoot (406.8 KB) - added by roiredxsoto 7 months ago.
Syslog on boot after "force power off", required due to landing on KDL
20181004-previous_syslogUSBHD (193.1 KB) - added by roiredxsoto 7 months ago.
Syslog, after plugging an external USB HD
20181004-listusb.txt (8.1 KB) - added by roiredxsoto 7 months ago.
listusb -v
20181004-A8-listusb.txt (931 bytes) - added by roiredxsoto 7 months ago.
listusb on the AMD A8 box
20181004-A8-syslog.old (512.1 KB) - added by roiredxsoto 7 months ago.
old syslog on the AMD A8 box
20181004-A8-syslogAfterLock (419.5 KB) - added by roiredxsoto 7 months ago.
syslog, presumably after the USB lock, on the AMD A8 box

Change History (42)

Changed 4 years ago by vidrep

Attachment: listdev added

Changed 4 years ago by vidrep

Attachment: listusb added

comment:1 Changed 4 years ago by diver

Could you please also attache the syslog after switching?

Changed 4 years ago by vidrep

Attachment: syslog added

Changed 4 years ago by vidrep

Attachment: previous_syslog added

comment:2 Changed 4 years ago by vidrep

I deleted all syslogs and did a reboot. First boot froze. Second boot I did the switch. Attached all syslogs from that session.

comment:3 Changed 4 years ago by vidrep

Since hrev49000 x86_gcc2 this appears to be working intermittently, usually taking 2 or 3 tries to get USB mouse and keyboard back after switching. I have attached my last syslog.

Changed 4 years ago by vidrep

Attachment: syslog.2 added

comment:4 Changed 4 years ago by vidrep

Is there any further test that I can do to provide information which may be helpful? As noted earlier, there definitely has been a change since hrev49000, where the KVM switch is now intermittent rather than not working at all.

comment:5 Changed 4 years ago by ithamar

Yes, could you attach the output of "listusb -v", giving us a little more detail on the actual usb devices attached?

I suspect we still have a race somewhere, there's an awful lot of errors (due to retries) coming out of the usb_hid driver when you switch, and that also delays the removal notification. At the very least, I think we could simply give up on the device when trying to unstall it fails (See the "usb_hid: Unable to unstall device: Device stalled" messages in the syslog).

comment:6 Changed 4 years ago by vidrep

I have attached a file "listusb_verbose" as requested.

Changed 4 years ago by vidrep

Attachment: listusb_verbose added

comment:7 Changed 4 years ago by vidrep

Just updated to hrev49020 x86_gcc2 today. I switched at least 6 times consecutively without issues. However, the issue appeared again afterwards. My system completely locked up three times while trying to edit this post. Not sure if it was related or not. Attached syslog in case it is helpful.

Last edited 4 years ago by vidrep (previous) (diff)

Changed 4 years ago by vidrep

Attachment: syslog.3 added

comment:8 Changed 4 years ago by vidrep

Tested hrev49058 x86_64 today. After a couple of successful switches it went into KDL. Attached are a photo of the KDL and a syslog.

Changed 4 years ago by vidrep

Attachment: IMG_0208.JPG added

Changed 4 years ago by vidrep

Attachment: syslog_x86_64 added

comment:9 Changed 4 years ago by ttcoder

Might be interesting to post that latter screen grab to #4157, or is it related ?

comment:10 Changed 4 years ago by stippi

I've updated to hrev49120 which contains some recent work my mmlr which sounds related, and switching now worked a couple of times. listusb consistently shows that the mouse and keyboard attached to the KVM hub are added and removed dynamically as they should be. However, the threads in the input_server do not go away. Each time I switch to the laptop, a new thread is created for the mouse, and another for the keyboard.

comment:11 Changed 4 years ago by vidrep

I have another PC (HP xw9400) which will not function whatsoever with USB devices connected through the KVM. I'll attach a listusb in case there is anything of relevance.

Changed 4 years ago by vidrep

Attachment: listusb_xw9400 added

comment:12 Changed 4 years ago by vidrep

KVM switching is not working at all with recent builds. Tested today with hrev49413. What changed? It was working at least some of the time before.

comment:13 Changed 4 years ago by vidrep

This is still an issue with hrev49663 x86_gcc2. The curious thing is that 5 or 6 months ago it was working more often than not. Now it doesn't work at all with the same hardware.

comment:14 Changed 3 years ago by vidrep

I bought a new KVM switch. This time it is a D-Link KVM-222. This one doesn't work on current builds either. It was working more often than not a year ago using the previous StarTech KVM switch. I'll re-install hrev49020 and see what happens.

comment:15 Changed 3 years ago by vidrep

I installed hrev49144 and was successfully able to switch between two PC's about 4 or 5 times.

comment:16 Changed 3 years ago by vidrep

I installed Alpha 2 on a spare partition and to my surprise both of my KVM switches are working on Alpha 2 without any issue. I have attached a Alpha 2 syslog in the hope the issue can be identified.

Changed 3 years ago by vidrep

Attachment: a2_syslog added

comment:17 Changed 3 years ago by vidrep

I'm going to leave Alpha 2 installed on the partition in the event further testing is required to resolve the problem

comment:18 Changed 7 months ago by roiredxsoto

Good day, Seems this is related to #14523, which I am experiencing right now on hrev52379 x64 on Ryzen box, though I can't reproduce the issue on hrev52379 x64 on a Vaio VGN-SR19XN, maybe because the Vaio only has USB 2.0 ports. I am adding a KDL screen picture when I plug the Wacom Graphire4 A6 to the USB front port on the Ryzen box. Plugging to the Vaio just let's me use the Wacom as a mouse, and use it in Krita, though I haven't felt the pressure sensitivity there. Later will add the Syslog from the Ryzen box. Regards, RR

Changed 7 months ago by roiredxsoto

KDL screen capture when Wacom Graphire4 A6 is plugged into the Ryzen box (hrev52379 x64)

comment:19 Changed 7 months ago by diver

Please open a new ticket agains wacom component and attach your image there.

Changed 7 months ago by roiredxsoto

Attachment: 20181004-previous_syslogKDL added

Previous Syslog. Presumed, when landing on KDL after plugging Wacom

Changed 7 months ago by roiredxsoto

Attachment: 20181004-syslogAfterNewBoot added

Syslog on boot after "force power off", required due to landing on KDL

Changed 7 months ago by roiredxsoto

Syslog, after plugging an external USB HD

comment:20 Changed 7 months ago by roiredxsoto

Added a syslog after plugging an external USB HD that also causes the USB to lock, thus resulting in the USB drive not mounting and keyboard/mouse not responding.

Haiku Aqvila 1 hrev52379 Oct 1 2018 14:59:14 x86_64 x86_64 Haiku

also add "listusb -v" file.

Changed 7 months ago by roiredxsoto

Attachment: 20181004-listusb.txt added

listusb -v

comment:21 Changed 7 months ago by roiredxsoto

Good day,

I was trying a different Tablet at home on another AMD (A8) computer and unplugging the Tablet USB wireless receiver rendered an USB lock.

Attached are the files with the different hardware marked with A8.

Thanks and Regards, RR

Changed 7 months ago by roiredxsoto

Attachment: 20181004-A8-listusb.txt added

listusb on the AMD A8 box

Changed 7 months ago by roiredxsoto

Attachment: 20181004-A8-syslog.old added

old syslog on the AMD A8 box

Changed 7 months ago by roiredxsoto

Attachment: 20181004-A8-syslogAfterLock added

syslog, presumably after the USB lock, on the AMD A8 box

comment:22 Changed 3 months ago by vidrep

This is still an issue on hrev52815 x86_64, using three different KVM switches.

comment:23 Changed 2 months ago by waddlesplash

Component: Drivers/USBDrivers/USB/EHCI
Summary: USB KVM Switch: Loss of mouse and keyboard after switchingEHCI: USB KVM Switch: Loss of mouse and keyboard after switching, error: 0x00088141
Note: See TracTickets for help on using tickets.