Date: Sun, 11 Aug 2019 15:37:14 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Message-ID: <bug-237666-19105-LPEmNGnJB9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237666-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-237666-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666 --- Comment #39 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Hans Petter Selasky from comment #36) These 'failed to allocate' messages are the secondary effects of reading all ones. Values of the bridge' registers to specify io and memory window to forward to subordinary buses are all ones (AKA 0xfff...), and that range conflicts with already allocated resources. So the question is how it comes that bridges were enumerated, but accessing their PCI config space reads failing. I am curious if manually reading e.g. pci vendor or device id using pciconf would show sane values or 1111...s. --=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-237666-19105-LPEmNGnJB9>