[Bug 258839] ure(4) needs a detach/reattch to work on SUPER

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 01 Oct 2021 11:21:08 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258839

            Bug ID: 258839
           Summary: ure(4) needs a detach/reattch to work on SUPER
           Product: Base System
           Version: CURRENT
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: usb
          Assignee: usb@FreeBSD.org
          Reporter: bz@FreeBSD.org

Hi,

I had this USB dongle for a long time on a single direct XHCI root port and it
came up with 480 speed and worked without issues (the HIGH speed only is
another issue on that port).

For debugging other things I moved it to a USB3 HUB port attached to a 2nd (but
same dwc3 xhci root) port and ther eit comes up as SUPER speed but after very
little use it has a hiccup.

When running ifconfig then it slightly hangs and then reports a media status of
100 half (the addresses are printed so I assume that query takes time).
It will no longer pass packets at that point.

Doing an ue0 down up will (a) cause the driver to detach and re-attach, and (b)
after it comes back up again it seems to work flawlessly.

I have yet to take usb traces but in case it sounds familar to anyone..
I cannot rule out that it is something specific to the roots/hub currently
but I wanted to document the status quo before I start messing around more.


ugen1.5: <Realtek USB 10/100/1000 LAN> at usbus1, cfg=0 md=HOST spd=SUPER
(5.0Gbps) pwr=ON (72mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0300 
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0009 
  idVendor = 0x0bda 
  idProduct = 0x8153 
  bcdDevice = 0x3000 
  iManufacturer = 0x0001  <Realtek>
  iProduct = 0x0002  <USB 10/100/1000 LAN>
  iSerialNumber = 0x0006  <000001>
  bNumConfigurations = 0x0002

-- 
You are receiving this mail because:
You are the assignee for the bug.