linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Mathias Nyman <mathias.nyman@intel.com>
Cc: 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: Mon, 1 Mar 2021 09:54:38 +0100	[thread overview]
Message-ID: <CA+icZUXCgW0bPcqNf+DSubBciQeBMbNX5zbjkMXinqRdkE1PfA@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUUzBvmi9SvJ4Bh8ER_+Rkm9vv9FkKwoS8ofmRsko_fJhg@mail.gmail.com>

On Wed, Feb 24, 2021 at 6:25 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
> On Wed, Feb 24, 2021 at 2:44 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
> >
> > Hi Mathias,
> >
> > I am here on Linux-v5.11-10201-gc03c21ba6f4e.
> >
> > I see a lot xhci-resets in my dmesg-log:
> >
> > root# LC_ALL=C dmesg -T | grep 'usb 4-1: reset SuperSpeed Gen 1 USB
> > device number 2 using xhci_hcd' | wc -l
> > 75
> >
> > This is what I have:
> >
> > root# lsusb -s 004:001
> > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> >
> > root# lsusb -s 004:002
> > Bus 004 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA
> > 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge,
> > ASM1153E SATA 6Gb/s bridge
> >
> > My external USB 3.0 HDD contains the partition with my Debian-system
> > and is attached to the above xhci bus/device.
> >
> > Can you enlighten what this means?
> > Is this a known issue?
> > Is there a fix around?
> >
> > BTW, in which Git tree is the xhci development happening?
> > Can you point me to it?
> >
> > I am attaching my linux-config and full dmesg-log.
> >
> > Also I have attached outputs of:
> >
> > $ sudo lsusb -vvv -d 1d6b:0003
> > $ sudo lsusb -vvv -d 174c:55aa
> >
> > If you need further information, please let me know.
> >
> > Thanks.
> >
>
> Looks like that xhci-reset happens here every 10min.
>

[ To Greg ]

The problem still remains with Linux v5.12-rc1 (see [1]).

Yesterday, I ran some disk-health checks with smartctl and gsmartcontrol.
All good.

For the first time I used badblocks from e2fsprogs Debian package:

root# LC_ALL=C badblocks -v -p 1 -s /dev/sdc -o
badblocks-v-p-1-s_dev-sdc_$(uname -r).txt
Checking blocks 0 to 976762583
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)

Good, there is no file-system corruption or badblocks or even a hardware damage.

Anyway, feedback is much appreciated.

Thanks.

Regards,
- Sedat -

[1] https://lore.kernel.org/lkml/CA+icZUUjVnBjC4AJTT9LYS4J+QbuQZUVj5XdW+iPmjxxuODVmA@mail.gmail.com/

  reply	other threads:[~2021-03-01  8:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+icZUWJyPTefHkGEgQtDO9TOM4CN_b2qPJGQVF7NE=Q=fGAEQ@mail.gmail.com>
2021-02-24 17:25 ` [xhci] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Sedat Dilek
2021-03-01  8:54   ` Sedat Dilek [this message]
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
     [not found]                           ` <CA+icZUWXBtOo+7TBGHFA=aKBs5o9hy3Po6NM0EPssu6y4SOZsQ@mail.gmail.com>
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
     [not found]                                       ` <CA+icZUWaGt2k4kdV0JHqKUkB8DySqdeUgVNnVT1BUo8aveGZOw@mail.gmail.com>
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=CA+icZUXCgW0bPcqNf+DSubBciQeBMbNX5zbjkMXinqRdkE1PfA@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 \
    /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).