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: Sun, 7 Mar 2021 17:57:39 +0100 [thread overview]
Message-ID: <CA+icZUVLC7=-MsXeGQOrAe1emzGW2UwWYxh3EHGPhjR=chygoQ@mail.gmail.com> (raw)
In-Reply-To: <20210307154645.GA103559@rowland.harvard.edu>
On Sun, Mar 7, 2021 at 4:46 PM Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Sat, Mar 06, 2021 at 09:49:00PM +0100, Sedat Dilek wrote:
>
> > For testing purposes, I stopped these systemd services:
> >
> > 1. systemctl stop smartmontools.service
> >
> > 2. systemctl stop udisks2.service
> >
> > Last seen xhci-reset:
> >
> > [Sat Mar 6 21:37:40 2021] SCSI ioctl error, cmd 85, prog pool-udisksd
> >
> > So, that every 10min xhci-reset was caused by pool-udisksd from udisks2.service.
>
> You have found the cause of your problem! Great!
>
> And now, obviously order to fix the problem, you'll have to look into
> the udisks2 service. Maybe you can configure it so that it won't send
> the problem-causing commands.
>
I tried yesterday to add --debug option to the ExexStart line of
udisks2.service, but did not see anything helpful.
There exist more user-space than udisks2 causing these xhci-resets.
The cmd#s are also clear: A1 and 85 - whatever they mean.
As said with Linux v5.10.y and Linux v5.11 I have not seen this.
What about CCing linux-block and linux-scsi people?
- Sedat -
next prev parent reply other threads:[~2021-03-07 16:59 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 [this message]
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+icZUVLC7=-MsXeGQOrAe1emzGW2UwWYxh3EHGPhjR=chygoQ@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).