From: Sedat Dilek <sedat.dilek@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Date: Fri, 5 Mar 2021 20:05:49 +0100 [thread overview]
Message-ID: <CA+icZUXnjDwyKEoX_7KOaVd=PpvEQhpJRvwZbW_xocDfXZpUzQ@mail.gmail.com> (raw)
In-Reply-To: <20210305160728.GE38200@rowland.harvard.edu>
On Fri, Mar 5, 2021 at 5:07 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Fri, Mar 05, 2021 at 01:09:16PM +0100, Sedat Dilek wrote:
> > On Mon, Mar 1, 2021 at 4:53 PM Alan Stern <stern@rowland.harvard.edu> wrote:
> > [ ... ]
> > > You can use usbmon on bus 4 to record the USB traffic. It may indicate
> > > why the resets occur.
> > >
> >
> > Hi Alan,
> >
> > I followed the instructions in [1].
> >
> > root# modprobe -v usbmon
> >
> > root# ls /sys/kernel/debug/usb/usbmon
> > 0s 0u 1s 1t 1u 2s 2t 2u 3s 3t 3u 4s 4t 4u
> >
> > root# cat /sys/kernel/debug/usb/usbmon/4u > /tmp/usbmon-log_4u.txt
> > [ Ctrl+C ]
> >
> > I recorded 13:03 - 13:04 (one minute).
> >
> > So these xhci-resets should be included:
> >
> > [Fri Mar 5 13:03:07 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 13:03:07 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 13:03:27 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 13:03:27 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 13:03:27 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 13:03:28 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 13:03:28 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> >
> > The usbmon-log is attached.
> >
> > Unsure how to interpret the log - the kernel-doc says `raw data`.
> > How can I bring this into a human-readable format?
> > Can you give me a hand?
>
> Don't worry about trying to decode the output. To me it looks like the
> drive crashes and needs to be reset at times when the computer sends it
> an ATA command. (Not all ATA commands, but some.) You can prevent this
> by setting the following module parameter for the usb-storage driver:
>
> quirks=174c:55aa:t
>
> where the two numbers are the Vendor and Product IDs for the external
> drive, and the 't' is a quirks flag saying not to use any ATA commands.
> If this module parameter fixes the problem, we can add a permanent quirk
> setting to the kernel.
>
Thanks Alan.
I did:
[ /etc/modules-load.d/usb-storage.conf ]
# Add quirks for ATA commands for usb-storage devices connected to
ASMedia M1042 USB-3.0 controller
options usb-storage quirks=174c:55aa:t
- EOF -
It is:
/lib/modules/5.12.0-rc1-11-amd64-clang13-cfi/kernel/drivers/usb/storage/usb-storage.ko
But:
root# lsmod | grep usb | grep storage
usb_storage 90112 2 uas
scsi_mod 307200 6 sd_mod,usb_storage,uas,libata,sg,sr_mod
usbcore 385024 14
usbserial,xhci_hcd,ehci_pci,usbnet,usbhid,usb_storage,usb_wwan,uvcvideo,ehci_hcd,btusb,xhci_pci,cdc_ether,uas,option
I have not rebooted yet.
Interferences with PowerTop?
These xhci-resets happen every 10mins in a sequence of 4.
I have here a powertop.service (systemd) with passing --auto-tune option.
That was not a problem with previous Linux-kernels >= v5.12-rc1, so.
Alan, what do you think?
- Sedat -
next prev parent reply other threads:[~2021-03-05 19:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 13:44 [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Sedat Dilek
2021-02-24 17:25 ` Sedat Dilek
2021-03-01 8:54 ` Sedat Dilek
2021-03-01 15:53 ` Alan Stern
2021-03-05 12:09 ` Sedat Dilek
2021-03-05 16:07 ` Alan Stern
2021-03-05 19:05 ` Sedat Dilek [this message]
2021-03-05 19:22 ` Sedat Dilek
2021-03-05 19:30 ` Alan Stern
2021-03-05 19:41 ` Sedat Dilek
2021-03-05 19:47 ` Alan Stern
2021-03-05 19:54 ` Sedat Dilek
2021-03-06 6:42 ` Sedat Dilek
2021-03-06 16:58 ` Alan Stern
2021-03-06 19:30 ` Sedat Dilek
2021-03-06 20:26 ` Sedat Dilek
2021-03-06 20:38 ` Sedat Dilek
2021-03-06 20:49 ` Sedat Dilek
2021-03-06 20:56 ` Sedat Dilek
2021-03-06 21:02 ` Sedat Dilek
2021-03-07 15:46 ` Alan Stern
2021-03-07 16:57 ` Sedat Dilek
2021-03-07 17:07 ` Alan Stern
2021-03-12 16:57 ` Sedat Dilek
2021-03-12 17:01 ` Sedat Dilek
2021-03-12 17:41 ` Sedat Dilek
2021-03-12 18:05 ` Alan Stern
2021-03-12 18:26 ` Sedat Dilek
2021-03-12 21:56 ` Alan Stern
2021-03-05 19:25 ` Alan Stern
2021-03-05 19:37 ` Sedat Dilek
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='CA+icZUXnjDwyKEoX_7KOaVd=PpvEQhpJRvwZbW_xocDfXZpUzQ@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stern@rowland.harvard.edu \
/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).