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 215906] DMAR fault when connected usb hub (xhci_hcd)
Date: Sun, 01 May 2022 12:32:00 +0000	[thread overview]
Message-ID: <bug-215906-208809-RZ4nUNh8DM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215906-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215906

--- Comment #1 from Royston Shufflebotham (royston@shufflebotham.org) ---
I just hit exactly the same issue when upgrading the kernel from v5.13.0-40 to
v5.15.0-27. With no devices plugged in, the USB hub reports everything as ok.
Plugging in a USB keyboard worked for a minute or two, and then I get exactly
the same errors from [+0,229229] to [+0,000004] above.

Same USB controller chipset as OP by the looks of things. I've managed to list
the Capabilities in case that's any help:
03:00.0 USB controller: VIA Technologies, Inc. VL805/806 xHCI USB 3.0
Controller (rev 01) (prog-if 30 [XHCI])
        Subsystem: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller
        Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 12
        Memory at e0a00000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [80] Power Management version 3
        Capabilities: [90] MSI: Enable+ Count=1/4 Maskable- 64bit+
        Capabilities: [c4] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

Downgrading back to v5.13.0-40 fixes the problem.

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

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

  reply	other threads:[~2022-05-01 12:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 20:21 [Bug 215906] New: DMAR fault when connected usb hub (xhci_hcd) bugzilla-daemon
2022-05-01 12:32 ` bugzilla-daemon [this message]
2022-05-05  9:40 ` [Bug 215906] " bugzilla-daemon
2022-05-05 12:30 ` bugzilla-daemon
2022-05-06 15:49 ` bugzilla-daemon
2022-05-09  5:42 ` bugzilla-daemon
2022-05-09  8:11 ` bugzilla-daemon
2022-05-09  9:00 ` bugzilla-daemon
2022-06-20  8:40 ` bugzilla-daemon
2023-10-22 19:19 ` bugzilla-daemon
2023-10-25  9:23 ` bugzilla-daemon
2023-10-29 22:39 ` bugzilla-daemon
2023-10-30 16:21 ` bugzilla-daemon
2023-10-30 16:26 ` bugzilla-daemon
2023-10-30 17:18 ` bugzilla-daemon
2023-10-31  9:10 ` bugzilla-daemon
2023-10-31 15:40 ` bugzilla-daemon
2023-11-02 10:59 ` bugzilla-daemon
2023-11-04  8:06 ` bugzilla-daemon
2024-11-01 14:03 ` bugzilla-daemon
2024-12-22 20:49 ` bugzilla-daemon
2024-12-23  9:57 ` bugzilla-daemon
2024-12-23 10:31 ` bugzilla-daemon
2024-12-23 11:02 ` bugzilla-daemon
2024-12-23 12:02 ` bugzilla-daemon
2024-12-23 12:18 ` bugzilla-daemon
2024-12-23 18:14 ` bugzilla-daemon
2024-12-23 18:29 ` bugzilla-daemon
2025-01-24 14:53 ` bugzilla-daemon
2025-03-09 23:12 ` bugzilla-daemon
2025-04-04 21:26 ` 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-215906-208809-RZ4nUNh8DM@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).