Date: Sat, 06 Jul 2019 15:08:13 -0600 From: Ian Lepore <ian@freebsd.org> To: sgk@troutmask.apl.washington.edu, Hans Petter Selasky <hps@selasky.org> Cc: freebsd-current@freebsd.org Subject: Re: Someone broke USB Message-ID: <4d866257df0aa0a671973555b4a9a0eb27088d5c.camel@freebsd.org> In-Reply-To: <20190706210613.GA45709@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d866257df0aa0a671973555b4a9a0eb27088d5c.camel>