Dear Linux hackers,
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.
I notice this, if the scroll wheel does not work under X. Doing `sudo
rmmod psmouse` and `sudo modprobe psmouse` fixes the issue for me in
this (boot) session.
I have not found the reason for this and am not able to reproduce this.
As written this issue pops up arbitrarily.
$ uname -a
Linux x 2.6.29-1-amd64 #1 SMP Fri Apr 17 16:26:42 UTC 2009 x86_64 GNU/Linux
$ lsmod | grep mouse
psmouse 41548 0
$ dmesg # excerpt
[…]
[ 1.021991] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 1.022270] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
[ 1.022734] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.022797] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.028167] mice: PS/2 mouse device common for all mice
[…]
[ 25.007328] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 25.754932] input: PS2++ Logitech Mouse as /devices/platform/i8042/serio1/input/input6
[…]
# after doing `sudo rmmod psmouse` and `sudo modprobe psmouse`
[ 1159.636233] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input7
$ diff -u /var/log/Xorg.0.log.old /var/log/Xorg.0.log | less # old is the “good” version with scroll wheel working
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
-(II) config/hal: Adding input device ImPS/2 Logitech Wheel Mouse
-(**) ImPS/2 Logitech Wheel Mouse: always reports core events
-(**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event6"
-(II) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
-(II) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
-(II) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
-(II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
-(**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
-(**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
-(II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE)
-(**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
-(**) ImPS/2 Logitech Wheel Mouse: (accel) filter chain progression: 2.00
-(**) ImPS/2 Logitech Wheel Mouse: (accel) filter stage 0: 20.00 ms
-(**) ImPS/2 Logitech Wheel Mouse: (accel) set acceleration profile 0
+(II) config/hal: Adding input device PS2++ Logitech Mouse
+(**) PS2++ Logitech Mouse: always reports core events
+(**) PS2++ Logitech Mouse: Device: "/dev/input/event6"
+(II) PS2++ Logitech Mouse: Found 3 mouse buttons
+(II) PS2++ Logitech Mouse: Found x and y relative axes
+(II) PS2++ Logitech Mouse: Configuring as mouse
+(**) PS2++ Logitech Mouse: YAxisMapping: buttons 4 and 5
+(**) PS2++ Logitech Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
+(II) XINPUT: Adding extended input device "PS2++ Logitech Mouse" (type: MOUSE)
+(**) PS2++ Logitech Mouse: (accel) keeping acceleration scheme 1
+(**) PS2++ Logitech Mouse: (accel) filter chain progression: 2.00
+(**) PS2++ Logitech Mouse: (accel) filter stage 0: 20.00 ms
+(**) PS2++ Logitech Mouse: (accel) set acceleration profile 0
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
Do you know what could causing this? If I can provide more information,
just tell me what.
Thanks,
Paul
[ added linux-input@ to CC ]
On Fri, 12 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.
[ left the rest of the message for linux-input@ ]
>
> I notice this, if the scroll wheel does not work under X. Doing `sudo
> rmmod psmouse` and `sudo modprobe psmouse` fixes the issue for me in
> this (boot) session.
>
> I have not found the reason for this and am not able to reproduce this.
> As written this issue pops up arbitrarily.
>
> $ uname -a
> Linux x 2.6.29-1-amd64 #1 SMP Fri Apr 17 16:26:42 UTC 2009 x86_64 GNU/Linux
>
> $ lsmod | grep mouse
> psmouse 41548 0
>
> $ dmesg # excerpt
> [?]
> [ 1.021991] input: Macintosh mouse button emulation as /devices/virtual/input/input0
> [ 1.022270] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
> [ 1.022734] serio: i8042 KBD port at 0x60,0x64 irq 1
> [ 1.022797] serio: i8042 AUX port at 0x60,0x64 irq 12
> [ 1.028167] mice: PS/2 mouse device common for all mice
> [?]
> [ 25.007328] input: PC Speaker as /devices/platform/pcspkr/input/input5
> [ 25.754932] input: PS2++ Logitech Mouse as /devices/platform/i8042/serio1/input/input6
> [?]
> # after doing `sudo rmmod psmouse` and `sudo modprobe psmouse`
> [ 1159.636233] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input7
>
> $ diff -u /var/log/Xorg.0.log.old /var/log/Xorg.0.log | less # old is the ?good? version with scroll wheel working
>
> (**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
> (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
> (**) Macintosh mouse button emulation: (accel) set acceleration profile 0
> -(II) config/hal: Adding input device ImPS/2 Logitech Wheel Mouse
> -(**) ImPS/2 Logitech Wheel Mouse: always reports core events
> -(**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event6"
> -(II) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
> -(II) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
> -(II) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
> -(II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
> -(**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
> -(**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> -(II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE)
> -(**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
> -(**) ImPS/2 Logitech Wheel Mouse: (accel) filter chain progression: 2.00
> -(**) ImPS/2 Logitech Wheel Mouse: (accel) filter stage 0: 20.00 ms
> -(**) ImPS/2 Logitech Wheel Mouse: (accel) set acceleration profile 0
> +(II) config/hal: Adding input device PS2++ Logitech Mouse
> +(**) PS2++ Logitech Mouse: always reports core events
> +(**) PS2++ Logitech Mouse: Device: "/dev/input/event6"
> +(II) PS2++ Logitech Mouse: Found 3 mouse buttons
> +(II) PS2++ Logitech Mouse: Found x and y relative axes
> +(II) PS2++ Logitech Mouse: Configuring as mouse
> +(**) PS2++ Logitech Mouse: YAxisMapping: buttons 4 and 5
> +(**) PS2++ Logitech Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> +(II) XINPUT: Adding extended input device "PS2++ Logitech Mouse" (type: MOUSE)
> +(**) PS2++ Logitech Mouse: (accel) keeping acceleration scheme 1
> +(**) PS2++ Logitech Mouse: (accel) filter chain progression: 2.00
> +(**) PS2++ Logitech Mouse: (accel) filter stage 0: 20.00 ms
> +(**) PS2++ Logitech Mouse: (accel) set acceleration profile 0
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
>
>
> Do you know what could causing this? If I can provide more information,
> just tell me what.
>
>
> Thanks,
>
> Paul
>
--
Jiri Kosina
SUSE Labs
Am Freitag, den 12.06.2009, 16:51 +0200 schrieb Jiri Kosina:
> [ added linux-input@ to CC ]
Maybe the contact address in MAINTAINERS should be set to linux-input@?
> On Fri, 12 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?
Jun 14 10:34:16 x kernel: [ 4667.683375] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: 28 <- i8042 (interrupt, 1, 12) [1166664]
Jun 14 10:34:16 x kernel: [ 4667.684331] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [1166665]
Jun 14 10:34:16 x kernel: [ 4667.685311] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: fb <- i8042 (interrupt, 1, 12) [1166665]
Jun 14 10:34:16 x kernel: [ 4667.686329] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [1166665]
Jun 14 10:34:16 x kernel: [ 4667.703063] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: 28 <- i8042 (interrupt, 1, 12) [1166669]
Jun 14 10:34:16 x kernel: [ 4667.704016] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [1166670]
Jun 14 10:34:16 x kernel: [ 4667.704980] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: f9 <- i8042 (interrupt, 1, 12) [1166670]
Jun 14 10:34:16 x kernel: [ 4667.705966] /build/buildd-linux-2.6_2.6.29-5-i386-xtBC0n/linux-2.6-2.6.29/debian/build/source_i386_none/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [1166670]
Thanks,
Paul
On Sun, 14 Jun 2009, Paul Menzel wrote:
> > [ added linux-input@ to CC ]
> Maybe the contact address in MAINTAINERS should be set to linux-input@?
I actually wanted to CC Dmitry as well, but forgot to do so.
> > > 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.
Thanks,
--
Jiri Kosina
SUSE Labs
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