From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219773] External USB disk drive and SSD corruption while connected to USB 3 ports.
Date: Mon, 17 Feb 2025 15:53:13 +0000 [thread overview]
Message-ID: <bug-219773-208809-hUL2TPAD40@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219773-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219773
--- Comment #16 from Frederic Bezies (fredbezies@gmail.com) ---
(In reply to Alan Stern from comment #15)
> One possibility is that the SSD doesn't like LPM. You can disable LPM by
> writing
>
> 0dd8:0562:k
>
> to /sys/module/usbcore/parameters/quirks before plugging in the drive.
As I said in comment 9, I don't any have access at all to the external SSD with
the usv reset spam in dmesg.
>
> If that doesn't make any difference, you can try collecting a usbmon trace
> that shows the error occurring. Warning: The usbmon output file is likely
> to be enormous, and the interesting part will be only the stuff that gets
> written when the error happens.
I will need to buy another external SSD and see it I still see this bug. But it
will take me around two weeks to do so :/
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-02-17 15:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 21:51 [Bug 219773] New: External USB disk drive and SSD corruption bugzilla-daemon
2025-02-11 21:52 ` [Bug 219773] " bugzilla-daemon
2025-02-12 18:27 ` [Bug 219773] External USB disk drive and SSD corruption while connected to USB 3 ports bugzilla-daemon
2025-02-12 18:28 ` bugzilla-daemon
2025-02-14 10:00 ` bugzilla-daemon
2025-02-15 12:38 ` bugzilla-daemon
2025-02-15 15:09 ` bugzilla-daemon
2025-02-15 15:09 ` bugzilla-daemon
2025-02-15 15:58 ` bugzilla-daemon
2025-02-15 16:51 ` bugzilla-daemon
2025-02-15 18:41 ` bugzilla-daemon
2025-02-15 18:45 ` bugzilla-daemon
2025-02-15 20:08 ` bugzilla-daemon
2025-02-15 20:25 ` bugzilla-daemon
2025-02-16 16:24 ` bugzilla-daemon
2025-02-17 14:36 ` bugzilla-daemon
2025-02-17 15:53 ` bugzilla-daemon [this message]
2025-02-17 17:48 ` bugzilla-daemon
2025-02-20 9:32 ` bugzilla-daemon
2025-02-20 9:34 ` bugzilla-daemon
2025-02-27 13:21 ` bugzilla-daemon
2025-02-27 13:22 ` bugzilla-daemon
2025-02-27 13:25 ` 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-219773-208809-hUL2TPAD40@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.