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: Sat, 6 Mar 2021 11:58:08 -0500 [thread overview]
Message-ID: <20210306165808.GD74411@rowland.harvard.edu> (raw)
In-Reply-To: <CA+icZUUBpB9UFEypCFmCYc2grUC11QESNwj0_cXfut9fx0JOQA@mail.gmail.com>
On Sat, Mar 06, 2021 at 07:42:30AM +0100, Sedat Dilek wrote:
> No, with Debian-Kernel 5.10.19-1 there are no xhci-resets:
Is the kernel the only thing that is different? The rest of the
operating system and environment is exactly the same?
> But I see there is already a quirk enabled and matches my ASmedia USB
> 3.0 controller (as I have *no* usb-storage-quirks enabled):
>
> root# LC_ALL=C dmesg -T | grep -i quirks | egrep '174c|55aa'
> [Sat Mar 6 06:52:41 2021] usb-storage 4-1:1.0: Quirks match for vid
> 174c pid 55aa: 400000
Yes, this is because that type of device already has a quirk entry built
into the kernel. You can find it by searching for "174c" in the kernel
source file drivers/usb/storage/unusual_devs.h.
> Thanks Alan for all the hints and tips in the topic "usb-storage and
> quirks" and your patience.
You can try building a 5.11 kernel with the patch below. I don't know
whether it will show anything in the dmesg log when one of these resets
occurs, but it might.
If that doesn't work out, another possibility is to use git bisect to
find the commit between 5.10 and 5.11 which caused the problem to start.
Alan Stern
--- usb-devel.orig/block/scsi_ioctl.c
+++ usb-devel/block/scsi_ioctl.c
@@ -258,8 +258,11 @@ static int blk_complete_sghdr_rq(struct
hdr->host_status = host_byte(req->result);
hdr->driver_status = driver_byte(req->result);
hdr->info = 0;
- if (hdr->masked_status || hdr->host_status || hdr->driver_status)
+ if (hdr->masked_status || hdr->host_status || hdr->driver_status) {
hdr->info |= SG_INFO_CHECK;
+ printk(KERN_INFO "SCSI ioctl error, cmd %02X, prog %s\n",
+ req->cmd[0], current->comm);
+ }
hdr->resid = req->resid_len;
hdr->sb_len_wr = 0;
next prev parent reply other threads:[~2021-03-06 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 [this message]
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
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=20210306165808.GD74411@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 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).