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: Thu, 07 Jul 2022 21:16:50 +0000 [thread overview]
Message-ID: <bug-214259-208809-uEdU4RZ0De@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214259-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214259
--- Comment #22 from Konrad J Hambrick (kjhambrick@gmail.com) ---
(In reply to Konrad J Hambrick from comment #21)
> Hans --
>
> I have exactly the same Hardware and when I Enable my Discrete ThunderBolt
> in the BIOS, I experience a series of TimeOut delays during Boot.
>
> I am running 5.15.53 on Slackware64 15.0 ...
>
> I don't have a Dock for my LapTop so I am not sure this bug is a duplicate
> of https://bugzilla.kernel.org/show_bug.cgi?id=206459
>
> Q1: Is your Patch Series still viable ?
>
> If so, your second link above for the patch series no longer works:
> https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/
> resource
>
> Q2: Was this patch ever included in the kernel source tree ?
>
> If so, what version should I try ?
>
> Thanks !
>
> -- kjh
p.s. this is my dmesg with the Discrete Thunderbolt Enabled:
[ 9.359600] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio2/input/input15
[ 27.953327] DMAR: DRHD: handling fault status reg 2
[ 27.959653] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 48.433330] DMAR: DRHD: handling fault status reg 2
[ 48.438777] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 68.913306] DMAR: DRHD: handling fault status reg 2
[ 68.919850] DMAR: [DMA Write NO_PASID] Request device [07:00.0] fault addr
0x69935000 [fault reason 0x05] PTE Write access is not set
[ 89.387726] thunderbolt 0000:07:00.0: failed to send driver ready to ICM
[ 89.394835] thunderbolt: probe of 0000:07:00.0 failed with error -110
--
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-07-07 21:16 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 [this message]
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-uEdU4RZ0De@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.