linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214259] New: Discrete Thunderbold Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional
Date: Wed, 01 Sep 2021 13:44:11 +0000	[thread overview]
Message-ID: <bug-214259-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=214259

            Bug ID: 214259
           Summary: Discrete Thunderbold Controller 8086:1137 throws DMAR
                    and XHCI errors and is only partially functional
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.13.12 and 5.14-rc7
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: wse@tuxedocomputers.com
        Regression: No

Affected devices: Clevo X170KM Barebone (I have one here) and according to this
reddit thread that describes the exact same problem a Thunderbold PCIe
exapansion card:
https://www.reddit.com/r/Thunderbolt/comments/ohjakr/asus_thunderboltex_4_linux_compatability/

The Clevo does not use the build in thunderbold controler of the CPU but a
discrete Thunderbold controler, which seems to be the exact same one from that
expansion card with the pci id of 8086:1137.

High level problem desciption: I have Thunderbold dock with DP-out, USB ports
and an Ethernet port. When I plug it in, only the DP port works. When its
plugged in before boot, ethernet also works. The USB ports on the Dock never
work.

dmesg is showing several erros regarding DMAR and xhci, since the DMAR errors
are shwing up first is suspect them to be the root cause making the rest
afterwards fails also.

The error is slightly different between 5.13 and 5.14

5.14-rc7:
[    3.148557] DMAR: DRHD: handling fault status reg 2
[    3.148561] DMAR: [DMA Write NO_PASID] Request device [0x04:0x00.0] fault
addr 0x69974000 [fault reason 0x05] PTE Write access is not set

5.13.12:
[    3.737783] DMAR: DRHD: handling fault status reg 2
[    3.737790] DMAR: [DMA Write] Request device [04:00.0] PASID ffffffff fault
addr 69974000 [fault reason 05] PTE Write access is not set

04.00.0 is the thunderbold controller:
04:00.0 USB controller [0c03]: Intel Corporation Thunderbolt 4 NHI [Maple Ridge
4C 2020] [8086:1137] (prog-if 40 [USB4 Host Interface])

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-09-01 13:44 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 13:44 bugzilla-daemon [this message]
2021-09-01 13:45 ` [Bug 214259] Discrete Thunderbold Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional bugzilla-daemon
2021-09-01 13:45 ` bugzilla-daemon
2021-09-01 13:46 ` bugzilla-daemon
2021-09-01 13:47 ` bugzilla-daemon
2021-09-01 13:48 ` bugzilla-daemon
2021-09-01 13:48 ` bugzilla-daemon
2021-09-01 13:50 ` bugzilla-daemon
2021-09-01 13:52 ` bugzilla-daemon
2021-09-01 13:52 ` bugzilla-daemon
2021-09-01 13:52 ` bugzilla-daemon
2021-09-01 13:53 ` bugzilla-daemon
2021-09-01 13:53 ` bugzilla-daemon
2021-09-01 13:53 ` bugzilla-daemon
2021-09-01 17:40 ` bugzilla-daemon
2021-09-28 16:24 ` bugzilla-daemon
2021-10-08  8:32 ` bugzilla-daemon
2021-10-08  8:33 ` bugzilla-daemon
2022-05-19 18:32 ` bugzilla-daemon
2022-05-23 13:25 ` bugzilla-daemon
2022-05-23 16:33 ` bugzilla-daemon
2022-07-07 21:13 ` bugzilla-daemon
2022-07-07 21:16 ` bugzilla-daemon
2022-07-28 16:32 ` bugzilla-daemon
2022-07-28 20:56 ` bugzilla-daemon
2022-11-03 15:45 ` bugzilla-daemon
2022-11-03 17:19 ` bugzilla-daemon
2022-11-04 10:16 ` bugzilla-daemon
2022-11-04 10:21 ` bugzilla-daemon
2022-11-04 10:42 ` bugzilla-daemon
2022-11-04 10:44 ` bugzilla-daemon
2022-11-04 21:13 ` bugzilla-daemon
2022-11-05 18:28 ` bugzilla-daemon
2022-11-07 13:15 ` bugzilla-daemon
2022-11-07 13:16 ` bugzilla-daemon
2022-11-07 14:08 ` bugzilla-daemon
2022-11-07 14:31 ` bugzilla-daemon
2022-11-07 16:15 ` bugzilla-daemon
2022-11-07 16:34 ` bugzilla-daemon
2022-11-07 16:52 ` bugzilla-daemon
2022-11-07 16:55 ` bugzilla-daemon
2022-11-07 17:40 ` bugzilla-daemon
2022-11-07 17:44 ` bugzilla-daemon
2022-11-07 17:45 ` bugzilla-daemon
2022-11-07 17:47 ` 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-214259-208809@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).