From: Johannes Erdfelt <johannes@erdfelt.com>
To: drizzt.dourden@iname.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [drizzt.dourden@iname.com: USB mass storage and USB message]
Date: Thu, 15 Feb 2001 15:49:47 -0500 [thread overview]
Message-ID: <20010215154946.M23514@sventech.com> (raw)
In-Reply-To: <20010215214330.B2094@menzoberrazan>
In-Reply-To: <20010215214330.B2094@menzoberrazan>; from drizzt.dourden@iname.com on Thu, Feb 15, 2001 at 09:43:30PM +0100
On Thu, Feb 15, 2001, drizzt.dourden@iname.com <drizzt.dourden@iname.com> wrote:
> I'm using the usb-uhci core with the 8200e storage drivers. I don't why
> the kernel logs the next message:
>
> uhci.c: root-hub INT complete: port1: 495 port2: 58a data: 4
> uhci.c: root-hub INT complete: port1: 495 port2: 58a data: 4
> uhci.c: root-hub INT complete: port1: 495 port2: 58a data: 4
> uhci.c: root-hub INT complete: port1: 495 port2: 58a data: 4
> uhci.c: root-hub INT complete: port1: 495 port2: 58a data: 4
> uhci.c: root-hub INT complete: port1: 495 port2: 58a data: 4
> (well a lot of them)
If it says, uhci.c, then it would be uhci.o. If it says usb-uhci.c, then
it's usb-uhci.o. Your statement conflicts with the log you pasted. Which
one is it?
> The kernel is 2.4.1, the hardware a Celeron 566 with a VIA chipset, with the
> next cat /proc/pci
>
> This doesn't hapeng with the uhci module.
>
> I was testing the cd writer with cdrecord at x1 speed( well, at least it can
> finish th simulation, because with the pre series, it can finished).
Did you get an oops? Is the khubd process zombied?
JE
prev parent reply other threads:[~2001-02-15 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 20:43 [drizzt.dourden@iname.com: USB mass storage and USB message] drizzt.dourden
2001-02-15 20:49 ` 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=20010215154946.M23514@sventech.com \
--to=johannes@erdfelt.com \
--cc=drizzt.dourden@iname.com \
--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