[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071107123237.d318cdbf.akpm@linux-foundation.org>
Date: Wed, 7 Nov 2007 12:32:37 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA>
Cc: linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: BUG: usb Mouse continual disconnect (2.6.22.10) leading to
eventual crash?
(+linux-usb-devel)
> On Wed, 7 Nov 2007 13:19:47 -0500 "Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA> wrote:
> Hi all,
>
> I'm having a preblem with a few workstations that are hard freezing from
> time to time since about a week. Curiously since then we upgraded from
> 2.6.20.6 to 2.6.20.10...
>
> While investigating I found out that there seems to be a problem,
> occuring randomly on some workstations after a certain amount time, that
> the mouse gets disconnected continously (see full log attached):
> Nov 7 00:09:36 mammatus kernel: [22055.357104] usb 2-1: USB disconnect,
> address 2
> Nov 7 00:09:37 mammatus kernel: [22055.596974] usb 2-1: new low speed
> USB device using uhci_hcd and address 3
> Nov 7 00:09:37 mammatus kernel: [22055.777831] usb 2-1: configuration
> #1 chosen from 1 choice
> Nov 7 00:09:37 mammatus kernel: [22055.793905] input: Logitech USB-PS/2
> Optical Mouse as /class/input/input5
> Nov 7 00:09:37 mammatus kernel: [22055.793994] input: USB HID v1.10
> Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1
> Nov 7 00:10:11 mammatus kernel: [22090.368722] usb 2-1: USB disconnect,
> address 3
> Nov 7 00:10:12 mammatus kernel: [22090.608588] usb 2-1: new low speed
> USB device using uhci_hcd and address 4
> Nov 7 00:10:12 mammatus kernel: [22090.784671] usb 2-1: configuration
> #1 chosen from 1 choice
> Nov 7 00:10:12 mammatus kernel: [22090.800881] input: Logitech USB-PS/2
> Optical Mouse as /class/input/input6
> Nov 7 00:10:12 mammatus kernel: [22090.800982] input: USB HID v1.10
> Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1
> [.....]
> Nov 7 17:57:28 mammatus kernel: [86097.543960] input: Logitech USB-PS/2
> Optical Mouse as /class/input/input596
> Nov 7 17:57:28 mammatus kernel: [86097.544050] input: USB HID v1.10
> Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1
> Nov 7 17:59:07 mammatus kernel: [86196.161272] usb 2-1: USB disconnect,
> address 112
> Nov 7 17:59:07 mammatus kernel: [86196.401142] usb 2-1: new low speed
> USB device using uhci_hcd and address 113
> Nov 7 17:59:08 mammatus kernel: [86196.577674] usb 2-1: configuration
> #1 chosen from 1 choice
> Nov 7 17:59:08 mammatus kernel: [86196.593834] input: Logitech USB-PS/2
> Optical Mouse as /class/input/input597
> Nov 7 17:59:08 mammatus kernel: [86196.593939] input: USB HID v1.10
> Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1
> Nov 7 17:59:13 mammatus kernel: [86202.206449] usb 2-1: USB disconnect,
> address 113
> Nov 7 17:59:13 mammatus kernel: [86202.446319] usb 2-1: new low speed
> USB device using uhci_hcd and address 114
> Nov 7 17:59:14 mammatus kernel: [86202.623309] usb 2-1: configuration
> #1 chosen from 1 choice
> Nov 7 17:59:14 mammatus kernel: [86202.638402] input: Logitech USB-PS/2
> Optical Mouse as /class/input/input598
> Nov 7 17:59:14 mammatus kernel: [86202.638493] input: USB HID v1.10
> Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1
>
> There are some occasionnal connect/disconnect due to the fact that we
> recently bought an ergonomic mouse (Evoluent Vertical Mouse 3 Rev. 2)
> that some people plug-in the workstation they are working for the
> duration of their day/night shift... but nothing like 600 disconnect /
> day / workstations? And actually, the source workstation of this log as
> not yet got the mouse connected to it since it's last reboot.
>
> Looking at the changes between 2.6.20.6 and 2.6.20.10 I only found this
> USB related:
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.22.y.git;a=co
> mmit;h=0e22438a5adfdf32b3bb1c75c81c01a29fba9770
>
> I'm presuming that maybie eventually it might hit a input max barrier
> (like a max of 1024) and then the kernel would be crashing?
>
> Help very much appreciated!
People are going to want to know if this is still happening in 2.6.23
or 2.6.24-rc2, please.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists