Date: Mon, 15 Jan 2024 20:08:11 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 276354] ubt0 triggering 1000 xhci0 interrupts per second Message-ID: <bug-276354-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276354 Bug ID: 276354 Summary: ubt0 triggering 1000 xhci0 interrupts per second Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: trasz@FreeBSD.org My ubt0 isn't working, but despite this it makes xhci0 generate 1000 interr= upts per second (according to "vmstat -i"), until I do "service bluetooth start ubt0". That errors out, but makes the interrupts go away. It needs to be = done again after a suspend/resume cycle. Relevant bits of dmesg: xhci0: <Intel Sunrise Point-LP USB 3.0 controller> mem 0xef230000-0xef23ffff irq 16 at device 20.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA usbus0: waiting for BIOS to give up control xhci_interrupt: host controller halted usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ubt0: <vendor 0x8087 product 0x0a2b, class 224/1, rev 2.00/0.10, addr 1> on usbus0 When "service bluetooth start ubt0" fails, dmesg says: ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=3D0x3, OCF=3D0x3. Timeout But this isn't really the problem I'm reporting here. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276354-227>