Date: Tue, 20 Feb 2007 16:12:50 -0500 From: John Baldwin <jhb@freebsd.org> To: Thomas.Sparrevohn@btinternet.com Cc: 'Thomas Sparrevohn' <t.sparrevohn@btinternet.com>, freebsd-usb@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: USB fails to attach in the SMP version of GENERIC with Nforce 590 Message-ID: <200702201612.51420.jhb@freebsd.org> In-Reply-To: <000a01c7551e$e1370e10$a3a52a30$@Sparrevohn@btinternet.com> References: <C0A29426-2516-496B-89FB-3EAF3AC6D3F2@btinternet.com> <200702201146.54419.jhb@freebsd.org> <000a01c7551e$e1370e10$a3a52a30$@Sparrevohn@btinternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 20 February 2007 13:42, Thomas Sparrevohn wrote: > Yes - I am always normally running CURRENT - It was when I couldn't get USB > to work > I tried with the 6.2 Image I had installed from and was surprised to > discover it worked > Under 6.2 - but then I discovered that SMP wasn't enabled So what I see from your e-mail is that a 6.2 UP kernel works fine (but no SMP), and a 7.0 SMP kernel breaks, but you want SMP. Have you tried a 6.2 SMP kernel? I imagine that is going to work fine. You have way too many variables here. The USB breakage could be due to SMP vs UP (I doubt it) or due to 6.2 vs 7.0 (more likely). > -----Original Message----- > From: owner-freebsd-amd64@freebsd.org > [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of John Baldwin > Sent: 20 February 2007 16:47 > To: freebsd-amd64@freebsd.org > Cc: Thomas Sparrevohn; freebsd-usb@freebsd.org > Subject: Re: USB fails to attach in the SMP version of GENERIC with Nforce > 590 > > On Saturday 17 February 2007 16:34, Thomas Sparrevohn wrote: > > HI > > Its a bit of a weird problem - If I boot the 6.2 RELEASE UP kernel - > > all USB devices works fine > > however it I boot with the most recent (cvsup today) - It fails > > attaching the root device. > > The only major difference are that the 6.2-RELEASE looks like its a > > UP kernel or at least > > it never starts the 3 other cores > > Well, you cvsupp'ed current (7.0) not 6.x-stable, was that on purpose? > It does look like the uhub(4) driver is what is keeling over. > -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702201612.51420.jhb>