Date: Wed, 12 Aug 2020 07:40:24 -0400 From: "Gerard E. Seibert" <gerard_seibert@outlook.com> To: freebsd-stable@freebsd.org Subject: Re: Bug 237666 - repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Message-ID: <DM6PR02MB52289254DE327BB95FB7AEA8FA420@DM6PR02MB5228.namprd02.prod.outlook.com> In-Reply-To: <20200811190911.GA72347@bastion.zyxst.net> References: <DM6PR02MB5228EF1885B2B8A39BFFD49BFA4A0@DM6PR02MB5228.namprd02.prod.outlook.com> <20200811190911.GA72347@bastion.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/6iCq01yPAh.IXkF41tRgOTI Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 11 Aug 2020 20:09:11 +0100, tech-lists stated: > On Tue, Aug 04, 2020 at 01:53:16PM -0400, Gerard E. Seibert wrote: > >I was told to resubmit this with the bug's title in the subject line. > >Therefore, I am. > > > >I am just inquiring to see if any progress had been made regarding > >bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237666 > > > >This bug affects both the 12.x and 13.x branches of FreeBSD. > >Fortunately, it does not affect <=3D 11.x branches. > > > >FreeBSD 12.2 is due out in October and version 13.0 only five months > >later. At present, this bug infects both the 12.x and 13.x branches > >making updating systems beyond 11.x impossible for users of the > >afflicted systems. The fact that this bug has gone unremedied for so > >long is somewhat disheartening. =20 >=20 > Hi, >=20 > I encountered this bug sometime last year; this year in April it was > bothersome enough to try to do something about it. I "fixed" it by > compiling and installing a new kernel with everything USB-related > removed. Fortunately the machine does not need a USB peripheral of > any sort. I've only ever run 12-stable on this machine. And it gave > the usb error messages with nothing usb attached, before installing > the new kernel. Quite frankly, that is a drastic step to take. Many people, like myself, need a USB port(s). What I find so annoying is that this bug did not exist prior to version 12.x; therefore, it is obvious that something changed. I am not a highly skilled system programmer, so my chances of discovering the problem are at best nil. However, the person or persons who wrote the code should be aware of what has changed and either revert it to it former working condition or fix it in its present state. This situation has gone on for over a year and continued through two major versions. That is just not acceptable. Perhaps, if we could collect a list of the know systems that are affected by this bug, it might help the developers to discover the source of the problem. My System: Dell XPS 8930 32 GB DDR4 @ 2400MHz 9th Gen Intel Core i3-9 100 (4 core, 6MB Cache) --=20 Gerard --Sig_/6iCq01yPAh.IXkF41tRgOTI Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEIQb/tTwl6I1ueEVtOHMGOIfexWQFAl8z1SgACgkQOHMGOIfe xWSrbAf+KSTAFMV+awQcF9Bl94+UqxTnhMi8YZyO5Vu15+OCsmqiP2QRXlVjC00F 41xNpzucKx62LU7j2VlFKkrGg15kjHn26CN7IxjOFNvXLxzPq6jUpj7M5E89WnEl xmT7wn4mgpVP2xaA911mBx1WtH2CuJpg6wOySx/vyyd5hR1ShEVBvjNFOB62BPXQ drk3AQfgk5QaZFCIMgmznx+CBdeSf586yF1CyK4KpQL75nj3djM2YwndtF02LGF7 6yGDR/oT9Wggj53RSLH1gqED4jvYMmCZzr44XrKBCn4jhONhuMkUGYrjA/h2TgXQ Iw0x2WI1QIn6b0ktI71BOSTnlHQinw== =CXyE -----END PGP SIGNATURE----- --Sig_/6iCq01yPAh.IXkF41tRgOTI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DM6PR02MB52289254DE327BB95FB7AEA8FA420>