[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Aug 10 17:46:22 UTC 2019


--- Comment #30 from Hans Petter Selasky <hselasky at FreeBSD.org> ---
Hi Konstatin,

We are seeing a 32-bit PCI read resulting in -1U. This is a regression issue in
more recent versions of FreeBSD. Can you comment on these failure messages:


> Hmm, I see that there are two xhci controllers.  One is on pci7, and I see this:
> pcib7: <PCI-PCI bridge> at device 2.0 numa-domain 0 on pci4
> pcib7: failed to allocate initial I/O port window: 0-0xfff
> pcib7: failed to allocate initial memory window: 0-0xfffff
> pcib7: failed to allocate initial prefetch window: 0-0xfffff
> pci7: <PCI bus> numa-domain 0 on pcib7
> xhci0: <XHCI (generic) USB 3.0 controller> mem 0xd8000000-0xd800ffff at device 0
> .0 numa-domain 0 on pci7
> xhci0: 32 bytes context size, 64-bit DMA
> usbus0 numa-domain 0 on xhci0
> and
> pcib1: <ACPI Host-PCI bridge> port 0xcf8-0xcff numa-domain 0 on acpi0
> pci1: <ACPI PCI bus> numa-domain 0 on pcib1
> ...
> pci1: <unknown> at device 17.0 (no driver attached)
> xhci1: <Intel Wellsburg USB 3.0 controller> mem 0xf6120000-0xf612ffff irq 19 at device 20.0 numa-domain 0 on pci1
> xhci1: 32 bytes context size, 64-bit DMA
> usbus1 numa-domain 0 on xhci1
> pci1: <simple comms> at device 22.0 (no driver attached)
> I'm also not using any USB3 device regularly, so I don't know if the misbehaving controller is functioning at all.
> The messages above are similar with 11.3.

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-usb mailing list