[Bug 262882] [13.1-RC5] usb disconnects repeatedly, losing all attached devices on that USB hub

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 03 May 2022 09:33:47 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262882

--- Comment #69 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Hans Petter Selasky from comment #67)

FYI, I just tried plugging in a USB3 NVMe SSD and got:

uhub_reattach_port: port 2 U1 timeout failed, error=USB_ERR_IOERROR
uhub_reattach_port: port 2 U2 timeout failed, error=USB_ERR_IOERROR
usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Samsung
PSSD T7 Touch (0x04e8:0x4001)
ugen0.9: <Samsung PSSD T7 Touch> at usbus0
umass2 on uhub0
umass2: <Samsung PSSD T7 Touch, class 0/0, rev 3.20/1.00, addr 9> on usbus0
umass2:  SCSI over Bulk-Only; quirks = 0x0100
umass2:12:2: Attached to scbus12
da5 at umass-sim2 bus 2 scbus12 target 0 lun 0
da5: <Samsung PSSD T7 Touch 0> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number REPLACED
da5: 400.000MB/s transfers
da5: 953869MB (1953525168 512 byte sectors)
da5: quirks=0x2<NO_6_BYTE>

By contrast the patched RPi4B got only:

usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Samsung
PSSD T7 Touch (0x04e8:0x4001)
ugen0.4: <Samsung PSSD T7 Touch> at usbus0
umass1 on uhub0
umass1: <Samsung PSSD T7 Touch, class 0/0, rev 3.20/1.00, addr 3> on usbus0
umass1:  SCSI over Bulk-Only; quirks = 0x0100
umass1:1:1: Attached to scbus1
da1 at umass-sim1 bus 1 scbus1 target 0 lun 0
da1: <Samsung PSSD T7 Touch 0> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number S5K5NJ0R107444J
da1: 400.000MB/s transfers
da1: 953869MB (1953525168 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>

So the ThreadRipper 1950X gets the extra lines:

uhub_reattach_port: port 2 U1 timeout failed, error=USB_ERR_IOERROR
uhub_reattach_port: port 2 U2 timeout failed, error=USB_ERR_IOERROR

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