From owner-freebsd-stable@freebsd.org Mon Mar 19 20:00:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 924D9F6859A for ; Mon, 19 Mar 2018 20:00:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45F1E821E2; Mon, 19 Mar 2018 20:00:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id F13AB1AE2B; Mon, 19 Mar 2018 20:00:54 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Mon, 19 Mar 2018 20:00:53 +0000 From: Glen Barber To: John Baldwin Cc: freebsd-stable@freebsd.org, Mark Saad , wishmaster Subject: Re: Problem with USB <---> UPS management connection Message-ID: <20180319200053.GE14326@FreeBSD.org> References: <1520423283.816382083.msco108y@frv52.fwdcdn.com> <548D61D9-2A86-48E4-B077-285298CB64CE@longcount.org> <20180308011646.GC7399@FreeBSD.org> <1744138.yp8bGWUsoN@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sfyO1m2EN8ZOtJL6" Content-Disposition: inline In-Reply-To: <1744138.yp8bGWUsoN@ralph.baldwin.cx> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 20:00:55 -0000 --sfyO1m2EN8ZOtJL6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 19, 2018 at 12:53:01PM -0700, John Baldwin wrote: > On Thursday, March 08, 2018 01:16:46 AM Glen Barber wrote: > > On Wed, Mar 07, 2018 at 08:04:47PM -0500, Mark Saad wrote: > > > > On Mar 7, 2018, at 6:55 AM, wishmaster wrote: > > > >=20 > > > > Hi, colleagues! > > > >=20 > > > > Something strange happens with a server. I am attempting to connect= management interface of UPS with server via USB. > > > > In console I see a lot of errors: > > > >=20 > > > > Mar 7 13:42:04 xxx kernel: ugen2.2: at usbus2 > > > > Mar 7 13:42:05 xxx kernel: uhid0 on uhub6 > > > > Mar 7 13:42:05 xxx kernel: uhid0: on usbus2 > > > > Mar 7 13:42:08 xxx kernel: ugen2.2: at usbus2 (disconnected) > > > > Mar 7 13:42:08 xxx kernel: uhid0: at uhub6, port 3, addr 2 (discon= nected) > > > > Mar 7 13:42:08 xxx kernel: uhid0: detached > > > > Mar 7 13:42:12 xxx kernel: ugen2.2: at usbus2 > > > > Mar 7 13:42:12 xxx kernel: uhid0 on uhub6 > > > > Mar 7 13:42:12 xxx kernel: uhid0: on usbus2 > > > > Mar 7 13:42:16 xxx kernel: ugen2.2: at usbus2 (disconnected) > > > > Mar 7 13:42:16 xxx kernel: uhid0: at uhub6, port 3, addr 2 (discon= nected) > > > > Mar 7 13:42:16 xxx kernel: uhid0: detached > > > >=20 > > > > I have changed USB-cables, USB port on the server - without success. > > > > On another server this problem is absent. > > > >=20 > > > > FreeBSD version: FreeBSD 11.1-STABLE #1 r329364M: > > > >=20 > > > > Any ideas? > > > >=20 > > > All > > > I lost power at home and noticed that nut didn=E2=80=99t work right = =2E I > > > had a similar dmesg . My box is running 11.1-stable amd64 built > > > from svn 7-8 days ago . When I get power back I=E2=80=99ll post detai= ls . > > >=20 > >=20 > > This seems suspiciously similar to an issue I am seeing with a USB mouse > > on both stable/11 a patched build of releng/11.1. In my case, the dmesg > > shows: > >=20 > > ugen1.3: at usbus1 (disconnected) > > ugen1.3: at usbus1 > > ugen1.3: at usbus1 (disconnected) > > ugen1.3: at usbus1 > >=20 > > What struck me as "suspiciously similar" is the 'ugen' reference. > > Unfortunately, I do not have more information yet, but have been > > pounding my head on my desk throughout the day. Then, I saw this > > thread. > >=20 > > Anyone else seeing at least USB mouse-related issues? It could entirely > > be a red herring. >=20 > I am definitely seeing issues with an APC USB I have on my desktop. I ha= ve > used this desktop + APC combination for at least 5 years now and only aft= er > my most recent upgrade to 11.1-STABLE at r326909. I did not have issues = on > the previous 11.1-STABLE kernel at r321399, so it does seem like it could > be a regression. >=20 I did figure out what the problem was with my mouse - the ums(4) driver was not properly loading on releng/11.1. It does appear to be fixed in stable/11, so the issue I pointed out in this thread may not be related. Glen --sfyO1m2EN8ZOtJL6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlqwFvUACgkQAxRYpUeP 4pOzIA/8DGiEUURBGsdEpyBZmonOpGqn1fZBVgw/km4X5tHRF2p12m5IxsyOT0ts JUKTsg7TfydIfqLenZIRlIMV6e2zFlAXzeBkIBcCNZIgRc53e502G6uLGDgLA9aK f58pK8p37HGCg3c/U4x8bVC/LtU7wYw8ef5GIa8t4wrd6ygyii5KVYrpPsTotuq9 WPlJ4uc3s+hUvYSbgtmtLQU2QQ3NB4dRdukUepfCx+3DJQvyWe8uFF8cNqmKf6PD MHGHOUP1wSnBkQhO1UlVOxXOSEEFNy4BDJj+1eZrvFwpXl3MEAoq1pojaTQFb5z4 GAxo/n3tNQPPpYi7KR4UcIiEEvMOgc6u1BvlOUn/r8c8dym+Ea3FxW/D4RKZ2QCC 3rn6FIQ3rjkUYmRg5Dpf16IBnfodqXlPjCmaQhBAijca3GvKJbKlhAmmbwSzK8Od AGTGyb2XikkPQ5l1NUPhYsc9f4I+GO106Kidd8JAIWcH1FBPOR8XpTztE8f7MORu QF0RbNyeblEfqJrc3w2wozANEVamRf92dlEL2KqERpwNWWtncFLPRbw92oWhlx88 rq9C/TrCUqXowHRl4gLBs7+9kpoZm3lTtYnRbBd81zwLKUdkSL9dTzdrHgYPZv/t sBlfUOShlc7RJBpqoC7I5D7TU6R94Lz/JuXGueWDgfoFzx5Vmsg= =+U0B -----END PGP SIGNATURE----- --sfyO1m2EN8ZOtJL6--