linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc SCHAEFER <schaefer@alphanet.ch>
To: linux-usb@vger.kernel.org
Subject: Re: Strange issues with USB device
Date: Sat, 24 Aug 2024 08:51:03 +0200	[thread overview]
Message-ID: <ZsmC1+ko50RcvE9a@alphanet.ch> (raw)
In-Reply-To: <20240824084437.342426dd@foxbook>

Hello,

On Sat, Aug 24, 2024 at 08:44:37AM +0200, Micha?? Pecio wrote:
> What sort of kernel is this?

5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) x86_64 GNU/Linux

If required, I can try a backport 6.x, or even compile manually
a last stable 6.x

> Looks like there are some stream-related xhci_hcd bugs here. You may
> have more luck with UAS disabled if you need this system working ASAP.

There is no urgency, but yes, I will try that.

> Not only SMART is failing, but also ordinary block reads and maybe
> writes as well, so it could potentially be a risk of data loss.

I am test-qualifying this system for a few weeks now, and that bug
only happened under very high load, apparently.  So far no data
corruption (data comparison is part of the test).

> For debugging, it would help to have a reliable trigger, like "happens
> every time I run smartctl manually" or "every time I do it while
> 'cat /dev/sdc >/dev/null'" or at least "often while <some workload>".

This seems to be encountered when I do an array check with mdadm,
and when I adjust the min and max speed to the max.

> I am able to find the PCI adapter responsible for a USB bus like this:
> 
> $ ls -d /sys/bus/pci/devices/*/usb8
> /sys/bus/pci/devices/0000:02:00.0/usb8

Thank you.

  reply	other threads:[~2024-08-24  6:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 19:18 Strange issues with USB device Marc SCHAEFER
2024-08-24  6:44 ` Michał Pecio
2024-08-24  6:51   ` Marc SCHAEFER [this message]
2024-08-24  8:44     ` Michał Pecio
2024-08-26  5:17       ` Marc SCHAEFER
2024-09-03  7:48         ` Strange issues with UAS URB cancellation Michał Pecio
2024-09-03 12:55           ` Marc SCHAEFER
2024-09-03 13:22             ` Michał Pecio
2024-09-03 13:50               ` Marc SCHAEFER
2024-09-03 13:52                 ` Marc SCHAEFER
2024-09-03 13:55                   ` Marc SCHAEFER
2024-09-03 15:45                     ` Michał Pecio
2024-09-03 19:40                       ` Marc SCHAEFER
2024-09-04 14:26                         ` Mathias Nyman
2024-09-04 16:36                           ` Marc SCHAEFER
2024-09-05 13:52                             ` Mathias Nyman
2024-09-05 15:01                               ` Marc SCHAEFER
2024-09-05 15:06                                 ` Marc SCHAEFER
2024-09-05 17:24                                   ` Marc SCHAEFER
2024-09-05 18:20                                     ` Marc SCHAEFER
2024-09-09 15:24                                     ` Mathias Nyman
2024-09-09 16:21                                       ` Marc SCHAEFER
2024-09-11 14:25                                         ` Mathias Nyman
2024-09-12 15:22                                           ` Mathias Nyman
2024-08-25 16:32   ` Strange issues with USB device Marc SCHAEFER

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=ZsmC1+ko50RcvE9a@alphanet.ch \
    --to=schaefer@alphanet.ch \
    --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).