From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208307] Alcor Micro Corp. Multi Flash Reader [058f:6366] keeps being detected and removed continuously
Date: Fri, 26 Jun 2020 19:16:40 +0000 [thread overview]
Message-ID: <bug-208307-208809-xJVVbZqrIQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208307-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208307
--- Comment #3 from Alan Stern (stern@rowland.harvard.edu) ---
On Wed, Jun 24, 2020 at 05:05:49AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> 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
> 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.
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.
next prev parent reply other threads:[~2020-06-26 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 5:05 [Bug 208307] New: Alcor Micro Corp. Multi Flash Reader [058f:6366] keeps being detected and removed continuously bugzilla-daemon
2020-06-24 5:09 ` [Bug 208307] " bugzilla-daemon
2020-06-24 5:20 ` bugzilla-daemon
2020-06-26 19:16 ` [Bug 208307] New: " Alan Stern
2020-06-26 19:16 ` bugzilla-daemon [this message]
2020-06-29 3:03 ` [Bug 208307] " 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-xJVVbZqrIQ@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).