mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Fr?d?ric L. W. Meunier" <2@pervalidus.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What causes "USB disconnect" ?
Date: Tue, 7 Feb 2006 08:39:21 -0800	[thread overview]
Message-ID: <20060207163921.GA10739@kroah.com> (raw)
In-Reply-To: <964857280602061812m748d19bew5ef0777e24359029@mail.gmail.com>

On Tue, Feb 07, 2006 at 12:12:58AM -0200, Fr?d?ric L. W. Meunier wrote:
> On 2/6/06, Fr?d?ric L. W. Meunier wrote:
> > When it happened, his lights turned off. I pressed a button, but
> > nothing happened. Then, I ignored it and it returned after the minutes
> > you see from the log.
> 
> It happened again. This, after an uptime of 3 days and a few hours.
> 
> Feb  6 23:59:00 pervalidus kernel: usb 1-2: USB disconnect, address 5
> Feb  6 23:59:39 pervalidus kernel: usb 1-2: new low speed USB device
> using uhci_hcd and address 6
> Feb  6 23:59:40 pervalidus kernel: usb 1-2: configuration #1 chosen
> from 1 choice
> Feb  6 23:59:44 pervalidus kernel: input: Logitech Inc. WingMan
> RumblePad as /class/input/input5
> Feb  6 23:59:44 pervalidus kernel: input: USB HID v1.10 Joystick
> [Logitech Inc. WingMan RumblePad] on usb-0000:00:10.0-2
> Feb  6 23:59:44 pervalidus kernel: usb 1-2: USB disconnect, address 6
> Feb  6 23:59:47 pervalidus kernel: usb 1-2: new low speed USB device
> using uhci_hcd and address 7
> Feb  6 23:59:47 pervalidus kernel: usb 1-2: configuration #1 chosen
> from 1 choice
> Feb  6 23:59:57 pervalidus kernel:
> /usr/local/src/kernel/linux-2.6.16/drivers/usb/input/hid-core.c:
> timeout initializing reports
> Feb  6 23:59:57 pervalidus kernel: input: Logitech Inc. WingMan
> RumblePad as /class/input/input6
> Feb  6 23:59:57 pervalidus kernel: input: USB HID v1.10 Joystick
> [Logitech Inc. WingMan RumblePad] on usb-0000:00:10.0-2
> 
> I changed it to other 2 ports and only see a
> 
> Feb  7 00:09:10 pervalidus kernel: usb 1-2: USB disconnect, address 7
> 
> Any way to know if this is the device's fault ?

I've never seen it to be anything but the device's fault, as it's pretty
much impossible for the kernel to disconnect a device like this from the
bus without specifically sending a command to do so (and that didn't
happen here.)

So I'd blame your device :)

thanks,

greg k-h

      parent reply	other threads:[~2006-02-07 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  0:15 Frédéric L. W. Meunier
2006-02-07  0:27 ` Greg KH
2006-02-07  1:06   ` Frédéric L. W. Meunier
2006-02-07  2:12     ` Frédéric L. W. Meunier
2006-02-07  2:18       ` Joshua Kugler
2006-02-07  2:50         ` Frédéric L. W. Meunier
2006-02-07 16:39       ` Greg KH [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=20060207163921.GA10739@kroah.com \
    --to=greg@kroah.com \
    --cc=2@pervalidus.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome