Date: Sat, 6 Jul 2019 14:06:13 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-current@freebsd.org Subject: Re: Someone broke USB Message-ID: <20190706210613.GA45709@troutmask.apl.washington.edu> In-Reply-To: <8ccf4066-7edc-e8c3-d669-16f649ec03c2@selasky.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190706210613.GA45709>