[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUVLC7=-MsXeGQOrAe1emzGW2UwWYxh3EHGPhjR=chygoQ@mail.gmail.com>
Date: Sun, 7 Mar 2021 17:57:39 +0100
From: Sedat Dilek <sedat.dilek@...il.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Mathias Nyman <mathias.nyman@...el.com>, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
On Sun, Mar 7, 2021 at 4:46 PM Alan Stern <stern@...land.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 -
Powered by blists - more mailing lists