Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jan 2006 20:11:49 +0100
From:      Juergen Lock <nox@jelal.kn-bremen.de>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-usb@freebsd.org
Subject:   Re: ehci not used(?) when connected device turned on later
Message-ID:  <20060119191149.GA13509@saturn.kn-bremen.de>
In-Reply-To: <20060117.163851.10386451.imp@bsdimp.com>
References:  <20060117225131.GA6571@saturn.kn-bremen.de> <20060117.162938.68129078.imp@bsdimp.com> <20060117.163851.10386451.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Tue, Jan 17, 2006 at 04:38:51PM -0700, Warner Losh wrote:
> From: Warner Losh <imp@bsdimp.com>
> Subject: Re: ehci not used(?) when connected device turned on later
> Date: Tue, 17 Jan 2006 16:29:38 -0700 (MST)
> 
> > From: Juergen Lock <nox@jelal.kn-bremen.de>
> > Subject: ehci not used(?) when connected device turned on later
> > Date: Tue, 17 Jan 2006 23:51:31 +0100
> > 
> > > Is this a known problem with the 5.4 usb code?
> > > 
> > > 1. connect an externally powered umass device (eg a harddrive with
> > > its own psu) thats turned off
> > > 2. boot freebsd
> > > 3. turn the device on later
> > > 
> > >  then it gets only usb 1.1 speed even when ehci is in the kernel.
> > > You have to reconnect it _while being turned on_ to get usb2 speed.
> > > Same problem if you turn it off after use and later turn it back on
> > > while still being connected...
> > > 
> > >  Is there a fix?  (With linux it works as expected, if that means
> > > anything... :)
> > > 
> > >  Oh, please Cc me with followups, I'm not subscribed on -usb (yet?)
> > 
> > I have no idea what you are saying.
> > 
> > ehci is used for me when I plug in my devices, or when I turn them
> > on.  Do you have ehci in your kernel?  It was disabled by default in
> > 5.4.
> 
> Oh, I'm slow today...
> 
> I'm pretty sure that -current does the right thing, but I'll double
> check tonight.

I got one instance of `40.000MB/s transfers' dmesg after turning it
on today, so apparently it only `sometimes' doesnt work.  (Next try
it didn't.)  Some kind of race?  Maybe the `rate of success' depends
on the device as well, as you haven't seen the problem at all... (right?)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060119191149.GA13509>