Opened 9 years ago

Last modified 2 years 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:
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 (26)

listdev (2.1 KB ) - added by vidrep 9 years ago.
listusb (692 bytes ) - added by vidrep 9 years ago.
syslog (406.0 KB ) - added by vidrep 9 years ago.
previous_syslog (115.0 KB ) - added by vidrep 9 years ago.
syslog.2 (294.2 KB ) - added by vidrep 9 years ago.
listusb_verbose (10.7 KB ) - added by vidrep 9 years ago.
syslog.3 (6.5 KB ) - added by vidrep 9 years ago.
IMG_0208.JPG (2.6 MB ) - added by vidrep 9 years ago.
syslog_x86_64 (132.4 KB ) - added by vidrep 9 years ago.
listusb_xw9400 (9.1 KB ) - added by vidrep 9 years ago.
a2_syslog (236.7 KB ) - added by vidrep 8 years ago.
IMG_20181004_133811689_BURST001.jpg (2.7 MB ) - added by roiredxsoto 6 years 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 6 years ago.
Previous Syslog. Presumed, when landing on KDL after plugging Wacom
20181004-syslogAfterNewBoot (406.8 KB ) - added by roiredxsoto 6 years ago.
Syslog on boot after "force power off", required due to landing on KDL
20181004-previous_syslogUSBHD (193.1 KB ) - added by roiredxsoto 6 years ago.
Syslog, after plugging an external USB HD
20181004-listusb.txt (8.1 KB ) - added by roiredxsoto 6 years ago.
listusb -v
20181004-A8-listusb.txt (931 bytes ) - added by roiredxsoto 6 years ago.
listusb on the AMD A8 box
20181004-A8-syslog.old (512.1 KB ) - added by roiredxsoto 6 years ago.
old syslog on the AMD A8 box
20181004-A8-syslogAfterLock (419.5 KB ) - added by roiredxsoto 6 years ago.
syslog, presumably after the USB lock, on the AMD A8 box
20200807-Switchinglog (8.7 KB ) - added by roiredxsoto 4 years ago.
Log of switching process through KVM
screenshot1.png (74.7 KB ) - added by roiredxsoto 3 years ago.
Input preferences (part 1) showing list of devices
screenshot2.png (75.5 KB ) - added by roiredxsoto 3 years ago.
Input preferences (part 2) end of list of devices
PC2_listdev.txt (2.2 KB ) - added by vidrep 2 years ago.
PC1_listdev.txt (1.7 KB ) - added by vidrep 2 years ago.
PC1_syslog.txt (140.6 KB ) - added by vidrep 2 years ago.
PC2_syslog.txt (296.8 KB ) - added by vidrep 2 years ago.

Change History (57)

by vidrep, 9 years ago

Attachment: listdev added

by vidrep, 9 years ago

Attachment: listusb added

comment:1 by diver, 9 years ago

Could you please also attache the syslog after switching?

by vidrep, 9 years ago

Attachment: syslog added

by vidrep, 9 years ago

Attachment: previous_syslog added

comment:2 by vidrep, 9 years ago

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 by vidrep, 9 years ago

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.

by vidrep, 9 years ago

Attachment: syslog.2 added

comment:4 by vidrep, 9 years ago

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 by ithamar, 9 years ago

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 by vidrep, 9 years ago

I have attached a file "listusb_verbose" as requested.

by vidrep, 9 years ago

Attachment: listusb_verbose added

comment:7 by vidrep, 9 years ago

Just updated to hrev49020 x86_gcc2 today. I switched at least 6 times consecutively without issues. Has anything changed in the last 3 days that would account for the sudden functionality?

Version 0, edited 9 years ago by vidrep (next)

by vidrep, 9 years ago

Attachment: syslog.3 added

comment:8 by vidrep, 9 years ago

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.

by vidrep, 9 years ago

Attachment: IMG_0208.JPG added

by vidrep, 9 years ago

Attachment: syslog_x86_64 added

comment:9 by ttcoder, 9 years ago

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

comment:10 by stippi, 9 years ago

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 by vidrep, 9 years ago

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.

by vidrep, 9 years ago

Attachment: listusb_xw9400 added

comment:12 by vidrep, 9 years ago

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 by vidrep, 9 years ago

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 by vidrep, 8 years ago

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 by vidrep, 8 years ago

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

comment:16 by vidrep, 8 years ago

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.

by vidrep, 8 years ago

Attachment: a2_syslog added

comment:17 by vidrep, 8 years ago

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

comment:18 by roiredxsoto, 6 years ago

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

by roiredxsoto, 6 years ago

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

comment:19 by diver, 6 years ago

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

by roiredxsoto, 6 years ago

Attachment: 20181004-previous_syslogKDL added

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

by roiredxsoto, 6 years ago

Attachment: 20181004-syslogAfterNewBoot added

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

by roiredxsoto, 6 years ago

Syslog, after plugging an external USB HD

comment:20 by roiredxsoto, 6 years ago

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.

by roiredxsoto, 6 years ago

Attachment: 20181004-listusb.txt added

listusb -v

comment:21 by roiredxsoto, 6 years ago

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

by roiredxsoto, 6 years ago

Attachment: 20181004-A8-listusb.txt added

listusb on the AMD A8 box

by roiredxsoto, 6 years ago

Attachment: 20181004-A8-syslog.old added

old syslog on the AMD A8 box

by roiredxsoto, 6 years ago

Attachment: 20181004-A8-syslogAfterLock added

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

comment:22 by vidrep, 5 years ago

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

comment:23 by waddlesplash, 5 years ago

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

comment:24 by roiredxsoto, 4 years ago

Still an issue as of 2020.06 with hrev54282 (will renew if after updating is still there, and will notify if issue disappeared).

Please let me know if you need any more info for me to provide it.

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

comment:25 by roiredxsoto, 4 years ago

Good day,

After some diggin, I presume this is related to ticket #14592 too. I did as @X512 pointed out, in the terminal and seems to be, as @waddlesplash said, a problem with XHCI.

~> uname -a
Haiku hawku 1 hrev54487 Aug  3 2020 06:48:02 x86_64 x86_64 Haiku

Attached is the output (20200807-Switchinglog) of tail -f /boot/system/var/log/syslog running in the Terminal checking the connection and disconnection of the keyboard/mouse through the switch. In the end the keyboard stops working, the mouse still does, and finally, none of them work.

Any more info/test needed let me know and will provide.
Regards,
RR

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

by roiredxsoto, 4 years ago

Attachment: 20200807-Switchinglog added

Log of switching process through KVM

comment:26 by roiredxsoto, 4 years ago

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

comment:27 by roiredxsoto, 3 years ago

Good day,

Haiku hawku 1 hrev55026 Apr  5 2021 07:18:13 x86_64 x86_64 Haiku

Today, the switching seems to have improved and I haven't got any problems so far with switching from Windows to Haiku and Viceversa.
The issue I'm facing right now relates to Input preferences window where each time I switch back to Haiku, new Keyboard and mouse Devices appear on the list.
listusb command still reports properly, only showing the connected devices:

1ea7:0907 /dev/bus/usb/0/10/2 "SHARKOON Technologies GmbH" "USB-HID Gaming Keyboard" ver. 0300
045e:0773 /dev/bus/usb/0/10/3 "Microsoft Corp." "Microsoft Nano Transceiver v1.0" ver. 0674
05e3:0610 /dev/bus/usb/0/10/hub "Genesys Logic, Inc." "4-port hub" ver. 9226
056a:0015 /dev/bus/usb/0/12 "Wacom Co., Ltd" "CTE-440 [Graphire4 (4x5)]" ver. 0403
0000:0000 /dev/bus/usb/0/hub "HAIKU Inc." "XHCI RootHub" ver. 0300
0000:0000 /dev/bus/usb/1/hub "HAIKU Inc." "XHCI RootHub" ver. 0300
0000:0000 /dev/bus/usb/2/hub "HAIKU Inc." "XHCI RootHub" ver. 0300

The pictures attached show the growing list of devices.

Regards,
RR

by roiredxsoto, 3 years ago

Attachment: screenshot1.png added

Input preferences (part 1) showing list of devices

by roiredxsoto, 3 years ago

Attachment: screenshot2.png added

Input preferences (part 2) end of list of devices

comment:28 by pulkomandy, 3 years ago

This ticket is for the EHCI driver, but your logs show that you are using XHCI. So it is a different problem.

Vidrep, since you originally reported this, can you confirm if in your case problems are with EHCI (USB2)? Or do you also have problems with USB3?

comment:29 by vidrep, 3 years ago

No difference whether I use USB2 or USB3 ports.

in reply to:  28 comment:30 by roiredxsoto, 3 years ago

Replying to pulkomandy:

This ticket is for the EHCI driver, but your logs show that you are using XHCI. So it is a different problem.

All right. Didn't notice that. Therefore I'll keep reporting this issue in the Ticket I opened (#14523) instead of here.

Apologies.
Regards,
RR

Last edited 3 years ago by roiredxsoto (previous) (diff)

comment:31 by vidrep, 2 years ago

Tested with hrev55608 x86_64 Both PC's connected to the KVM switch will freeze after switching a couple of times. Attached are listdev and syslog for each PC in this configuration.

by vidrep, 2 years ago

Attachment: PC2_listdev.txt added

by vidrep, 2 years ago

Attachment: PC1_listdev.txt added

by vidrep, 2 years ago

Attachment: PC1_syslog.txt added

by vidrep, 2 years ago

Attachment: PC2_syslog.txt added
Note: See TracTickets for help on using tickets.