public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Dan Hopper <dbhopper@austin.rr.com>, Greg KH <greg@kroah.com>,
	Patrick Mochel <mochel@osdl.org>,
	Pierre Rousselet <pierre.rousselet@wanadoo.fr>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: 2.5.5-pre1 rmmod usb-uhci hangs
Date: Sun, 24 Feb 2002 12:50:55 -0500	[thread overview]
Message-ID: <20020224125055.A5232@sventech.com> (raw)
In-Reply-To: <fa.n7cofbv.1him3j@ifi.uio.no> <fa.dsb79pv.on84ii@ifi.uio.no> <20020224025411.GA2418@yoda.dummynet> <20020224062124.GB15060@kroah.com> <20020224063915.GA2799@yoda.dummynet> <20020224064931.GD15060@kroah.com> <20020224173711.GA2355@yoda.dummynet>
In-Reply-To: <20020224173711.GA2355@yoda.dummynet>; from dbhopper@austin.rr.com on Sun, Feb 24, 2002 at 11:37:11AM -0600

On Sun, Feb 24, 2002, Dan Hopper <dbhopper@austin.rr.com> wrote:
> Greg KH <greg@kroah.com> remarked:
> > On Sun, Feb 24, 2002 at 12:39:15AM -0600, Dan Hopper wrote:
> > > 
> > > The reason I'd like to switch back to usb-uhci instead of uhci is
> > > twfold:  Vmware seems to want to only use usb-uhci and not uhci
> > > (dummies!).  And uhci seems to be unable to get the scanner going
> > > such that it doesn't "stutter" all the way down the page.  usb-uhci
> > > seems to be able to keep up so that it just sweeps on down the page.
> > 
> > I noticed that Vmware does that, and was wondering why.
> > 
> > If you get a chance, can you try the uhci patches that were posted on
> > linux-usb-devel last week, or all of them rolled up at:
> > 	http://www.kernel.org/pub/linux/kernel/people/gregkh/usb/linux-2.4.18-rc2-gregkh-1.patch.gz
> > and let me know if that solves your problem with uhci or not?
> 
> Well, that was interesting.  I upgraded to rc2 and applied that
> patch.  uhci still behaved the same (can't keep up with scanner). 
> But usb-uhci now doesn't lock up the system on a shutdown.  And it
> was the patch that did it, not rc2, because I tried a pristine rc2
> build, too, and it still locks up.  I note that there's nothing in
> the patch that directly touches usb-uhci, so it must be a side
> affect of some other fix.

Hmm, that is interesting. I wonder what is going on with it. Are you
using the scanner kernel driver?

JE


  reply	other threads:[~2002-02-24 17:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.n7cofbv.1him3j@ifi.uio.no>
     [not found] ` <fa.dsb79pv.on84ii@ifi.uio.no>
2002-02-24  2:54   ` 2.5.5-pre1 rmmod usb-uhci hangs Dan Hopper
2002-02-24  6:21     ` Greg KH
2002-02-24  6:39       ` Dan Hopper
2002-02-24  6:49         ` Greg KH
2002-02-24 17:37           ` Dan Hopper
2002-02-24 17:50             ` Johannes Erdfelt [this message]
2002-02-24 18:49               ` [linux-usb-devel] " Dan Hopper
2002-02-25  3:41                 ` Johannes Erdfelt
2002-02-26  3:22                   ` Dan Hopper
2002-02-26  3:39                     ` Johannes Erdfelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020224125055.A5232@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=dbhopper@austin.rr.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mochel@osdl.org \
    --cc=pierre.rousselet@wanadoo.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox