public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Michael Cohen <lkml@ohdarn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Lockups
Date: Mon, 7 Jan 2002 20:01:50 -0500	[thread overview]
Message-ID: <20020107200150.T10145@sventech.com> (raw)
In-Reply-To: <1010449229.4069.6.camel@ohdarn.net> <20020107193600.S10145@sventech.com> <1010451492.4127.8.camel@ohdarn.net>
In-Reply-To: <1010451492.4127.8.camel@ohdarn.net>; from lkml@ohdarn.net on Mon, Jan 07, 2002 at 07:58:12PM -0500

On Mon, Jan 07, 2002, Michael Cohen <lkml@ohdarn.net> wrote:
> > > Tried with UHCI and JE driver. JE doesn't recognize the USB controller
> > > half the time.  It seems to me that this is similar to the problem
> > > with a saturated PCI bus that someone posted a latency fix for.
> > > I'd appreciate any input.  A similar machine does this on windows as
> > > well, too.  BIOS is as late as it gets.
> > 
> > Doesn't recognize the USB controller half the time? This is something I
> > would expect to either work all of the time, or none of the time.
> > 
> > Do you get any error messages?
> 
> The JE driver strangely seems to be an unstable beast on here.
> It more often does not work, though every once in a while it wakes up on
> boot.  I've stuck with the standard.  As for error messages, "No devices
> found" is the only one I get with the standard driver (when nothing is
> plugged in :).  Oh, it's SMP PIII.

It'll say that if usb-uhci is loaded since it has claimed all of the
host controllers.

What sort of instability are you seeing?

JE


      reply	other threads:[~2002-01-08  1:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08  0:20 USB Lockups Michael Cohen
2002-01-08  0:36 ` Johannes Erdfelt
2002-01-08  0:58   ` Michael Cohen
2002-01-08  1:01     ` Johannes Erdfelt [this message]

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=20020107200150.T10145@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@ohdarn.net \
    /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