From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214259] Discrete Thunderbold Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional
Date: Mon, 07 Nov 2022 16:15:28 +0000 [thread overview]
Message-ID: <bug-214259-208809-vbpcoUihac@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214259-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214259
Bjorn Helgaas (bjorn@helgaas.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |---
--- Comment #37 from Bjorn Helgaas (bjorn@helgaas.com) ---
Regarding the delay, i.e., this from Konrad's attachment at comment 27:
[ 6.837625] DMAR: DRHD: handling fault status reg 2
[ 6.837629] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 26.937996] DMAR: DRHD: handling fault status reg 2
[ 26.944592] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 47.417982] DMAR: DRHD: handling fault status reg 2
[ 47.424711] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 67.897999] DMAR: DRHD: handling fault status reg 2
[ 67.904639] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 88.372827] thunderbolt 0000:07:00.0: failed to send driver ready to ICM
[ 88.380241] thunderbolt: probe of 0000:07:00.0 failed with error -110
This all involves the same device (07:00.0) and it's all likely related, so I
think we should reserve *this* bug report for this DMAR/timeout issue.
As far as I can tell, this is unrelated to bug 206459 and the E820 issues
addressed by Hans de Goede's patches, so I'm going to reopen this bug report.
If we're lucky, maybe the DMAR/timeout stuff has been fixed by something
between v5.15 and v6.0.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-11-07 16:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 13:44 [Bug 214259] New: Discrete Thunderbold Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional bugzilla-daemon
2021-09-01 13:45 ` [Bug 214259] " 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 [this message]
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-vbpcoUihac@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).