From: Matthew Harrell <lists-sender-14a37a@bittwiddlers.com>
To: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.4[3-5] usb problems
Date: Fri, 1 Nov 2002 11:35:47 -0500 [thread overview]
Message-ID: <20021101163547.GA10449@bittwiddlers.com> (raw)
In-Reply-To: <20021101142751.GA908@bittwiddlers.com>
: Finally, I've noticed a few times that the mouse has taken a vacation - i.e.
: I move it and nothing happens. This goes on for about twenty seconds and then
: all the movements in did in the interum start happening. During this twenty
: seconds my built-in PS/2 mouse works fine. Oh, and I get no kernel output
: from any of this.
More on this problem - it's not a time issue. It's happened three more times
and I noticed that the mouse suddenly started working when I hit keys (any key)
on the USB keyboard. And it starts up working by executing everything I did
to the mouse in the interum
--
Matthew Harrell Gravity is a myth, the Earth sucks.
Bit Twiddlers, Inc.
mharrell@bittwiddlers.com
next prev parent reply other threads:[~2002-11-01 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 14:27 2.5.4[3-5] usb problems Matthew Harrell
2002-11-01 16:35 ` Matthew Harrell [this message]
2002-11-01 21:50 ` Greg KH
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=20021101163547.GA10449@bittwiddlers.com \
--to=lists-sender-14a37a@bittwiddlers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell-dated-1036600547.a57f33@bittwiddlers.com \
/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