Someone broke USB
Steve Kargl
sgk at troutmask.apl.washington.edu
Sat Jul 6 23:14:57 UTC 2019
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
More information about the freebsd-current
mailing list