In article <20150622151341.GA25921@odin>, Mayuresh <[email protected]> wrote: >On Sun, Jun 21, 2015 at 10:46:30PM +0530, Mayuresh wrote: >> #dmesg | grep -i -e usb -e xhci -e ehci >> xhci0 at pci0 dev 20 function 0: vendor 8086 product 0f35 (rev. 0x0e) >> xhci0: interrupting at ioapic0 pin 20 >> xhci0: xHCI version 1.0 >> usb0 at xhci0: USB revision 2.0 >> uhub0 at usb0: NetBSD xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0 >> uhub1 at uhub0 port 3: vendor 1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, >> addr 1 >> xhci0 at pci0 dev 20 function 0: vendor 8086 product 0f35 (rev. 0x0e) >> xhci0: interrupting at ioapic0 pin 20 >> xhci0: xHCI version 1.0 >> usb0 at xhci0: USB revision 2.0 >> uhub0 at usb0: NetBSD xHCI Root Hub, class 9/0, rev 2.00/1.00, addr 0 >> uhidev0: GASIA USB KB >> V11M-oM-?M-?M-aM-!M-(M-hM^DM^FM-oM-?M-?M-oM-?M-?M-`M-(M^@, rev 1.10/2.10, >> addr 1, iclass 3/1 >> uhidev1: GASIA USB KB >> V11M-oM-?M-?M-aM-!M-(M-hM^DM^FM-oM-?M-?M-oM-?M-?M-gM-%M^V, rev 1.10/2.10, >> addr 1, iclass 3/0 >> uhub1 at uhub0 port 3: vendor 1a40 USB 2.0 Hub, class 9/0, rev 2.00/1.11, >> addr 2 >> >> Got these with USB 3.0 enabled in the bios, setting xhcidebug=1, >> connecting a usb kbd and then continue. > >Were those useful? Shall I share something more?
Yes, shows that we are not parsing some string properly. What does $ vmstat -u usbhist say? christos
