logitech attack 3 joystick causes boot delay

[David Tombs]

When I have my Logitech Attack 3 USB joystick plugged in, it causes a ~10s delay in an otherwise-speedy boot. I have experienced this bug at least since Intrepid.

I've attached dmesg with the joystick unplugged and with it plugged in. The apport info was collected with it plugged in.

Relevant lines of dmesg-plugged.txt are:

[ 13.477165] usbcore: registered new interface driver spca561
[ 13.477183] spca561: registered
[ 22.120050] /build/buildd/linux-2.6.28/drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed
[ 22.120061] generic-usb 0003:046D:C214.0002: timeout initializing reports
[ 22.120182] input: Logitech Logitech Attack 3 as /devices/pci0000:00/0000:00:02.0/usb2/2-9/2-9:1.0/input/input6
[ 22.128662] generic-usb 0003:046D:C214.0002: input,hidraw1: USB HID v1.10 Joystick [Logitech Logitech Attack 3] on usb-0000:00:02.0-9/input0
[ 22.128686] usbcore: registered new interface driver usbhid
[ 22.128702] usbhid: v2.6:USB HID core driver
[ 22.246241] lp0: using parport0 (interrupt-driven).

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=4654b040-659b-4861-9aa0-cef295981b15
MachineType:

NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-15-generic 2.6.28-15.49
ProcCmdLine: root=UUID=cb832714-a26f-4f20-a85f-de2b92164bcb ro splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.49-generic
SourcePackage: linux

[David Tombs (dgtombs)]

Forgot to mention, also experienced bug with my old x86 install.

[David Tombs (dgtombs)]

Same behavior, with same dmesg lines, in mainline kernel 2.6.28-02062810-generic.

[Leann Ogasawara (leannogasawara)]

Hi David,

Care to also test with the latest Karmic 9.10 Alpha release? It contains a much newer 2.6.31 based kernel. If you wait about a day or two the latest Alpha 6 images will be released - http://cdimage.ubuntu.com/releases/karmic/ . Thanks in advance.

[David Tombs (dgtombs)]

Hi Leann,

The problem is still present in Karmic Alpha 6. I've attached the dmesg from a Live CD boot. Thanks!

[David Tombs (dgtombs)]

Changed status back to new because I provided what was asked and didn't want it to expire. Hope it's not a problem!

[Jeremy Foshee (jeremyfoshee)]

Hi David,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 430164

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[David Tombs (dgtombs)]

Yep, can still reproduce in Karmic final and Lucid Alpha 3. Here's the dmesg from Lucid.

Note that the boot seems parallel (upstart I guess?) so the full 10s aren't wasted, but you can see a 10s delay from

[ 3.399091] usb 2-8: configuration #1 chosen from 1 choice

to

[ 13.937045] /build/buildd/linux-2.6.32/drivers/hid/usbhid/hid-core.c: usb_sub
mit_urb(ctrl) failed

It just has stuff going on in between now. It looks like it causes an effective delay of about 5s now.

[David Tombs (dgtombs)]

Changing back to new since I provided requested info.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.