I never got this messages since I started using 2.6. Today I
got it in 2.6.16-rc2. Is this a problem in this version ? How
to determine ? I wasn't using the device.
Feb 6 20:49:48 pervalidus kernel: usb 1-2: USB disconnect, address 4
Feb 6 21:01:03 pervalidus kernel: usb 1-2: new low speed USB device using uhci_hcd and address 5
Feb 6 21:01:03 pervalidus kernel: usb 1-2: configuration #1 chosen from 1 choice
Feb 6 21:01:13 pervalidus kernel: /usr/local/src/kernel/linux-2.6.16/drivers/usb/input/hid-core.c: timeout initializing reports
Feb 6 21:01:13 pervalidus kernel: input: Logitech Inc. WingMan RumblePad as /class/input/input4
Feb 6 21:01:13 pervalidus kernel: input: USB HID v1.10 Joystick [Logitech Inc. WingMan RumblePad] on usb-0000:00:10.0-2
--
How to contact me - http://www.pervalidus.net/contact.html
On Mon, Feb 06, 2006 at 10:15:11PM -0200, Fr?d?ric L. W. Meunier wrote:
> I never got this messages since I started using 2.6. Today I
> got it in 2.6.16-rc2. Is this a problem in this version ? How
> to determine ? I wasn't using the device.
>
> Feb 6 20:49:48 pervalidus kernel: usb 1-2: USB disconnect, address 4
The device went away.
> Feb 6 21:01:03 pervalidus kernel: usb 1-2: new low speed USB device using uhci_hcd and address 5
10 minutes later it came back.
Did you bump the cable?
It it still working ok?
Did it go into "suspend" mode and just power down, and then later come
back when you touch it (like a mouse)?
thanks,
greg k-h
On 2/6/06, Greg KH wrote:
> On Mon, Feb 06, 2006 at 10:15:11PM -0200, Fr?d?ric L. W. Meunier wrote:
> > I never got this messages since I started using 2.6. Today I
> > got it in 2.6.16-rc2. Is this a problem in this version ? How
> > to determine ? I wasn't using the device.
> >
> > Feb 6 20:49:48 pervalidus kernel: usb 1-2: USB disconnect, address 4
>
> The device went away.
>
> > Feb 6 21:01:03 pervalidus kernel: usb 1-2: new low speed USB device using uhci_hcd and address 5
>
> 10 minutes later it came back.
>
> Did you bump the cable?
No.
> It it still working ok?
I think so. I don't do any gaming actually, but tested with jstest and
all buttons are working.
> Did it go into "suspend" mode and just power down, and then later come
> back when you touch it (like a mouse)?
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.
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 ?
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/
On Mon, 6 Feb 2006, Joshua Kugler wrote:
> 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.
I think it just died. I also have an USB mouse which is working
fine, but I rebooted under 2.6.15 to see if the gamepad would
return to live and it didn't.
About the motherboard, it's an ECS K7VTA 5.0 which I bought
almost 3 years ago. Poorly grounded, probably, but not worse
than it was before.
--
How to contact me - http://www.pervalidus.net/contact.html
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