linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 15:22:25 +0000	[thread overview]
Message-ID: <bug-219198-208809-ubtz0ydLKK@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 #11 from Adam Williamson (adamw@happyassassin.net) ---
I'm not replugging mine, but as I noted, the Thunderbolt service (I forgot it's
bolt.service , not thunderbolt.service) is producing a similar effect. I do
indeed see similar messages to yours *after* bolt.service starts:

Aug 26 11:47:21 xps13a.happyassassin.net systemd[1]: Started bolt.service -
Thunderbolt system service.
...
Aug 26 11:47:22 xps13a.happyassassin.net kernel: pci 0000:55:00.0: enabling
device (0000 -> 0002)
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: new USB
bus registered, assigned bus number 5
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: hcc
params 0x200071e9 hci version 0x100 quirks 0x0000000000000010
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: new USB
bus registered, assigned bus number 6
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: Host
supports USB 3.0 SuperSpeed
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: DRHD: handling fault
status reg 2
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: [DMA Read NO_PASID]
Request device [55:00.0] fault addr 0xffffb000 [fault reason 0x06] PTE Read
access is not set
...
Aug 26 11:47:22 xps13a.happyassassin.net kernel: pci 0000:56:00.0: enabling
device (0000 -> 0002)
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: new USB
bus registered, assigned bus number 7
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: hcc
params 0x200071e9 hci version 0x100 quirks 0x0000000000000010
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: new USB
bus registered, assigned bus number 8
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Host
supports USB 3.0 SuperSpeed
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: DRHD: handling fault
status reg 2
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: [DMA Read NO_PASID]
Request device [56:00.0] fault addr 0xffffb000 [fault reason 0x0c] non-zero
reserved fields in PTE
...
Aug 26 11:47:22 xps13a.happyassassin.net kernel: pci 0000:57:00.0: enabling
device (0000 -> 0002)
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: new USB
bus registered, assigned bus number 9
Aug 26 11:47:22 xps13a.happyassassin.net audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'
[snip unrelated messages]
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: DRHD: handling fault
status reg 2
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: [DMA Read NO_PASID]
Request device [57:00.0] fault addr 0xffffb000 [fault reason 0x06] PTE Read
access is not set

And indeed there are no similar messages in my 6.10.6 log.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-08-27 15:22 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
2024-08-27 15:22 ` bugzilla-daemon [this message]
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-ubtz0ydLKK@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).