kern/52576: USB KVM not detected when attached to USB2 port managed by xhci

[mpumford%trigati.mudcovered.org.uk@localhost]

>Number:         52576
>Category:       kern
>Synopsis:       USB KVM not detected when attached to USB2 port managed by xhci
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 27 18:45:00 +0000 2017
>Originator:     Mike Pumford
>Release:        NetBSD 8.0_BETA
>Organization:
	
>Environment:
System: NetBSD trigati.mudcovered.org.uk 8.0_BETA NetBSD 8.0_BETA (GENERIC) #5: Sat Sep 16 20:22:01 BST 2017 builder%trigati.mudcovered.org.uk@localhost:/work/netbsd/8-stable/obj.amd64/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
	My USB2 KVM is not detected when it is attached to a USB2 port 
        managed by the USB3 xhci controller. The same device on 
	NetBSD-7.1-STABLE worked in the same port. The device does 
	work in a USB3 port on the same machine which gives me a workround
	until the problem is resolved

Dmesg from failed detect:

uhub6 at uhub1 port 5: ATEN International (0x557) product 8021 (0x8021), class 9/0, rev 1.10/1.00, addr 2
uhub6: 4 ports with 4 removable, self powered
uhub6: device problem, disabling port 1


Dmesg from successful detect in USB3 port:
uhub6: at uhub3 port 2 (addr 1) disconnected
uhub6 at uhub3 port 2: ATEN International (0x557) product 8021 (0x8021), class 9/0, rev 1.10/1.00, addr 1
uhub6: 4 ports with 4 removable, self powered
uhidev0 at uhub6 port 1 configuration 1 interface 0
uhidev0: Microsoft (0x45e) MicrosoftM-BM-. 2.4GHz Transceiver v8.0 (0x745), rev 2.00/6.56, addr 2, iclass 3/1
ukbd0 at uhidev0: 8 Variable keys, 6 Array codes
wskbd0 at ukbd0: console keyboard, using wsdisplay0
uhidev1 at uhub6 port 1 configuration 1 interface 1
uhidev1: Microsoft (0x45e) MicrosoftM-BM-. 2.4GHz Transceiver v8.0 (0x745), rev 2.00/6.56, addr 2, iclass 3/1
uhidev1: 28 report ids
uhid0 at uhidev1 reportid 18: input=0, output=0, feature=1
uhid1 at uhidev1 reportid 22: input=4, output=0, feature=0
uhid2 at uhidev1 reportid 23: input=0, output=0, feature=1
ums0 at uhidev1 reportid 26: 5 buttons, W and Z dirs
wsmouse0 at ums0 mux 0
uhid3 at uhidev1 reportid 28: input=3, output=0, feature=0
uhidev2 at uhub6 port 1 configuration 1 interface 2
uhidev2: Microsoft (0x45e) MicrosoftM-BM-. 2.4GHz Transceiver v8.0 (0x745), rev 2.00/6.56, addr 2, iclass 3/0
uhidev2: 8 report ids
uhid4 at uhidev2 reportid 3: input=1, output=0, feature=0
uhid5 at uhidev2 reportid 4: input=1, output=0, feature=0
uhid6 at uhidev2 reportid 7: input=7, output=0, feature=0
uhid7 at uhidev2 reportid 8: input=1, output=0, feature=0
uhidev3 at uhub6 port 1 configuration 1 interface 3
uhidev3: Microsoft (0x45e) MicrosoftM-BM-. 2.4GHz Transceiver v8.0 (0x745), rev 2.00/6.56, addr 2, iclass 3/1
ums1 at uhidev3: 5 buttons and Z dir
wsmouse1 at ums1 mux 0


The detection output from 7.1-STABLE was almost exactly the same part from the 
uhub device number and port number.


>How-To-Repeat:
	Insert the device into a USB2 port
>Fix:
	Not sure how to fix but the same device in a USB3 port works on
	fine.