New: Alcor Micro Corp. Multi Flash Reader [058f:6366] keeps being detected and removed continuously

https://bugzilla.kernel.org/show_bug.cgi?id=208307

            Bug ID: 208307
           Summary: Alcor Micro Corp. Multi Flash Reader [058f:6366] keeps
                    being detected and removed continuously
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.8-rc2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 289855
--> https://bugzilla.kernel.org/attachment.cgi?id=289855&action=edit
The full dmesg

We have a laptop equipped with AMD Ryzen 5 4500U with Radeon Graphics. The Alcor Micro Corp. Multi Flash Reader keeps being detected and removed continuously. Then, once the storage modules try to access it, there will be the failure. These messages keep showing up like floods in the kernel message log.

[    8.371606] usb 3-1: new high-speed USB device number 9 using xhci_hcd
[    8.501528] usb 3-1: New USB device found, idVendor=058f, idProduct=6366,
bcdDevice= 1.00
[    8.501529] usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[    8.501530] usb 3-1: Product: Flash Card Reader/Writer
[    8.501531] usb 3-1: Manufacturer: Generic
[    8.501531] usb 3-1: SerialNumber: 058F63666485
[    8.501914] usb-storage 3-1:1.0: USB Mass Storage device detected
[    8.502053] scsi host3: usb-storage 3-1:1.0
[    9.547020] scsi 3:0:0:0: Direct-Access     Multiple Card  Reader     1.00
PQ: 0 ANSI: 4
[    9.547104] sd 3:0:0:0: Attached scsi generic sg1 type 0
[    9.966614] usb 3-1: reset high-speed USB device number 9 using xhci_hcd
[   10.204353] usb 3-1: USB disconnect, device number 9
[   10.211655] sd 3:0:0:0: [sdb] Read Capacity(10) failed: Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   10.211657] sd 3:0:0:0: [sdb] Sense not available.
[   10.211661] sd 3:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[   10.211662] sd 3:0:0:0: [sdb] 0-byte physical blocks
[   10.211670] sd 3:0:0:0: [sdb] Write Protect is off
[   10.211671] sd 3:0:0:0: [sdb] Mode Sense: 00 00 00 00
[   10.211678] sd 3:0:0:0: [sdb] Asking for cache data failed
[   10.211678] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[   10.218103] sd 3:0:0:0: [sdb] Read Capacity(10) failed: Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[   10.218106] sd 3:0:0:0: [sdb] Sense not available.
[   10.218132] sd 3:0:0:0: [sdb] Attached SCSI removable disk

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=208307

--- Comment #1 from [email protected] ---
Here is the USB tree and the Multi Flash Reader

$ lsusb -tv
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    |__ Port 1: Dev 97, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 2: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 2: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 3: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 3: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 480M

$ lsusb -vd 058f:6366

Bus 003 Device 055: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Couldn't open device, some information will be missing Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.01

  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x058f Alcor Micro Corp.
  idProduct          0x6366 Multi Flash Reader
  bcdDevice            1.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=208307

--- Comment #2 from [email protected] ---
Created attachment 289857
--> https://bugzilla.kernel.org/attachment.cgi?id=289857&action=edit
The raw trace by usbmon listening on bus 3

You are receiving this mail because:
You are watching the assignee of the bug.

Try disabling Link Power Management for this device:

echo 058f:6366:k >/sys/module/usbcore/parameters/quirks

Alan Stern

https://bugzilla.kernel.org/show_bug.cgi?id=208307

--- Comment #3 from Alan Stern ([email protected]) ---

Try disabling Link Power Management for this device:

echo 058f:6366:k >/sys/module/usbcore/parameters/quirks

Alan Stern

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=208307

--- Comment #4 from [email protected] ---
(In reply to Alan Stern from comment #3)

Thanks for your information. But the issue still happen, after the quirk is applied.

You are receiving this mail because:
You are watching the assignee of the bug.