On Sunday 06 January 2013 02:36:38 Eitan Adler wrote: > On 4 January 2013 17:01, Hans Petter Selasky <hsela...@c2i.net> wrote: > > On Friday 04 January 2013 22:50:38 Eitan Adler wrote: > >> On 4 January 2013 16:41, Hans Petter Selasky <hsela...@c2i.net> wrote: > >> > This typically means set address failed, which in the XHCI is done in > >> > "HW". I'll look into if I find some time. Not sure what we can do > >> > about it. > > > > Hi, > > > >> As I mentioned - it works in 9.1 so *something* regressed. > > > > The only which I can think of which caused this is the recently added > > ETRON patches. You can look in the xhci.c revision history and revert > > from the top? There aren't that many patches made in that area. > > I tested in stable/9 and it is broken in stable too. This does not > have the relevant patch applied I think. > > >> > You can try set first set config 255 and the config 0 on the parent > >> > HUB of this device using usbconfig. > >> > >> I'm not sure what you mean here. What command should I run? > > > > usbconfig -d X.1 set_config 255 > > usbconfig -d X.1 set_config 0 > > done. It did not help.
Could you do a diff between 9.1 and 9-stable sources and see what is changed? Might be some BIOS/ACPI stuff too. --HPS _______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"