From: Ross Zwisler <zwisler@google.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"kernel@collabora.com" <kernel@collabora.com>
Subject: Re: xhci problem -> general protection fault
Date: Wed, 9 Dec 2020 11:54:13 -0700 [thread overview]
Message-ID: <X9EdVbO08Y8Ohih5@google.com> (raw)
In-Reply-To: <068b49cd-4afa-7adb-572b-634b1728744d@linux.intel.com>
On Wed, Dec 09, 2020 at 03:11:14PM +0200, Mathias Nyman wrote:
<>
> I was testing with Andrzej's script against a g_zero gadget.
> I could trigger many similar issues as those he reported, but not this
> dequeue issue you see.
>
> The rewrite resolved all issues I saw. Script was running without issues
> over night. (tested against both USB2 and USB3).
>
> I haven't tried with two devices simultaneously, I could try that.
>
> Could you share more details about the system you have, what xhci
> controller do you have?
Sure. I'm running with the following CPU:
Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz
with 72 virtual cores, if that matters.
The full output of "lsusb -vvv" can be found here:
https://gist.github.com/rzwisler/8c61f10c7a9642cbc6fffe1daadfa8cc
And here is the xhci entry in "lspci -vvv":
00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI Controller (rev 09) (prog-if 30 [XHCI])
Subsystem: Lenovo C620 Series Chipset Family USB 3.0 xHCI Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 38
NUMA node: 0
IOMMU group: 16
Region 0: Memory at 90320000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
We've seen this issue on a variety of hardware from Lenovo and HP, so it's not
specific to this specific workstation model (Lenovo P920).
I repro the issue by running the bulk-cancel program against my "servo"
hardware, which is debugging hardware for Chromebooks. As I said, though, I
can repro it easily without having a device attached, so I *think* all you
need is a device which handles BULK IN commands. I've got 2, and if I run
against both my system repros the issue in under a minute, usually. With 1 it
takes a little longer but still repros, so I don't think it's an interaction
between the two devices.
Please let me know if I can provide anything else of value.
next prev parent reply other threads:[~2020-12-09 18:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 15:30 xhci problem -> general protection fault Andrzej Pietrasiewicz
2020-09-18 10:50 ` Mathias Nyman
2020-09-18 14:20 ` Andrzej Pietrasiewicz
2020-09-25 13:40 ` Mathias Nyman
2020-09-25 21:05 ` Ross Zwisler
2020-09-28 13:32 ` Andrzej Pietrasiewicz
2020-09-29 7:13 ` Mathias Nyman
2020-10-01 14:13 ` Andrzej Pietrasiewicz
2020-09-28 22:35 ` Mathias Nyman
2020-10-01 16:43 ` zwisler
2020-10-12 19:20 ` Mathias Nyman
2020-10-12 21:53 ` zwisler
2020-10-13 7:49 ` Mathias Nyman
2020-10-13 8:29 ` Andrzej Pietrasiewicz
2020-10-13 16:44 ` zwisler
2020-11-19 16:52 ` Ross Zwisler
2020-11-23 15:06 ` Mathias Nyman
2020-12-02 22:59 ` Ross Zwisler
2020-12-04 18:07 ` Mathias Nyman
2020-12-08 17:24 ` Ross Zwisler
2020-12-09 13:11 ` Mathias Nyman
2020-12-09 18:54 ` Ross Zwisler [this message]
2020-12-30 12:33 ` Mathias Nyman
2021-01-06 18:52 ` Ross Zwisler
2021-01-07 8:57 ` Mathias Nyman
2021-01-07 16:07 ` Ross Zwisler
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=X9EdVbO08Y8Ohih5@google.com \
--to=zwisler@google.com \
--cc=andrzej.p@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.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).