lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1254994936.6681.32.camel@mattotaupa.wohnung.familie-menzel.net>
Date:	Thu, 08 Oct 2009 09:42:16 +0000
From:	Paul Menzel <paulepanter@...rs.sourceforge.net>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [BUG] [input] Sometimes mouse gets detected as PS2++ Logitech
 Mouse instead of ImPS/2 Logitech Wheel Mouse

Am Montag, den 10.08.2009, 16:23 +0200 schrieb Paul Menzel:
> Am Dienstag, den 16.06.2009, 11:43 +0200 schrieb Jiri Kosina:
> > On Sun, 14 Jun 2009, Paul Menzel wrote:
> 
> […]
> 
> > > > > arbitrarily (I would say every two month) my Logitech Cordless MouseMan
> > > > > Wheel gets detected as (in dmesg)
> > > > > 
> > > > > PS2++ Logitech Mouse
> > > > > 
> > > > > instead of
> > > > > 
> > > > > ImPS/2 Logitech Wheel Mouse.
> > > > It would be nice if you could capture the dmesg output with i8042.debug 
> > > > command-line from the situation the mouse gets mis-detected. But I 
> > > > understand that with so low frequency of occurence, that would be a major 
> > > > pain.
> > > No problem. The problem has not yet surfaced again. But do I need to
> > > rebuild Linux or are those debug messages enough?
> > 
> > No rebuilding needed, just booting with i8042.debug is enough. Please 
> > provide us with the output once the bug triggers again.
> 
> Please find the dmesg output attached. After noticing I also issued
> 
> $ sudo rmmod psmouse

$ sudo modprobe -r psmouse # “more correct”

> $ sudo modprobe psmouse
> 
> to fix the problem.
> 
> It triggered today. I cannot remember the times before, but today I had
> to turn off the system holding the power button for some seconds because
> the system had crashed and the bug triggered the next boot. I do not
> know if that matters.

I just wanted to tell you that the problem surfaced yesterday again.
This time with

linux-image-2.6.30-2-amd64 2.6.30-8

under Debian sid/unstable.


Thanks,

Paul

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ