From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216497] USB connections through thunderbolt dock broken
Date: Mon, 19 Sep 2022 14:15:54 +0000 [thread overview]
Message-ID: <bug-216497-208809-e1azE5sRyA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216497-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216497
Jason M. (jason@montleon.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason@montleon.com
--- Comment #6 from Jason M. (jason@montleon.com) ---
I am seeing similar except my wireless is broken because the firmware can't
load.
https://bugzilla.redhat.com/show_bug.cgi?id=2127753
Among the errors from my dmesg attached over there:
Sep 18 14:28:02 kernel: DMAR: DRHD: handling fault status reg 2
Sep 18 14:28:02 kernel: DMAR: [INTR-REMAP] Request device [01:00.0] fault index
0x8080 [fault reason 0x25] Blocked a compatibility format interrupt request
After running through a bisect reverting just
9516acba29e322202674d18f4dc383879f7813a5 fixes it.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.19.y&id=9516acba29e322202674d18f4dc383879f7813a5
--
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-09-19 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 0:24 [Bug 216497] New: USB connections through thunderbolt dock broken bugzilla-daemon
2022-09-17 17:12 ` [Bug 216497] " bugzilla-daemon
2022-09-17 22:41 ` bugzilla-daemon
2022-09-19 5:32 ` bugzilla-daemon
2022-09-19 7:42 ` bugzilla-daemon
2022-09-19 8:11 ` bugzilla-daemon
2022-09-19 14:15 ` bugzilla-daemon [this message]
2022-09-20 1:04 ` bugzilla-daemon
2022-09-20 9:22 ` bugzilla-daemon
2022-09-20 9:29 ` bugzilla-daemon
2022-09-20 11:40 ` bugzilla-daemon
2022-09-26 1:24 ` bugzilla-daemon
2022-09-26 5:21 ` bugzilla-daemon
2022-09-26 11:10 ` bugzilla-daemon
2022-10-07 13:54 ` 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-216497-208809-e1azE5sRyA@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).