public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mouse resync messages since 2.6.15-rc2-mm1, still in 2.6.15-rc3-mm1
Date: Thu, 1 Dec 2005 20:59:38 -0500	[thread overview]
Message-ID: <200512012059.39163.dtor_core@ameritech.net> (raw)
In-Reply-To: <20051201195145.GA20896@amd64.of.nowhere>

On Thursday 01 December 2005 14:51, jurriaan wrote:
> I access my workstations with a KVM switch, a Rose Vista model, and
> since 2.6.15-rc2-mm1, I get an awful lot of
> 
> logips2pp: Detected unknown logitech mouse model 1
> psmouse.c: resync failed, issuing reconnect request
> 
> messages. What is the information content in these messages? I take it
> they tell me something important - but I can't understand what. If they
> are just noise, could they please be removed?
> I know my mouse works when I switch consoles; this KVM has worked for
> ages with linux. 
>

You not supposed to see thiese messages. When you boot, what mouse type
does the kernel detect? Could you send me your dmesg please? Also, if
you could do:

1. echo 1 > /sys/modules/i8042/parameters/debug
2. Switch your KVM to another box
3. Wait 5 seconds
4. Switch back
5. Move the mouse slightly
6. echo 0 > /sys/modules/i8042/parameters/debug

... and send me dmesg I would appreciate it. 

> I can always #if 0 them out myself, but I'm curious what the meaning of
> these messages is.
>

You can disable resync mode by doing:

	echo -n 0 > /sys/bus/serio/devices/serioX/resync_time

where serioX is serio port your mouse is connected to.

-- 
Dmitry

      reply	other threads:[~2005-12-02  1:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 19:51 mouse resync messages since 2.6.15-rc2-mm1, still in 2.6.15-rc3-mm1 jurriaan
2005-12-02  1:59 ` Dmitry Torokhov [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=200512012059.39163.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    /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