From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: Re: 2.2.18-24 intermittent PS/2 mouse problems
Date: Wed, 6 Dec 2000 20:14:36 -0700 [thread overview]
Message-ID: <20001206201436.A15470@vger.timpanogas.org> (raw)
In-Reply-To: <20001206201019.A15457@vger.timpanogas.org>
In-Reply-To: <20001206201019.A15457@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Wed, Dec 06, 2000 at 08:10:19PM -0700
On Wed, Dec 06, 2000 at 08:10:19PM -0700, Jeff V. Merkey wrote:
>
>
> Alan,
>
> I am still seeing intermittent mouse problems with a PS2 mouse on a
> 4 x PPro box with 2.2.18-24. When the system is first powered up,
> the mouse detection is working great. If I reboot the machine without
> powering it down, about 1 in 3 times I do this, the next kernel load
> fails to detect the mouse. I have not looked at the driver to see
> what state the Mouse port is in, but could.
>
> Is there something I could do to help you debug this problem (i.e.
> is there somewhere in the kernel code I should put in some
> sanity checking to see if the mouse is being left in a good state.
>
> Powering down the machine makes the problem go away. Does not happen
> on 2.4.0-12, BTW, just 2.2.18-24.
>
> Jeff
Alan,
One more thing. I was able to reproduce it once during an initial powerup
sequence by putzing with the mouse buttons while the auto-detection was going
on (generating interrupts?). I am wondering if the problem in in the way
interrupts are being handled for the mouse. If I leave the mouse alone
it seems to get autodetected properly.
Jeff
-
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/
prev parent reply other threads:[~2000-12-07 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 3:10 Jeff V. Merkey
2000-12-07 3:14 ` Jeff V. Merkey [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=20001206201436.A15470@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®