From: Maxim Fomin <maxim@fomin.one>
To: cryptsetup@lists.linux.dev
Subject: Re: mkfs on luks USB flash drive blocks forever with "reset SuperSpeed USB device" (kernel 6.7.9)
Date: Sat, 27 Apr 2024 05:05:26 +0000 [thread overview]
Message-ID: <RAfpmZ2xkxaP9hDzji38HPCaLGowefnvLadVpdY53QL2Vv8TOeWyknA4nsP4hsUDYrRJ_nZfO_tpFJvdLaANd9lGjRsrKZ-tFKo3mUwSqDQ=@fomin.one> (raw)
In-Reply-To: <10e060de0431f88edeaf7fa395965c1763a6b749.camel@mega.nu>
On Friday, April 26th, 2024 at 8:35 PM, Daniel Pouzzner <douzzer@mega.nu> wrote:
>
> [Mon Apr 22 18:08:59 2024] usb 2-2.3: reset SuperSpeed USB device number 12
> using xhci_hcd
> [Mon Apr 22 18:09:04 2024] usb 4-3: reset SuperSpeed USB device number 10 using
> xhci_hcd
>
Hi! I have similar problem with some of my disks. In my case these messages were shown often and randomly without specific disk usage pattern. The problem was solved by disabling UAS dirver for these disks by appending following parameter to kernel in GRUB:
usb_storage.quirks=XXXX:YYYY:u
where XXXX and YYYY are disk vendor and product id attributes. In your case this probably will not solve the problem because the error is triggered by specific disk usage pattern, but it will probably eliminate one possible suspect. In may case the error was caused by disk controller which flush behavior does not match fs assumptions (information got from btrfs mailing list and irc, but such errors also often happened with ext4).
Best regards,
Maxim
prev parent reply other threads:[~2024-04-27 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 19:35 mkfs on luks USB flash drive blocks forever with "reset SuperSpeed USB device" (kernel 6.7.9) Daniel Pouzzner
2024-04-27 5:05 ` Maxim Fomin [this message]
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='RAfpmZ2xkxaP9hDzji38HPCaLGowefnvLadVpdY53QL2Vv8TOeWyknA4nsP4hsUDYrRJ_nZfO_tpFJvdLaANd9lGjRsrKZ-tFKo3mUwSqDQ=@fomin.one' \
--to=maxim@fomin.one \
--cc=cryptsetup@lists.linux.dev \
/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.