mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: BUG: usb Mouse continual disconnect (2.6.22.10) leading to eventual crash?
Date: Wed, 7 Nov 2007 12:32:37 -0800	[thread overview]
Message-ID: <20071107123237.d318cdbf.akpm@linux-foundation.org> (raw)
In-Reply-To: <F1D642E5A91BC94D9504EC83AE19E6B0B89760@ecqcmtlmail3.quebec.int.ec.gc.ca>

(+linux-usb-devel)

> On Wed, 7 Nov 2007 13:19:47 -0500 "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.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.

  reply	other threads:[~2007-11-07 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 18:19 Fortier,Vincent [Montreal]
2007-11-07 20:32 ` Andrew Morton [this message]
2007-11-07 22:13   ` Fortier,Vincent [Montreal]
2007-11-08 15:04     ` [linux-usb-devel] " Alan Stern

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=20071107123237.d318cdbf.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Vincent.Fortier1@EC.GC.CA \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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®