Date: Thu, 06 Feb 2020 12:21:09 +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-adrpeC9TT6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237666-19105@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #101 from Gerard Seibert <gerard_seibert@outlook.com> --- Apparently, this problem has existed since at least April 2019. That seems, at least to me, to be an awfully long time, at least at this level, for a bug to go unsquashed. I am preparing to purchase another PC similar to the one I now have to replace an older unit. It is apparent that FreeBSD 12.x will not operate on it correctly. I am starting to wonder if FreeBSD is the best platform for my use. If it is unable to run modern hardware, then perhaps it is time for me to investigate other operating systems. I would hate to start over with a new OS, but I don't seem to be left with too many other options. While 12.2 is still a long way off, 11.4 is due this summer. I am not even sure if that will work on my PC or simple make the system unbootable. I guess my quest is if there is anyone actively working on this bug and what the prognosis is for this problem. I don't mean to sound crass, but this problem has gone on, in my opinion, far too long. With newer systems coming on the market daily, I honestly believe that this problem will manifest into a much larger problem and potential embarrassment for FreeBSD. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237666-19105-adrpeC9TT6>
