On Mon, Mar 01, 2021 at 09:54:38AM +0100, Sedat Dilek wrote: > On Wed, Feb 24, 2021 at 6:25 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > > > On Wed, Feb 24, 2021 at 2:44 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> 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. You can use usbmon on bus 4 to record the USB traffic. It may indicate why the resets occur. Alan Stern
