On Thu, Sep 09, 2010 at 01:04:56PM -0700, John Youn wrote: > > -----Original Message----- > > From: Sarah Sharp [mailto:sarah.a.sharp@xxxxxxxxxxxxxxx] > > Sent: Thursday, September 09, 2010 12:31 PM > > To: John Youn > > Cc: Greg KH; linux-usb@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH 0/4] usbutils fixes for USB 3.0 devices > > > > On Thu, Sep 09, 2010 at 12:13:37PM -0700, John Youn wrote: > > > > > I've tested the patches with our hardware and it doesn't show up > > in > > > > lsusb. It shows up in /proc/bus/usb/devices and it also works fine > > as > > > > both a 2.0 and 3.0 hub. Downstream 3.0 and 2.0 devices show up in > > > > lsusb as well. Only the hub itself does not. There are no > > > > error/warning messages from lsusb. VIA hub also shows up fine. > > I've > > > > attached the device/hub descriptor output. > > > > > > > > Do you have CONFIG_USB_SUSPEND set to yes? That can cause USB hubs > > > > under xHCI to disappear when they can't be suspended. > > > > > > > > Sarah Sharp > > > > > > That seemed to be the issue. I can now see the details of our hub in > > lsusb. However it seg faults just before displaying the 3.0 root hub > > port status. This happens with or without our hub plugged in. The > > root hub was not displaying before with CONFIG_USB_SUSPEND=y. > > > > Which seg faults, the kernel or lsusb? Please send dmesg and USBmon > > output. > > > The seg fault is from lsusb. > > Could there be some parse error of the data coming from the root hub since it returns a 2.0 formatted hub descriptor? Yes, that's probably the issue. It should get fixed when I split the xHCI roothub into a separate USB 3.0 and USB 2.0 roothub, but I'm not sure what to do with kernels that only report the 2.0 formatted descriptor. Maybe lsusb needs to look at the type in the roothub descriptor to see how to display it? I hate to put in a lsusb hack for my kernel hack. Greg, do you have an opinion? Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
