From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208257] Kingston USB flash drive repeatedly disconnected after "Set SEL for device-initiated U2 failed."
Date: Sat, 25 Jul 2020 08:52:30 +0000 [thread overview]
Message-ID: <bug-208257-208809-vKoHGMUk13@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208257-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208257
--- Comment #5 from Julien Humbert (julroy67@gmail.com) ---
Created attachment 290557
--> https://bugzilla.kernel.org/attachment.cgi?id=290557&action=edit
Sony Vaio kernel 5.7.10 dmesg log
Sorry for the delay.
The exact same thing happens on my Sony Vaio SVP132A1CM (dmesg logs attached).
Disabling Link Power Management before plugging in the flash drive with "sudo
echo 0951:1666:k >/sys/module/usbcore/parameters/quirks" fixes the issue.
I have no other laptop at hand to test, but I hope you can get the informations
needed to fix it.
Thank you!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-07-25 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 7:57 [Bug 208257] New: Kingston USB flash drive repeatedly disconnected after "Set SEL for device-initiated U2 failed." bugzilla-daemon
2020-07-07 11:48 ` [Bug 208257] " bugzilla-daemon
2020-07-07 17:12 ` bugzilla-daemon
2020-07-08 12:14 ` bugzilla-daemon
2020-07-08 14:32 ` bugzilla-daemon
2020-07-25 8:52 ` bugzilla-daemon [this message]
2020-07-26 15:05 ` bugzilla-daemon
2020-08-25 18:48 ` bugzilla-daemon
2020-08-27 7:47 ` bugzilla-daemon
2020-10-29 9:33 ` bugzilla-daemon
2020-11-01 0:50 ` bugzilla-daemon
2020-11-02 9:13 ` bugzilla-daemon
2020-11-02 14:44 ` bugzilla-daemon
2020-11-02 15:52 ` bugzilla-daemon
2020-11-21 11:23 ` 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-208257-208809-vKoHGMUk13@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