All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 25 Nov 2023 22:15:18 +0000	[thread overview]
Message-ID: <bug-215740-208809-RJpeuh8D0E@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 #305444|0                           |1
        is obsolete|                            |
 Attachment #305456|0                           |1
        is obsolete|                            |

--- Comment #34 from Alan Stern (stern@rowland.harvard.edu) ---
Created attachment 305473
  --> https://bugzilla.kernel.org/attachment.cgi?id=305473&action=edit
Revised (again) diagnostics

I revised the test patch slightly.  Now the addresses are printed in hex, as
they should have been all along.  Also, there's a line to print out the
physical addresses pointed to by hub->buffer and hub->status when a new hub is
configured.  Here's the log for plugging in a hub, then plugging a mouse into
the hub:

[   32.757399] usb 1-1: new high-speed USB device number 5 using xhci_hcd
[   32.886200] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608,
bcdDevice= 9.01
[   32.886444] usb 1-1: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[   32.886631] usb 1-1: Product: USB2.0 Hub
[   32.889566] hub 1-1:1.0: USB hub found
[   32.889813] usb 1-1: hub buffer at 100e71818, status at 100e71610
[   32.890499] hub 1-1:1.0: 4 ports detected
[   42.761267] usb 1-1.3: new low-speed USB device number 6 using xhci_hcd
[   42.833935] kauditd_printk_skb: 101 callbacks suppressed
[   42.844775] usb 1-1.3: New USB device found, idVendor=093a, idProduct=2510,
bcdDevice= 1.00
[   42.844841] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[   42.844890] usb 1-1.3: Product: USB OPTICAL MOUSE
[   42.844933] usb 1-1.3: Manufacturer: PIXART
[   42.851150] input: PIXART USB OPTICAL MOUSE as
/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:093A:2510.0009/input/input10
[   42.851585] hid-generic 0003:093A:2510.0009: input,hidraw8: USB HID v1.11
Mouse [PIXART USB OPTICAL MOUSE] on usb-0000:00:14.0-1.3/input0

The cache line size on this computer is 64 bytes, same as yours.  As you can
see, hub->buffer and hub->status were allocated in different cache lines, so
the DMA debugging routine did not detect an overlap.  That's why I didn't get
any error messages.

-- 
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:[~2023-11-25 22:15 UTC|newest]

Thread overview: 57+ 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-04-11 10:21   ` [Bug 215740] New: kernel warning: DMA-API: xhci_hcd: cacheline tracking EEXIST, overlapping mappings aren't supported #forregzbot Thorsten Leemhuis
2022-03-31  7:41 ` [Bug 215740] kernel warning: DMA-API: xhci_hcd: cacheline tracking EEXIST, overlapping mappings aren't supported 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
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 [this message]
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
2024-09-24 16:50 ` bugzilla-daemon
2024-09-24 16:56 ` bugzilla-daemon
2025-06-03  4:08 ` bugzilla-daemon
2025-06-03 14:28 ` bugzilla-daemon
2025-06-03 18:31 ` bugzilla-daemon
2025-06-03 19:09 ` bugzilla-daemon
2026-01-22  4:53 ` bugzilla-daemon
2026-01-22  7:27 ` bugzilla-daemon
2026-01-22 19:38 ` bugzilla-daemon
2026-03-17 14:52 ` bugzilla-daemon
2026-03-17 16:18 ` bugzilla-daemon
2026-03-17 17:51 ` bugzilla-daemon
2026-03-26 19:46 ` bugzilla-daemon
2026-03-27  0:04 ` bugzilla-daemon
2026-03-27  7:32 ` 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-RJpeuh8D0E@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.