From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208307] New: Alcor Micro Corp. Multi Flash Reader [058f:6366] keeps being detected and removed continuously
Date: Wed, 24 Jun 2020 05:05:49 +0000 [thread overview]
Message-ID: <bug-208307-208809@https.bugzilla.kernel.org/> (raw)
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: drivers_usb@kernel-bugs.kernel.org
Reporter: jian-hong@endlessm.com
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.
next reply other threads:[~2020-06-24 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 5:05 bugzilla-daemon [this message]
2020-06-24 5:09 ` [Bug 208307] Alcor Micro Corp. Multi Flash Reader [058f:6366] keeps being detected and removed continuously bugzilla-daemon
2020-06-24 5:20 ` bugzilla-daemon
2020-06-26 19:16 ` [Bug 208307] New: " Alan Stern
2020-06-26 19:16 ` [Bug 208307] " bugzilla-daemon
2020-06-29 3:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-208307-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).