From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working
Date: Tue, 27 Aug 2024 09:56:17 +0000 [thread overview]
Message-ID: <bug-219198-208809-j0lgoskgI3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219198-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219198
--- Comment #10 from Markus Rathgeb (maggu2810@gmail.com) ---
Forget the bisect.
I currently tested the another commit.
I started the laptop without the dock attached.
In a Wayland session I opened a terminal to look at the kernel messages.
I plugged in the dock.
All loooks good.
The USB keyboard attached to the dock is working.
Before I entered "git bisect good" I had the idee to test again.
I disconnected the dock, waited a moment
I connected the dock again
Now the lines
Aug 27 11:51:07 b0v9by3 kernel: DMAR: DRHD: handling fault status reg 2
Aug 27 11:51:07 b0v9by3 kernel: DMAR: [DMA Read NO_PASID] Request device
[04:00.0] fault addr 0xffffe000 [fault reason 0x0c] non-zero reserved fields in
PTE
are part of the kernel log
additional the USB keyboard attached to the dock are not recognized again
So, we need to disconnect and reconnect the dock at least once to run into the
error.
--
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:[~2024-08-27 9:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 8:49 [Bug 219198] New: usb on Dell WD19TB Thunderbolt Dock stop working bugzilla-daemon
2024-08-26 8:50 ` [Bug 219198] " bugzilla-daemon
2024-08-26 9:12 ` bugzilla-daemon
2024-08-26 11:17 ` bugzilla-daemon
2024-08-26 18:35 ` bugzilla-daemon
2024-08-26 19:06 ` bugzilla-daemon
2024-08-26 19:07 ` bugzilla-daemon
2024-08-26 19:07 ` bugzilla-daemon
2024-08-26 20:32 ` bugzilla-daemon
2024-08-27 9:19 ` bugzilla-daemon
2024-08-27 9:56 ` bugzilla-daemon [this message]
2024-08-27 15:22 ` bugzilla-daemon
2024-08-27 15:41 ` bugzilla-daemon
2024-08-27 18:56 ` bugzilla-daemon
2024-08-27 20:20 ` bugzilla-daemon
2024-08-28 9:39 ` bugzilla-daemon
2024-08-28 10:09 ` bugzilla-daemon
2024-08-28 10:12 ` bugzilla-daemon
2024-08-28 10:46 ` bugzilla-daemon
2024-08-28 17:51 ` bugzilla-daemon
2024-08-28 17:57 ` bugzilla-daemon
2024-08-28 18:05 ` bugzilla-daemon
2024-08-28 19:11 ` bugzilla-daemon
2024-08-28 19:14 ` bugzilla-daemon
2024-08-28 19:18 ` bugzilla-daemon
2024-08-28 19:19 ` bugzilla-daemon
2024-08-29 7:06 ` bugzilla-daemon
2024-08-29 8:36 ` bugzilla-daemon
2024-09-03 23:40 ` bugzilla-daemon
2024-09-04 5:42 ` bugzilla-daemon
2024-09-04 5:44 ` 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-219198-208809-j0lgoskgI3@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).