From: Greg KH <greg@wirex.com>
To: f5ibh <f5ibh@db0bm.ampr.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18pre, usb mouse messages
Date: Thu, 23 Nov 2000 13:48:04 -0800 [thread overview]
Message-ID: <20001123134804.C28923@wirex.com> (raw)
In-Reply-To: <200011232132.WAA29552@db0bm.ampr.org>
In-Reply-To: <200011232132.WAA29552@db0bm.ampr.org>; from f5ibh@db0bm.ampr.org on Thu, Nov 23, 2000 at 10:32:01PM +0100
On Thu, Nov 23, 2000 at 10:32:01PM +0100, f5ibh wrote:
> Hi,
>
> I use an USB mouse, it works perfectly both with 'gpm' and with X-window but
> time to time, I've this kind of message stream :
>
> [root@debian-f5ibh] ~ # usb-uhci.c: interrupt, status 3, frame# 20
> usb-uhci.c: interrupt, status 3, frame# 44
> usb-uhci.c: interrupt, status 3, frame# 68
> usb-uhci.c: interrupt, status 3, frame# 92
> usb-uhci.c: interrupt, status 3, frame# 116
> usb-uhci.c: interrupt, status 3, frame# 140
> usb-uhci.c: interrupt, status 3, frame# 164
> usb-uhci.c: interrupt, status 3, frame# 188
> usb-uhci.c: interrupt, status 3, frame# 212
> hub.c: already running port 2 disabled by hub (EMI?), re-enabling...
>
> This message appears with most (all ?) of the 2.2.18pre releases, the actual
> one is 2.2.18pre23.
The messages are harmless debug messages. Anyone want to whip up a
patch to turn them off (like was recently done for 2.4.0-test)? If no
one else does, I can do it later this weekend...
greg k-h
--
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 21:32 2.2.18pre, usb mouse messages f5ibh
2000-11-23 21:48 ` Greg KH [this message]
2000-11-24 6:31 ` Peter Samuelson
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=20001123134804.C28923@wirex.com \
--to=greg@wirex.com \
--cc=f5ibh@db0bm.ampr.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.