All of lore.kernel.org
 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: Mon, 23 Dec 2024 09:57:07 +0000	[thread overview]
Message-ID: <bug-215906-208809-FWFfaEOHJv@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 #21 from Rolf Reintjes (lists.rolf@reintjes.nrw) ---
(In reply to Michał Pecio from comment #20)
> By a complete accident I found that VL805 has a known bug where it
> overfetches transfer rings:
> https://github.com/raspberrypi/linux/issues/4685
> 
> Rolf, there is a workaround for similar bug in Zhaoxin hardware which may
> solve your IOMMU faults.
> 
> Update to at least v6.6, or the latest v6.12 series if it's not a problem.
> 
> Run the following (if using a USB keyboard put it all in a script):
> rmmod xhci_pci
> rmmod xhci_hcd
> modprobe xhci_hcd quirks=0x200000000000
> modprobe xhci_pci
> 
> Verify that it worked:
> dmesg |grep quirks
> [122123.422469] xhci_hcd 0000:08:00.0: hcc params 0x002841eb hci version
> 0x100 quirks 0x0000200000000890
>                                                                             
> ^-- here
> And see if it helps.

Thank you very much.

I just tried it and it works. The USB port runs fine.

But what is actually done here?
modprobe xhci_hcd quirks=0x200000000000
A setting is given to the driver when starting, but what does this setting
mean?

-- 
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-12-23  9:57 UTC|newest]

Thread overview: 32+ 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 ` [Bug 215906] " bugzilla-daemon
2022-05-05  9:40 ` 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 [this message]
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
2026-03-18  7:52 ` 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-FWFfaEOHJv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.