From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 206901] Valve Index HMD breaks the USB controller it's connected into
Date: Thu, 26 Mar 2020 03:26:27 +0000 [thread overview]
Message-ID: <bug-206901-208809-YbMVc4CgQY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206901-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206901
--- Comment #2 from Carlo Wood (carlo@alinoe.com) ---
I had a LOT more problems with the USB 3 on my ASUS Sabertooth 990FX
motherboard, so I bought a PCI Express card (PEXUSB3S44V from Startech, see
https://www.startech.com/nl/en/Cards-Adapters/USB-3.0/Cards/PCI-Express-USB-3-Card-4-Dedicated-Channels-4-Port~PEXUSB3S44V)
basically because it is the most expensive card you can get (I was hoping to
rule out certain things with that).
As a result I no longer needed to disable iommu in the BIOS or pass iommu=soft
as kernel boot parameter. But the above bug remained (although less
frequently).
The PEXUSB3S44V uses the μPD720202 host controller chip (four of them I think).
Documents here
https://www.renesas.com/us/en/products/usb-assp/upd720202.html#documents
This bug has the feel of https://bugzilla.kernel.org/show_bug.cgi?id=65021
from 2013 (kernel 3.x). A patch that has been in the kernel for long related
to that bug is https://www.spinics.net/lists/linux-usb/msg122678.html a few
people said was fixing the issue for them.
However, I added debug output to the module and in my case it never even gets
to the line
> xhci->quirks |= XHCI_AVOID_BEI;
so no wonder that patch didn't solve it for me ;).
Hence, apparently pdev->vendor != PCI_VENDOR_ID_INTEL for me.
But maybe it should be? The μPD720202 specs say it is Intel compatible...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-03-26 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 8:06 [Bug 206901] New: Valve Index HMD breaks the USB controller it's connected into bugzilla-daemon
2020-03-26 3:05 ` [Bug 206901] " bugzilla-daemon
2020-03-26 3:26 ` bugzilla-daemon [this message]
2020-03-26 3:30 ` bugzilla-daemon
2020-03-26 3:42 ` bugzilla-daemon
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=bug-206901-208809-YbMVc4CgQY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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).