From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221633] thunderbolt: hard system freeze from repeated DP tunnel activation failures (LG UltraFine 5K dual-tile + active TB3 cable, Meteor Lake-P)
Date: Wed, 10 Jun 2026 08:56:56 +0000 [thread overview]
Message-ID: <bug-221633-208809-ut9CkOKJ89@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221633-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221633
--- Comment #1 from Allan Petersen (allan.petersen@vocast.com) ---
Created attachment 310289
--> https://bugzilla.kernel.org/attachment.cgi?id=310289&action=edit
Full kernel log, freeze boot #2 (mainline 6.19.14, incl. tb_path_activate
WARNs)
--
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:[~2026-06-10 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:56 [Bug 221633] New: thunderbolt: hard system freeze from repeated DP tunnel activation failures (LG UltraFine 5K dual-tile + active TB3 cable, Meteor Lake-P) bugzilla-daemon
2026-06-10 8:56 ` bugzilla-daemon [this message]
2026-06-10 10:33 ` [Bug 221633] " bugzilla-daemon
2026-06-10 10:34 ` bugzilla-daemon
2026-06-10 10:34 ` bugzilla-daemon
2026-06-10 11:07 ` 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-221633-208809-ut9CkOKJ89@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