From owner-freebsd-current@freebsd.org Sat Jul 6 23:14:57 2019 Return-Path: Delivered-To: freebsd-current@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 3F16915D5C75 for ; Sat, 6 Jul 2019 23:14:57 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C6B685E1F; Sat, 6 Jul 2019 23:14:56 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id x66NErX5046478 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 6 Jul 2019 16:14:54 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id x66NErtv046477; Sat, 6 Jul 2019 16:14:53 -0700 (PDT) (envelope-from sgk) Date: Sat, 6 Jul 2019 16:14:53 -0700 From: Steve Kargl To: Ian Lepore Cc: Hans Petter Selasky , freebsd-current@freebsd.org Subject: Re: Someone broke USB Message-ID: <20190706231453.GA46470@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20190706182301.GA45149@troutmask.apl.washington.edu> <770bc251-7d0f-d56f-6b86-89245b79945f@selasky.org> <20190706194124.GA45536@troutmask.apl.washington.edu> <8ccf4066-7edc-e8c3-d669-16f649ec03c2@selasky.org> <20190706210613.GA45709@troutmask.apl.washington.edu> <4d866257df0aa0a671973555b4a9a0eb27088d5c.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d866257df0aa0a671973555b4a9a0eb27088d5c.camel@freebsd.org> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 1C6B685E1F X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [0.71 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; NEURAL_HAM_MEDIUM(-0.00)[-0.004,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.55)[-0.546,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[washington.edu]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.38)[0.381,0]; MX_GOOD(-0.01)[cached: troutmask.apl.washington.edu]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.01)[ip: (0.07), ipnet: 128.95.0.0/16(0.07), asn: 73(-0.13), country: US(-0.06)] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jul 2019 23:14:57 -0000 On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > > > On 2019-07-06 21:41, Steve Kargl wrote: > > > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky > > > > wrote: > > > > > On 2019-07-06 20:23, Steve Kargl wrote: > > > > > > So, how does one get usb working, again? > > > > > > > > > > > > -- Steve > > > > > > > > > > Can you show dmesg? > > > > > > > > > > > > > It looks like the enumeration of busses and devices has changed. > > > > grepping for uhub and usbus of the working and broken dmesg.boot > > > > gives > > > > > > > > > > Are you able to bisect the commit introducing the bad behaviour? > > > > > > > I'll give it a shot. I have two revision number to work with. > > > > It seems almost certain to be r349161 that causes the problem. > I've backed out the change, and the buildkernel is currently running. It won't finish for an hour or so (old hardware and rebuilding another project). -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow