[Karmic] USB device not recognized or automounted at boot-up

[dailyglen]

Binary package hint: linux-image-2.6.31-11-generic

Hi,

When booting into Karmic my Blutooth USB dongle and USB to PS2 keyboard adapter are not recognized until I unplug them and plug them back in. In my dmesg (see attachment for the full version) I get error messages like:

[ 3.028029] usb 7-1: new full speed USB device using uhci_hcd and address 2
[ 3.148023] usb 7-1: device descriptor read/64, error -71
[ 3.372524] usb 7-1: device descriptor read/64, error -71
[ 3.588019] usb 7-1: new full speed USB device using uhci_hcd and address 3
[ 3.708018] usb 7-1: device descriptor read/64, error -71
[ 3.936027] usb 7-1: device descriptor read/64, error -71
[ 4.153513] usb 7-1: new full speed USB device using uhci_hcd and address 4
[ 4.564074] usb 7-1: device not accepting address 4, error -71
[ 4.676023] usb 7-1: new full speed USB device using uhci_hcd and address 5
[ 5.088023] usb 7-1: device not accepting address 5, error -71
[ 5.088042] hub 7-0:1.0: unable to enumerate USB device on port 1

My USB mouse and USB sound card are correctly identified on boot-up. Everything works fine in 9.04 so this seems like a regression.

Here is my lsusb after replugging the devices in:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 046d:c216 Logitech, Inc. Dual Action Gamepad
Bus 001 Device 006: ID 08bb:2704 Texas Instruments Japan
Bus 001 Device 005: ID 06b4:1c70
Bus 001 Device 003: ID 0424:a700 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 0e8f:0020 GreenAsia Inc.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 034: ID 0c10:0000
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

And full dmesg is attached.

Let me know if I can test anything out.

Thanks.

ProblemType: Bug
Architecture: i386
Date: Wed Oct 7 01:02:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/upstart-udev-bridge
Package: upstart 0.6.3-7
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: upstart
Uname: Linux 2.6.31-11-generic i686

[dailyglen (dailyglen)]

Hi,

I tracked down the issue with "git bisect" to this commit:

Quote:
diff --git a/drivers/input/input.c b/drivers/input/input.c
index 913392f..a79c833 100644 (file)
--- a/drivers/input/input.c
+++ b/drivers/input/input.c
@@ -1551,7 +1551,6 @@ int input_register_handle(struct input_handle *handle)
return error;
list_add_tail_rcu(&handle->d_node, &dev->h_list);
mutex_unlock(&dev->mutex);
- synchronize_rcu();

/*
* Since we are supposed to be called from ->connect()

If I put "synchronize_rcu();" back into drivers/input/input.c and recompile the kernel then it works for me.

I'm currently working with the kernel developers so they can get a high quality fix. It seems that this synchronize_rcu() is a catch all and some other part of the system is missing the call. While reverting the above patch works it is not optimal because it slows down boot-up.

It seems that there are quite a few people on the forums having issues with USB devices not being recognized.

Thanks.

[Sarraceno (jfhtomas)]

Hi!

I also have this kind of issue with a usb serial (LINDY USB-SERIAL PN 42856).

Syslog lines after connecting:
Nov 5 12:23:06 ptjtomasub kernel: [ 2544.120036] usb 3-2: new full speed USB device using uhci_hcd and address 38
Nov 5 12:23:06 ptjtomasub kernel: [ 2544.244030] usb 3-2: device descriptor read/64, error -71
Nov 5 12:23:06 ptjtomasub kernel: [ 2544.472027] usb 3-2: device descriptor read/64, error -71
Nov 5 12:23:07 ptjtomasub kernel: [ 2544.688035] usb 3-2: new full speed USB device using uhci_hcd and address 39
Nov 5 12:23:07 ptjtomasub kernel: [ 2544.812027] usb 3-2: device descriptor read/64, error -71
Nov 5 12:23:07 ptjtomasub kernel: [ 2545.040032] usb 3-2: device descriptor read/64, error -71
Nov 5 12:23:07 ptjtomasub kernel: [ 2545.256034] usb 3-2: new full speed USB device using uhci_hcd and address 40
Nov 5 12:23:08 ptjtomasub kernel: [ 2545.672027] usb 3-2: device not accepting address 40, error -71
Nov 5 12:23:08 ptjtomasub kernel: [ 2545.784026] usb 3-2: new full speed USB device using uhci_hcd and address 41
Nov 5 12:23:08 ptjtomasub kernel: [ 2546.200032] usb 3-2: device not accepting address 41, error -71
Nov 5 12:23:08 ptjtomasub kernel: [ 2546.200054] hub 3-0:1.0: unable to enumerate USB device on port 2

lsusb comand doesn't shows any new device.
I'm running 2.6.31-14-generic #48-Ubuntu SMP

[Peterson Silva (petersonsilva)]

@dailyglen, will there be a fix for this soon-to-be-released on karmic?

[dailyglen (dailyglen)]

@Spaceport, no clue. I'm just a user. I don't know if this will ever be fixed. I guess the more people who have this problem the more likely it will be fixed.

[Peterson Silva (petersonsilva)]

Strange as it is, today it was fixed for me. The printer I could not connect (lsusb would freeze If I plugged it in) now is working perfectly =S

[Boots Whitlock (boots-whitlock)]

This has been happening to me as well. A very ODD intermittent USB problem. Please refer to the following posts in forums:

http://ubuntuforums.org/showthread.php?t=1384743&highlight=boots+Bus+001+Device+004%3A+5986%3A0203+Acer%2C&page=2

Boots

[dailyglen (dailyglen)]

@spaceport: for me the problem doesn't happen all the time.

[-- (jims-account)]

While almost none of them work, most of the USB devices are plugged in, but I try to plug in a USB headset and my system becomes very unstable.

This was not an issue with Ubuntu 9.04.

2.6.31-20-generic

lspci
00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor (rev a2)
00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1)
00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:09.0 RAID bus controller: nVidia Corporation MCP78S [GeForce 8200] SATA Controller (RAID mode) (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP77 Ethernet (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:13.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:14.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
01:05.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70)
02:00.0 VGA compatible controller: nVidia Corporation C77 [GeForce 8200] (rev a2)
03:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GT] (rev a2)
06:00.0 Communication controller: Conexant Systems, Inc. Device 2f82

lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 03f0:2b11 Hewlett-Packard PSC 2170 series
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 046d:08c1 Logitech, Inc. QuickCam Fusion
Bus 002 Device 003: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

After plugging Logitech USB headse...

[Jeremy Foshee (jeremyfoshee)]

Hi dailyglen,

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 445160

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.]

[Marty Vowles (mvowles311)]

I still have a problem with this in Lucid. When I had compiled the .33 kernel in Karmic with the change above everything was dandy but with the fresh Lucid install I've got the issue again. Here's some data:

[Marty Vowles (mvowles311)]

Or not, though I could use apport-collect as well. The only information that concerns me is with respect to IRQs:
cat /proc/interrupts
           CPU0 CPU1 CPU2
  0: 47 0 3 IO-APIC-edge timer
  1: 0 1 530 IO-APIC-edge i8042
  4: 0 0 2 IO-APIC-edge
  6: 0 6 1462 IO-APIC-edge floppy
  7: 1 0 0 IO-APIC-edge parport0
  8: 0 0 1 IO-APIC-edge rtc0
  9: 0 0 0 IO-APIC-fasteoi acpi
 14: 0 7 7760 IO-APIC-edge pata_amd
 15: 0 0 0 IO-APIC-edge pata_amd
 20: 0 3732 1383 IO-APIC-fasteoi ohci_hcd:usb4, nvidia
 21: 0 252 63077 IO-APIC-fasteoi ohci_hcd:usb3, HDA Intel
 22: 0 0 2 IO-APIC-fasteoi ehci_hcd:usb2
 23: 0 0 3 IO-APIC-fasteoi ehci_hcd:usb1
 26: 0 15 12358 PCI-MSI-edge ahci
 27: 0 14 8680 PCI-MSI-edge eth0
NMI: 0 0 0 Non-maskable interrupts
LOC: 40966 15159 10882 Local timer interrupts
SPU: 0 0 0 Spurious interrupts
PMI: 0 0 0 Performance monitoring interrupts
PND: 0 0 0 Performance pending work
RES: 112031 75992 52409 Rescheduling interrupts
CAL: 956 168 1072 Function call interrupts
TLB: 518 439 395 TLB shootdowns
TRM: 0 0 0 Thermal event interrupts
THR: 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 Machine check exceptions
MCP: 2 2 2 Machine check polls
ERR: 1
MIS: 0

Could the doubled-up interrupts cause problems?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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