All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Sedat Dilek <sedat.dilek@gmail.com>
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 14:47:45 -0500	[thread overview]
Message-ID: <20210305194745.GF48113@rowland.harvard.edu> (raw)
In-Reply-To: <CA+icZUXUAVAusGBKSAtUEN1kH2PLchpi0cU+w-m67QznA7+F4A@mail.gmail.com>

On Fri, Mar 05, 2021 at 08:41:40PM +0100, Sedat Dilek wrote:
> On Fri, Mar 5, 2021 at 8:30 PM Alan Stern <stern@rowland.harvard.edu> wrote:

> > 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?

No.  Especially since I have no idea what programs are running on your 
computer.

Alan Stern

  reply	other threads:[~2021-03-05 19:48 UTC|newest]

Thread overview: 34+ 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 [this message]
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
     [not found] <87sfr0okqm.fsf@laptop.lockywolf.net>
2022-03-30  3:02 ` Vladimir Nikishkin
2022-03-30 11:46   ` Vladimir Nikishkin
2022-03-30 20:01     ` Alan Stern

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=20210305194745.GF48113@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=sedat.dilek@gmail.com \
    /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.