Date: Sun, 19 Aug 2012 14:15:53 +0200 From: =?windows-1252?Q?Hans_Petter_Selasky?= <hans.petter.selasky@bitfrost.no> To: =?windows-1252?Q?Andrew_Turner?= <andrew@fubar.geek.nz> Cc: "=?windows-1252?Q?svn-src-head=40freebsd.org?=" <svn-src-head@freebsd.org>, "=?windows-1252?Q?svn-src-all=40freebsd.org?=" <svn-src-all@freebsd.org>, "=?windows-1252?Q?src-committers=40freebsd.org?=" <src-committers@freebsd.org>, =?windows-1252?Q?Hans_Petter_Selasky?= <hselasky@freebsd.org> Subject: RE: svn commit: r239214 - in head/sys: dev/usb dev/usb/controller sys Message-ID: <zarafa.5030d8f9.78da.3793f9461199bff8@eric2.bitfrost> In-Reply-To: <20120819202622.6db6a8dd@fubar.geek.nz> References: <20120819202622.6db6a8dd@fubar.geek.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,=0D=0A=0D=0A=A0=0D=0A=0D=0AWhat exactly is the driver the USB mass sto= rage device is attached to=3F=0D=0A=0D=0A=A0=0D=0A=0D=0AAnd the problem i= s the same using the latest FreeBSD version from -current=3F=0D=0A=0D=0A=A0= =0D=0A=0D=0AYou are certain that all parts of the kernel were rebuilt=3F=0D= =0A=0D=0A=A0=0D=0A=0D=0AAnd you are certain that it has nothing to do wit= h the FreeBSD version bump which is also part of this change=3F=0D=0A=0D=0A= =A0=0D=0A=0D=0AProbably we should move this thread to -current @=0D=0A=0D= =0A=A0=0D=0A=0D=0A--HPS=0D=0A=A0=0D=0A-----Original message-----=0D=0AFro= m:Andrew Turner <andrew@fubar.geek.nz>=0D=0ASent:Sun 19-08-2012 10:27=0D=0A= Subject:Re: svn commit: r239214 - in head/sys: dev/usb dev/usb/controller= sys=0D=0ATo:Hans Petter Selasky <hans.petter.selasky@bitfrost.no>;=20=0D= =0ACC:Hans Petter Selasky <hselasky@freebsd.org>; svn-src-head@freebsd.or= g; svn-src-all@freebsd.org; src-committers@freebsd.org;=20=0D=0AOn Sun, 1= 9 Aug 2012 09:39:11 +0200=0D=0AHans Petter Selasky =A0<hans.petter.selask= y@bitfrost.no> wrote:=0D=0A=0D=0A> Hi,=0D=0A>=20=0D=0A> =A0=0D=0A>=20=0D=0A= > Have you stepped the versions=3F=0D=0AI did a binary search of the comm= its to find the revision that caused=0D=0Athe issue.=0D=0A=0D=0A> Are you= sure it is exactly this commit=3F=0D=0AI built with r239213 and the prob= lem went away, when I built with=0D=0Ar239214 it appeared again.=0D=0A=0D= =0AAndrew=0D=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zarafa.5030d8f9.78da.3793f9461199bff8>