https://bugzilla.kernel.org/show_bug.cgi?id=215740 Bug ID: 215740 Summary: kernel warning: DMA-API: xhci_hcd: cacheline tracking EEXIST, overlapping mappings aren't supported Product: Drivers Version: 2.5 Kernel Version: 5.17 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: USB Assignee: drivers_usb@xxxxxxxxxxxxxxxxxxxxxx Reporter: travneff@xxxxxxxxx Regression: No Created attachment 300612 --> https://bugzilla.kernel.org/attachment.cgi?id=300612&action=edit full dmesg log with the warning I have this kernel trace often while PC booting: DMA-API: xhci_hcd 0000:09:00.3: cacheline tracking EEXIST, overlapping mappings aren't supported WARNING: CPU: 4 PID: 69 at kernel/dma/debug.c:570 add_dma_entry+0x1c7/0x250 Modules linked in: bpf_preload CPU: 4 PID: 69 Comm: kworker/4:1 Not tainted 5.17.0 #1 Hardware name: ASUS System Product Name/TUF GAMING B550M-PLUS, BIOS 2423 08/10/2021 Workqueue: usb_hub_wq hub_event RIP: 0010:add_dma_entry+0x1c7/0x250 Code: ff 0f 84 97 00 00 00 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 4b 53 80 00 48 89 c6 48 89 da 48 c7 c7 58 b3 84 94 e8 27 21 ca 00 <0f> 0b 48 85 ed 0f 85 69 d2 ca 00 8b 05 88 a0 30 02 85 c0 0f 85 f4 RSP: 0018:ffff9cadc0c9ba88 EFLAGS: 00010292 RAX: 0000000000000060 RBX: ffff9173d2c49ea0 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00000000ffffffff RBP: ffff9173d11a5e80 R08: 0000000000000000 R09: ffff9cadc0c9b8c0 R10: ffff9cadc0c9b8b8 R11: ffffffff95165128 R12: 0000000000000000 R13: 0000000000000001 R14: 0000000000000206 R15: 00000000046882ee FS: 0000000000000000(0000) GS:ffff9182a8200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fce5d52a130 CR3: 0000000119b28000 CR4: 0000000000350ee0 Call Trace: <TASK> dma_map_page_attrs+0x82/0x250 ? _raw_spin_unlock_irqrestore+0x30/0x60 usb_hcd_map_urb_for_dma+0x3eb/0x4f0 usb_hcd_submit_urb+0x9b/0xb90 ? lockdep_init_map_type+0x62/0x260 usb_start_wait_urb+0x55/0x130 usb_control_msg+0xc9/0x110 hub_ext_port_status+0x89/0x110 hub_event+0x1e4/0x1920 ? lock_acquire+0xe0/0x2d0 ? lock_is_held_type+0xea/0x140 process_one_work+0x29b/0x5f0 worker_thread+0x4f/0x390 ? process_one_work+0x5f0/0x5f0 kthread+0xf5/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> My usb devices: $ lsusb -t /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=uas, 5000M |__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 2: Dev 2, If 3, Class=Application Specific Interface, Driver=, 12M |__ Port 2: Dev 2, If 1, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 2: Dev 2, If 2, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 2: Dev 2, If 0, Class=Vendor Specific Class, Driver=btusb, 12M |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 12, If 0, Class=Communications, Driver=cdc_ether, 480M |__ Port 1: Dev 12, If 1, Class=CDC Data, Driver=cdc_ether, 480M |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 3: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 8, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=, 480M |__ Port 4: Dev 10, If 0, Class=Imaging, Driver=, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 6: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 7: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M $ lsusb Bus 004 Device 006: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 005: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 004: ID 0578:0578 Intrinsix Corp. KingSpec Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 010: ID 1004:633e LG Electronics, Inc. LM-X420xxx/G2/G3 Android Phone (MTP/download mode) Bus 003 Device 009: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter Bus 003 Device 008: ID 0463:ffff MGE UPS Systems UPS Bus 003 Device 007: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 006: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 003 Device 005: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 012: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB Ethernet/RNDIS Gadget Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 0b05:1939 ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Kernel is built from https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git at v5.17 tag (f443e374ae131c168a065ea1748feac6b2e76613) Also reproduces for my distro kernel: https://bugzilla.redhat.com/show_bug.cgi?id=2021242 -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
