From: Greg KH <greg@kroah.com>
To: Nathan <wfilardo@fuse.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: USB OOPS persists in 2.5.3-dj4
Date: Mon, 11 Feb 2002 13:58:20 -0800 [thread overview]
Message-ID: <20020211215820.GH12514@kroah.com> (raw)
In-Reply-To: <3C644F9B.4050702@fuse.net> <20020209001405.GG27610@kroah.com> <3C64B635.5080804@fuse.net>
In-Reply-To: <3C64B635.5080804@fuse.net>
On Sat, Feb 09, 2002 at 12:40:05AM -0500, Nathan wrote:
> Greg KH wrote:
>
> >
> >Can you let me know if 2.5.4-pre3 has this problem?
> >
> No, it does not have *this* problem, however...
>
> rmmod usb-uhci
> rmmod usbcore - "in use"
> umount /proc/bus/usb
> rmmod usbcore
> modprobe usbcore
> mount -t usbdevfs none /proc/bus/usb
> modprobe uhci - OOPS. Didn't manage to capture it. System kept running.
That's the important one. Everything else was just errors because of
this one. Let me know if you can capture this.
thanks,
greg k-h
prev parent reply other threads:[~2002-02-11 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 22:22 USB OOPS persists in 2.5.3-dj4 Nathan
2002-02-09 0:14 ` Greg KH
2002-02-09 0:25 ` Dave Jones
2002-02-09 5:40 ` Nathan
2002-02-11 21:58 ` 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=20020211215820.GH12514@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wfilardo@fuse.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