Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: USB device detection problem

On 25/08/2017 13:51, Nick Hudson wrote:
On 06/25/17 11:06, Mike Pumford wrote:
Just trying to fire up NetBSD 8-BETA on my builder machine but I've run into a bit of a showstopper (for me) bug in the new kernel.

On NetBSD 7-STABLE (Apr 14th) my KVM is detected as:
uhub6 at uhub1 port 6:  , class 9/0, rev 1.10/1.00, addr 1
uhub6: 4 ports with 4 removable, self powered

And then the kernel carries on an finds the keyboard and mouse downstream of that device.

In NetBSD 8 I get:
uhub6 at uhub1 port 6: vendor 0557 (0x557) product 8021 (0x8021), class 9/0, rev 1.10/1.00, addr 1
uhub6: 4 ports with 4 removable, self powered

<ATA and other uhub detection removed>
uhub6: device problem, disabling port 1

This means I have no console keyboard. Anything I can do to help track this down?

I've also attached full dmesg from Both 8-BETA and 7.1-STABLE.

So, to be clear these builds are from recent netbsd-8 and netbsd-7 trees and therefore both have approximately the same sys/dev/usb code?

Just got back from a holiday so I'm still catching up. Yes they were from recent netbsd-8 and netbsd-7. Probably fetched and built just before I sent out the e-mail.

If so, I wonder if using msi interrupts is part of the problem?

-xhci0 at pci0 dev 20 function 0: vendor 0x8086 product 0x8cb1 (rev. 0x00)
-xhci0: interrupting at ioapic0 pin 21
+xhci0 at pci0 dev 20 function 0: vendor 8086 product 8cb1 (rev. 0x00)
+xhci0: interrupting at msi2 vec 0

Can you check interrupt counters (vmstat -i) ?

I will do that a little bit later on. One oddity is that if I move the keyboard/mouse connection to a USB3 port rather than one of the USB2 only ports it actually works perfectly on 8-BETA.




Home | Main Index | Thread Index | Old Index