public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Aaron D. Turner" <aturner@whiskey.synfin.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13pre5 breaks usb-storage ?
Date: Sat, 20 Oct 2001 16:20:21 -0700	[thread overview]
Message-ID: <20011020162021.A4814@kroah.com> (raw)
In-Reply-To: <20011020125945.B4314@kroah.com> <Pine.LNX.4.33.0110201546080.1235-200000@whiskey.synfin.net>
In-Reply-To: <Pine.LNX.4.33.0110201546080.1235-200000@whiskey.synfin.net>

On Sat, Oct 20, 2001 at 03:51:06PM -0700, Aaron D. Turner wrote:
> 
> On Sat, 20 Oct 2001, Greg KH wrote:
> 
> > If you use usb-uhci.o instead of uhci.o on 2.4.13-pre5, does that work?
> > 
> > The uhci.o driver has changed between -pre3 and -pre5, not usb-storage.
> 
> Well looks like I spoke too soon.  Works great on the IBM 600X, but USB is 
> completely hosed under 2.4.13pre5 on my Athalon system.  Can't get the 
> mouse to work, or the pendrive.  I'm getting Oops's during boot in various 
> places (seems to be dependant on what USB things are compiled statically 
> vs. modules).  One such oops is included in the attached dmesg.
> 
> I haven't tried 2.4.13p3 on the Athalon, this was a direct upgrade from 
> 2.4.10.

Bleah, this is the hub.c bug.  This problem is fixed in the -ac tree.
I'd recommend using that tree for now, or just grab the
drivers/usb/hub.c and drivers/usb/hub.h files from a -ac tree and put
them in your 2.4.13-pre5 directory.

If you still have problems after doing that, please let me know.

thanks,

greg k-h

      reply	other threads:[~2001-10-20 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20 18:50 2.4.13pre5 breaks usb-storage ? Aaron D. Turner
2001-10-20 19:59 ` Greg KH
2001-10-20 20:49   ` justme
2001-10-20 22:51   ` Aaron D. Turner
2001-10-20 23:20     ` Greg KH [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=20011020162021.A4814@kroah.com \
    --to=greg@kroah.com \
    --cc=aturner@whiskey.synfin.net \
    --cc=linux-kernel@vger.kernel.org \
    /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