linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:37:26 +0100	[thread overview]
Message-ID: <CA+icZUXHnc-Qd9NhwxFx3+LQakNTWmS_RRYsTAY8-gO8wc219Q@mail.gmail.com> (raw)
In-Reply-To: <20210305192529.GD48113@rowland.harvard.edu>

On Fri, Mar 5, 2021 at 8:25 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Fri, Mar 05, 2021 at 08:05:49PM +0100, Sedat Dilek wrote:
> > On Fri, Mar 5, 2021 at 5:07 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> > > 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 don't understand.  What is the point of this listing?
>

I was confused about lsmod and modinfo output:
usb-storage.ko (kernel-module name) VS. usb_storage (modinfo: name: usb_storage)

> > I have not rebooted yet.
>
> Depending on how your system is set up, the new usb-storage.conf file
> might need to be copied into the initramfs image.
>

That seems not to be needed.

> However, you don't need to reload the driver module or reboot.  To make
> the new quirk take effect, all you have to do is write 174c:55aa:t to
> /sys/module/usb_storage/parameters/quirks.
>

OK, keep this for next USB(mon) testings before doing a reboot.

> > Interferences with PowerTop?
>
> Maybe.  It's entirely possible that PowerTop or some other program is
> issuing the troublesome ATA commands.
>
> > 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?
>
> Try turning the service off and see if that makes any difference.
>

NO, it is not powertop.service causing the xhci-resets.

- Sedat -

      reply	other threads:[~2021-03-05 19:38 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
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 [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=CA+icZUXHnc-Qd9NhwxFx3+LQakNTWmS_RRYsTAY8-gO8wc219Q@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).