From: David T Hollis <dhollis@davehollis.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Mouse oddity with 2.6.0-test2-mm4 + 013int
Date: Mon, 04 Aug 2003 21:57:03 -0400 [thread overview]
Message-ID: <3F2F0EEF.3080705@davehollis.com> (raw)
In-Reply-To: <20030805004552.GA17205@kroah.com>
Greg KH wrote:
>On Mon, Aug 04, 2003 at 05:39:30PM -0400, David T Hollis wrote:
>
>
>>I just went to 2.6.0-test2-mm4 with Con's 012/013 interactivity patches
>>(from 2.6.0-test2-mm2) on my laptop and I'm now having an odd time with
>>my USB mouse. After a short period of time (5 minutes or less), it
>>stops working entirely. If I remove the usbmouse module and reload it,
>>I get it back. There is nothing in my logs or dmesg output stating any
>>kind of problem. Is anyone else seeing this problem? Anyone happen to
>>know where the problem may lie?
>>
>>
>
>Don't use the usbmouse module, use the hid module instead.
>
>But that should not really cause this problem. Can you enable
>CONFIG_USB_DEBUG to see if anything else shows up in your logs?
>
>Oh, and does this also happen with 2.6.0-test2?
>
>thanks,
>
>greg k-h
>
>
It worked fine under 2.6.0-test2-mm2 and 2.6.0-test2-mm1. With some
further investigating, it seems that usbmouse is not loaded at startup,
just hid. Following your suggestion, I removed both and just loaded hid
and the mouse works ok, for a short period of time. Eventually it stops
and I have to rmmod hid and reload load it. Sometimes I get a decent
amount of time (maybe 30 minutes or so) before it sticks. I'm turning
on USB_DEBUG and will rebuild to see if I get any more helpful info.
prev parent reply other threads:[~2003-08-05 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 21:39 USB Mouse oddity with 2.6.0-test2-mm4 + 013int David T Hollis
2003-08-05 0:45 ` Greg KH
2003-08-05 1:57 ` David T Hollis [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=3F2F0EEF.3080705@davehollis.com \
--to=dhollis@davehollis.com \
--cc=greg@kroah.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 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.