Ubuntu

Upgraded Gusty->Hardy: No USB Devices (mouse, external HD, Ipod)

Asked by rodoyle

I recently upgraded from Ubuntu (amd64 version) Gusty Gibbon (7.10) to Hardy Heron (8.04) on my laptop. All my devices worked fine under Gusty, but now under Hardy all my usb devices stop working AFTER I LOG IN. To clarify, everything works fine until about half way between entering my password and the gnome desktop appears. Any suggestions would be greatly appreciated.

To try and figure out the source of the problem, I've done a few experiments:

When I start just a terminal, lsusb returns all my devices as it should. My external HS mounts and is read and writable. Once the desktop loads and everything stops working lsusb runs very slowly, but eventually returns that only my mouse is recognized.

I entered dmesg into the terminal to what was going on, and recieved the following output:

rodoyle@rodoyle-laptop:$ dmesg|grep usb
[ 242.373365] usb 3-1: new high speed USB device using ehci_hcd and address 5
[ 250.655555] usb 3-1: device not accepting address 5, error -110
[ 250.705290] usb 3-1: new high speed USB device using ehci_hcd and address 6
[ 263.433882] usb 3-1: device not accepting address 6, error -110
[ 263.546182] usb 3-1: new high speed USB device using ehci_hcd and address 7
[ 273.826518] usb 3-1: device not accepting address 7, error -110
[ 273.946031] usb 3-1: new high speed USB device using ehci_hcd and address 8
[ 284.092649] usb 3-1: device not accepting address 8, error -110
[ 284.092688] usb 3-3: USB disconnect, address 3
[ 284.236518] usb 3-3: new high speed USB device using ehci_hcd and address 9
[ 299.230923] usb 3-3: device not accepting address 9, error -110
[ 299.354832] usb 3-3: new high speed USB device using ehci_hcd and address 10
[ 312.732137] usb 3-3: device not accepting address 10, error -110
[ 312.782795] usb 3-3: new high speed USB device using ehci_hcd and address 11
[ 319.201860] usb 3-3: device not accepting address 11, error -110
[ 319.255041] usb 3-3: new high speed USB device using ehci_hcd and address 12
[ 328.936420] usb 3-3: device not accepting address 12, error -110
[ 353.997329] usb 3-3: new high speed USB device using ehci_hcd and address 14
[ 368.645358] usb 3-3: device not accepting address 14, error -110
[ 368.744822] usb 3-3: new high speed USB device using ehci_hcd and address 15
[ 377.244074] usb 3-3: device not accepting address 15, error -110
[ 377.355981] usb 3-3: new high speed USB device using ehci_hcd and address 16
[ 385.657694] usb 3-3: device not accepting address 16, error -110
[ 385.707431] usb 3-3: new high speed USB device using ehci_hcd and address 17

Here is an interesting section of the un-grepped output of dmesg from a different start up:
[ 94.304981] irq 11: nobody cared (try booting with the "irqpoll" option)
[ 94.304990] Pid: 0, comm: swapper Tainted: P 2.6.24-16-generic #1
[ 94.304992]
[ 94.304993] Call Trace:
[ 94.304995] <IRQ> [<ffffffff8027ad8e>] __report_bad_irq+0x1e/0x80
[ 94.305041] [<ffffffff8027b09d>] note_interrupt+0x2ad/0x2e0
[ 94.305052] [<ffffffff8027be53>] handle_level_irq+0xb3/0x120
[ 94.305061] [<ffffffff8020ef6b>] do_IRQ+0x7b/0x100
[ 94.305067] [<ffffffff8020c891>] ret_from_intr+0x0/0xa
[ 94.305083] [<ffffffff8027a079>] handle_IRQ_event+0x19/0x70
[ 94.305095] [<ffffffff8027be3b>] handle_level_irq+0x9b/0x120
[ 94.305103] [<ffffffff8020ef6b>] do_IRQ+0x7b/0x100
[ 94.305108] [<ffffffff8020c891>] ret_from_intr+0x0/0xa
[ 94.305111] <EOI> [<ffffffff8802e6f3>] :processor:acpi_idle_enter_simple+0x162/0x1cb
[ 94.305143] [<ffffffff8802e6e9>] :processor:acpi_idle_enter_simple+0x158/0x1cb
[ 94.305149] [<ffffffff8020b390>] default_idle+0x0/0x40
[ 94.305155] [<ffffffff803d10a2>] cpuidle_idle_call+0xa2/0xe0
[ 94.305158] [<ffffffff8020b390>] default_idle+0x0/0x40
[ 94.305161] [<ffffffff803d1000>] cpuidle_idle_call+0x0/0xe0
[ 94.305164] [<ffffffff8020b43f>] cpu_idle+0x6f/0xc0
[ 94.305171] [<ffffffff805d6bb5>] start_kernel+0x2b5/0x340
[ 94.305178] [<ffffffff805d612e>] _sinittext+0x12e/0x140
[ 94.305187]
[ 94.305188] handlers:
[ 94.305189] [<ffffffff88043300>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 94.305214] [<ffffffff88043300>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 94.305227] [<ffffffff88043300>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 94.305239] [<ffffffff8810ee70>] (ohci_irq_handler+0x0/0x910 [ohci1394])
[ 94.305247] [<ffffffff88451940>] (yenta_interrupt+0x0/0xc0 [yenta_socket])
[ 94.305255] Disabling IRQ #11
[ 94.307868] ACPI: EC: missing confirmations, switch off interrupt mode. <- A clue?
[ 94.308483] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 102.292857] usb 3-1: reset high speed USB device using ehci_hcd and address 2
[ 113.635803] usb 3-1: device not accepting address 2, error -110
[ 113.685538] usb 3-1: reset high speed USB device using ehci_hcd and address 2
[ 123.757156] usb 3-1: device not accepting address 2, error -110
[ 123.806898] usb 3-1: reset high speed USB device using ehci_hcd and address 2
[ 128.438908] usb 3-1: device not accepting address 2, error -110
[ 128.488642] usb 3-1: reset high speed USB device using ehci_hcd and address 2

I have read a few posts, but most people have not been able to resolve this issue sufficiently (if you find one I should check out please link me).

THINGS KNOWN:
* It is not a device issue. All devices work on other machines (windows and ubuntu). Every usb device I have tried does not work on my computer.

* It is unlikely a hardware issue with the usbhost. All devices are properly recognized when only a terminal is run and worked great under Gustry. Other devices such as my keyboard and touchpad work fine as well.

* Resetting the xorg.conf file does not resolve the issue (this was a theory based on the mouse not working). It does seem to slightly delay the onset of the problem by 1 minute.

Based on the dmesg output posted above I feel that there is some error in addressing in how the desktop manages usb devices.

I am totally stuck on this one. Any help would be greatly appreciated. If you need any more info, just let me know.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
rodoyle
Solved:
Last query:
Last reply:
Revision history for this message
John Rose (johnaaronrose) said : 		#1

Known problem in Hardy & Gutsy (broken over a month ago) on laptops. I have added to existing bug reports (e.g. 196288 & 222588 in Launchpad). I suggest you add your comments to these. I've also tried the irc channel to see if the developers have a solution, with no success. I regard this as very important as it will put newbies off Ubuntu.

Revision history for this message
rodoyle (riley-o-doyle) said : 		#2

I was able to solve the problem by removing the 'noapic' boot option from the GRUB loader. All my USB devices work fine now. Based on what I have read both here and elsewhere, this I have the following theory:

When upgrading from Gusty to Hardy, and likely when doing any distro upgrade, it is very important that you return your computer to its 'default state' as much as possible. This mean you need to remove all those little tweaks that were required under the old distro to get things working properly. Only then should you proceed with the upgrade, and if the problems are still present, then re-apply those modifications. Essentially, you must give the defaults a chance to work.

Revision history for this message
John Rose (johnaaronrose) said : 		#3

rodoyle,

Do you mean the noapic option that can be set in the kernel or defoptions lines of the /boot/grub/menu.lst file? If so, then it wouldn't make any difference to my setup. On the kernel line, I only have ro, quiet & splash in addition to the kernel details. I have no defoptions line.

Revision history for this message
rodoyle (riley-o-doyle) said : 		#4

After I tried it out by manually removing noapic during boot, I made the change in the defoptions lines so it would be the default boot option. It is important to note that I was undoing a change I made when I installed Gusty. Based on what your settings are, this same technique unfortunately would be not an applicable solution.

Revision history for this message
MT (micdhack) said : 		#5

I have the same problem now with 8.10...
No usb device that will be plug on the system works..with older kernel i dont have this problem

Revision history for this message
hoctro0104 (hoctro0104) said : 		#6

I have the same problem.
this comes from the kernel or what ?

Revision history for this message
Mike (kincanonmi) said : 		#7

I'm new to Ubantu and upgraded to 8.1 not to long ago on a laptop and seldom us external USB devices. Yesterday when I plugged in my USB HD it showed up in computer but could not be mounted. I than tried a thumb drive with the same results. Both devices are formated as FAT32. I have a second drive that is NTFS but I haven't tried to read it yet.

I assume this is the same problem that you're discussing above? If so I would like to keep tabs of what the solution is because I'd like to access information on my UAB HD to do my taxes next month. Until then I'm sort of dead in the water.