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 11:02:04 +0000 [thread overview]
Message-ID: <bug-215906-208809-nwSj9yCboJ@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 #23 from Rolf Reintjes (lists.rolf@reintjes.nrw) ---
(In reply to Michał Pecio from comment #22)
> That's good to hear. Just to be sure, can you confirm that without this
> quirk the problem still exists today, on the same machine running the same
> kernel?
The problem still exists today.
rolf@i7-5820K-debian-testing1:~$ uname -a
Linux i7-5820K-debian-testing1 6.12.5-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.12.5-1 (2024-12-15) x86_64 GNU/Linux
> BTW, there is speculation that the Zhaoxin bug may be caused by odd page
> size requirements of some controllers. If your kernel has debugfs enabled,
> please also post the output of:
>
> grep PAGESIZE /sys/kernel/debug/usb/xhci/*/reg-op
rolf@i7-5820K-debian-testing1:~$ sudo grep PAGESIZE
/sys/kernel/debug/usb/xhci/*/reg-op
grep: /sys/kernel/debug/usb/xhci/*/reg-op: Datei oder Verzeichnis nicht
gefunden
Which is translated: File or directory not found
> lspci -nn |grep USB
rolf@i7-5820K-debian-testing1:~$ lspci -nn |grep USB
00:14.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB
xHCI Host Controller [8086:8d31] (rev 05)
00:1a.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB
Enhanced Host Controller #2 [8086:8d2d] (rev 05)
00:1d.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB
Enhanced Host Controller #1 [8086:8d26] (rev 05)
05:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805/806 xHCI USB 3.0
Controller [1106:3483] (rev 01)
06:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host
Controller [1b21:1242]
--
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-12-23 11:02 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
2024-12-23 10:31 ` bugzilla-daemon
2024-12-23 11:02 ` bugzilla-daemon [this message]
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-nwSj9yCboJ@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.