Re: regression: if_rue device doesn't attach on HEAD
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
Re: regression: if_rue device doesn't attach on HEAD
On 6 January 2013 03:52, Hans Petter Selasky hsela...@c2i.net wrote: Could you do a diff between 9.1 and 9-stable sources and see what is changed? Might be some BIOS/ACPI stuff too. I havn't had a chance to go much beyond this but - 9.1-RELEASE is known to be working (this is r243808, right?) - r245084 is broken - r26 is broken - r244127 is broken - r243968 is broken -- Eitan Adler ___ 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
Re: regression: if_rue device doesn't attach on HEAD
On Sunday 06 January 2013 19:00:03 Eitan Adler wrote: On 6 January 2013 03:52, Hans Petter Selasky hsela...@c2i.net wrote: Could you do a diff between 9.1 and 9-stable sources and see what is changed? Might be some BIOS/ACPI stuff too. I havn't had a chance to go much beyond this but - 9.1-RELEASE is known to be working (this is r243808, right?) - r245084 is broken - r26 is broken - r244127 is broken - r243968 is broken Hi, From what I can see from the SVN log, there has been no relevant changes in the USB core since r242xxx: http://svnweb.freebsd.org/base/stable/9/sys/dev/usb/ I suspect the problem is somewhere else, like PCI/BIOS/ACPI. --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
Re: regression: if_rue device doesn't attach on HEAD
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. -- Eitan Adler ___ 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
Re: regression: if_rue device doesn't attach on HEAD
On Friday 04 January 2013 05:45:00 Eitan Adler wrote: I have a USB nic which worked in 9.1 but regressed in HEAD and appears as an unrecognized device. I have not had time to properly bisect this issue. Any suggestions or pointers are appreciated: ugen2.3: USB 10100 LAN USBKR100 bLength = 0x0012 bDescriptorType = 0x0001 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x idVendor = 0x0bda idProduct = 0x8150 bcdDevice = 0x0100 iManufacturer = 0x0001 USBK100 LAN iProduct = 0x0002 USB 10/100 LAN iSerialNumber = 0x0003 8628 bNumConfigurations = 0x0001 Did you kldload if_rue? Did you enable devd? --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
Re: regression: if_rue device doesn't attach on HEAD
On 4 January 2013 03:21, Hans Petter Selasky hsela...@c2i.net wrote: Did you kldload if_rue? Did you enable devd? Default Default - it worked in 9.1 so I assumed it should work the same in HEAD. I'll try explicitly doing so when I get home. -- Eitan Adler ___ 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
Re: regression: if_rue device doesn't attach on HEAD
On 4 January 2013 03:21, Hans Petter Selasky hsela...@c2i.net wrote: Did you kldload if_rue? Yes. This did nothing to help. Did you enable devd? Yes, this was already enabled. Use(full|less) debug info: I now see xhci_do_command: Command timeout! device init 2 failed USB_ERR_TIMEOUT which I did not see before in dmesg. -- Eitan Adler ___ 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
Re: regression: if_rue device doesn't attach on HEAD
On Friday 04 January 2013 22:31:31 Eitan Adler wrote: On 4 January 2013 03:21, Hans Petter Selasky hsela...@c2i.net wrote: Did you kldload if_rue? Yes. This did nothing to help. Did you enable devd? Yes, this was already enabled. Use(full|less) debug info: I now see xhci_do_command: Command timeout! device init 2 failed USB_ERR_TIMEOUT which I did not see before in dmesg. Hi, 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. You can try set first set config 255 and the config 0 on the parent HUB of this device using usbconfig. --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
Re: regression: if_rue device doesn't attach on HEAD
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. As I mentioned - it works in 9.1 so *something* regressed. 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? -- Eitan Adler ___ 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
Re: regression: if_rue device doesn't attach on HEAD
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. As I mentioned - it works in 9.1 so *something* regressed. 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? What XHCI hardware is this? --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
Re: regression: if_rue device doesn't attach on HEAD
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. 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 --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
regression: if_rue device doesn't attach on HEAD
I have a USB nic which worked in 9.1 but regressed in HEAD and appears as an unrecognized device. I have not had time to properly bisect this issue. Any suggestions or pointers are appreciated: ugen2.3: USB 10100 LAN USBKR100 bLength = 0x0012 bDescriptorType = 0x0001 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x idVendor = 0x0bda idProduct = 0x8150 bcdDevice = 0x0100 iManufacturer = 0x0001 USBK100 LAN iProduct = 0x0002 USB 10/100 LAN iSerialNumber = 0x0003 8628 bNumConfigurations = 0x0001 -- Eitan Adler ___ 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
