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:41:40 +0100 [thread overview]
Message-ID: <CA+icZUXUAVAusGBKSAtUEN1kH2PLchpi0cU+w-m67QznA7+F4A@mail.gmail.com> (raw)
In-Reply-To: <20210305193003.GE48113@rowland.harvard.edu>
On Fri, Mar 5, 2021 at 8:30 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Fri, Mar 05, 2021 at 08:22:22PM +0100, Sedat Dilek wrote:
> > The quirks match:
> >
> > [Fri Mar 5 20:06:56 2021] usb-storage 4-1:1.0: USB Mass Storage device detected
> > [Fri Mar 5 20:06:56 2021] usb-storage 4-1:1.0: Quirks match for vid
> > 174c pid 55aa: 400000
> >
> > That seems not to be the trick:
> >
> > root# LC_ALL=C dmesg -T | grep 'usb 4-1:'
> > [Fri Mar 5 20:06:55 2021] usb 4-1: new SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
> > [Fri Mar 5 20:06:55 2021] usb 4-1: New USB device found,
> > idVendor=174c, idProduct=55aa, bcdDevice= 1.00
> > [Fri Mar 5 20:06:55 2021] usb 4-1: New USB device strings: Mfr=2,
> > Product=3, SerialNumber=1
> > [Fri Mar 5 20:06:55 2021] usb 4-1: Product: MEDION HDDrive-n-GO
> > [Fri Mar 5 20:06:55 2021] usb 4-1: Manufacturer: MEDION
> > [Fri Mar 5 20:06:55 2021] usb 4-1: SerialNumber: 3180000000000000092C
> > [Fri Mar 5 20:06:57 2021] usb 4-1: reset SuperSpeed Gen 1 USB device
> > number 2 using xhci_hcd
>
> Okay, that indicates the ATA commands are being sent not by the kernel
> but by some program. I'm not sure how you can easily find out which
> program; probably the best thing to do is turn them off one by one until
> you find the one responsible.
>
I can hardly imagine which user-space tools other than powertop can
interfere here.
Any ideas?
I will remove or better comment the quirks in
/etc/modules-load.d/usb-storage.conf for now.
- Sedat -
next prev parent reply other threads:[~2021-03-05 19:42 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 [this message]
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+icZUXUAVAusGBKSAtUEN1kH2PLchpi0cU+w-m67QznA7+F4A@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).