From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215740] kernel warning: DMA-API: xhci_hcd: cacheline tracking EEXIST, overlapping mappings aren't supported
Date: Mon, 20 Nov 2023 19:43:37 +0000 [thread overview]
Message-ID: <bug-215740-208809-s8V03UzTKb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215740-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215740
Alan Stern (stern@rowland.harvard.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #305425|0 |1
is obsolete| |
--- Comment #17 from Alan Stern (stern@rowland.harvard.edu) ---
Created attachment 305444
--> https://bugzilla.kernel.org/attachment.cgi?id=305444&action=edit
Revised diagnostics
The ftrace doesn't help. You can't tell where the error occurs or which hub
the function calls are for.
The patch wasn't quite right, so here is an updated version. Be sure to
include the "cacheline tracking EEXIST, overlapping mappings aren't supported"
line when you post the dmesg output.
--
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:[~2023-11-20 19:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 15:18 [Bug 215740] New: kernel warning: DMA-API: xhci_hcd: cacheline tracking EEXIST, overlapping mappings aren't supported bugzilla-daemon
2022-03-31 6:52 ` [Bug 215740] " bugzilla-daemon
2022-03-31 6:54 ` bugzilla-daemon
2022-03-31 7:41 ` [Bug 215740] New: " Thorsten Leemhuis
2022-04-05 5:19 ` Christoph Hellwig
2022-03-31 7:41 ` [Bug 215740] " bugzilla-daemon
2022-03-31 7:54 ` bugzilla-daemon
2022-04-05 5:19 ` bugzilla-daemon
2022-05-04 8:10 ` bugzilla-daemon
2022-05-04 10:17 ` bugzilla-daemon
2023-10-10 20:19 ` bugzilla-daemon
2023-11-12 20:46 ` bugzilla-daemon
2023-11-13 22:11 ` bugzilla-daemon
2023-11-14 3:25 ` bugzilla-daemon
2023-11-15 20:24 ` bugzilla-daemon
2023-11-16 2:19 ` bugzilla-daemon
2023-11-17 22:13 ` bugzilla-daemon
2023-11-19 16:47 ` bugzilla-daemon
2023-11-19 21:12 ` bugzilla-daemon
2023-11-20 19:43 ` bugzilla-daemon [this message]
2023-11-21 19:31 ` bugzilla-daemon
2023-11-21 20:51 ` bugzilla-daemon
2023-11-23 21:27 ` bugzilla-daemon
2023-11-24 12:02 ` bugzilla-daemon
2023-11-24 12:07 ` bugzilla-daemon
2023-11-24 15:27 ` bugzilla-daemon
2023-11-24 15:30 ` bugzilla-daemon
2023-11-24 15:40 ` bugzilla-daemon
2023-11-24 15:50 ` bugzilla-daemon
2023-11-24 16:09 ` bugzilla-daemon
2023-11-24 16:21 ` bugzilla-daemon
2023-11-24 21:05 ` bugzilla-daemon
2023-11-24 22:22 ` bugzilla-daemon
2023-11-25 2:03 ` bugzilla-daemon
2023-11-25 20:50 ` bugzilla-daemon
2023-11-25 21:17 ` bugzilla-daemon
2023-11-25 22:15 ` bugzilla-daemon
2023-11-28 19:04 ` bugzilla-daemon
2023-11-28 21:28 ` bugzilla-daemon
2023-11-29 15:44 ` bugzilla-daemon
2023-11-30 19:35 ` 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-215740-208809-s8V03UzTKb@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).