From: Joshua Kugler <joshua.kugler@uaf.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: What causes "USB disconnect" ?
Date: Mon, 6 Feb 2006 17:18:08 -0900 [thread overview]
Message-ID: <200602061718.08473.joshua.kugler@uaf.edu> (raw)
In-Reply-To: <964857280602061812m748d19bew5ef0777e24359029@mail.gmail.com>
On Monday 06 February 2006 17:12, 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 just saw this behavior on a USB keyboard/mouse combo the other day when I
touched the case and discharged static electricity. Nothing else was
affected, but I saw the keyboard and mouse disconnect and then immediately
reconnect. Possibly an intolerant chipset or poorly grounded motherboard?
j----- k-----
--
Joshua Kugler PGP Key: http://pgp.mit.edu/
CDE System Administrator ID 0xDB26D7CE
http://distance.uaf.edu/
next prev parent reply other threads:[~2006-02-07 2:18 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 [this message]
2006-02-07 2:50 ` Frédéric L. W. Meunier
2006-02-07 16:39 ` Greg KH
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=200602061718.08473.joshua.kugler@uaf.edu \
--to=joshua.kugler@uaf.edu \
--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
all inboxes | Powered by JetHome®