Date: Mon, 20 Aug 2012 13:55:24 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Hans Petter Selasky <hans.petter.selasky@bitfrost.no> Cc: "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>, Andrew Turner <andrew@fubar.geek.nz>, Hans Petter Selasky <hselasky@freebsd.org> Subject: Re: svn commit: r239214 - in head/sys: dev/usb dev/usb/controller sys Message-ID: <CAJ-VmombTOLoQ3AQZEfhEUatOnv=wfbw1Ap8jL3phUzQayzROw@mail.gmail.com> In-Reply-To: <zarafa.5030d8f9.78da.3793f9461199bff8@eric2.bitfrost> References: <20120819202622.6db6a8dd@fubar.geek.nz> <zarafa.5030d8f9.78da.3793f9461199bff8@eric2.bitfrost>
next in thread | previous in thread | raw e-mail | index | archive | help
I have a report that AR71XX (MIPS) USB broke with this change. Hans, would you mind reverting it until we figure out what's going on in the non-intel USB world? Thanks, Adrian On 19 August 2012 05:15, Hans Petter Selasky <hans.petter.selasky@bitfrost.no> wrote: > Hi, > > > > What exactly is the driver the USB mass storage device is attached to? > > > > And the problem is the same using the latest FreeBSD version from -current? > > > > You are certain that all parts of the kernel were rebuilt? > > > > And you are certain that it has nothing to do with the FreeBSD version bump > which is also part of this change? > > > > Probably we should move this thread to -current @ > > > > --HPS > > > -----Original message----- > From: Andrew Turner <andrew@fubar.geek.nz> > Sent: Sun 19-08-2012 10:27 > Subject: Re: svn commit: r239214 - in head/sys: dev/usb dev/usb/controller > sys > To: Hans Petter Selasky <hans.petter.selasky@bitfrost.no>; > CC: Hans Petter Selasky <hselasky@freebsd.org>; svn-src-head@freebsd.org; > svn-src-all@freebsd.org; src-committers@freebsd.org; > On Sun, 19 Aug 2012 09:39:11 +0200 > Hans Petter Selasky <hans.petter.selasky@bitfrost.no> wrote: > >> Hi, >> >> >> >> Have you stepped the versions? > I did a binary search of the commits to find the revision that caused > the issue. > >> Are you sure it is exactly this commit? > I built with r239213 and the problem went away, when I built with > r239214 it appeared again. > > Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmombTOLoQ3AQZEfhEUatOnv=wfbw1Ap8jL3phUzQayzROw>