usb ports randomly shut off Jaunty beta (SOLVED)

Bug #350065 reported by Chem. Imbalance
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

{SOLVED--see below}
On Jaunty beta (and previous alphas) I notice that my mouse stops responding after a seemingly random amount of time. All the usb ports it turns out shut off--I've tried plugging various devices in all ports after the mouse stops responding and they are all without power. (edit:) However, all the devices still work except for the mouse until you replug them in--then they have no power.

Intrepid works perfectly on this machine with this bug never occuring before except in the Jaunty alphas and beta.

Also, all my usb ports (according to my mobo manual) should be USB 2.0 compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0. My motherboard is an Asus M3N78-Pro.

I'm using the latest nVidia driver from Jaunty--180.44

NOTE: the following attachments/terminal outputs are before the issue occurs (since my mouse doesn't work when the bug happens).
(EDIT): I have attached my lsusb and dmesg out put also AFTER the bug occurs.
--------------------------------------
uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64 GNU/Linux
--------------------------------------
Jaunty beta
--------------------------------------
lscpi:

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:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)
00:07.0 Audio device: nVidia Corporation MCP78S [GeForce 8200] High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:09.0 SATA controller: nVidia Corporation MCP78S [GeForce 8200] AHCI Controller (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200] 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] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control
02:00.0 VGA compatible controller: nVidia Corporation GeForce 8300 (rev a2)
---------------------------------------------
lsusb:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 045e:00dd Microsoft Corp.
Bus 004 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 003 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt Wheel
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
--------------------------------------------

SOLUTION:
Here are my /proc/interrupts and my lsusb:

[code]cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3
  0: 102 0 0 3 IO-APIC-edge timer
  1: 0 0 0 2 IO-APIC-edge i8042
  4: 0 0 0 1 IO-APIC-edge
  7: 1 0 0 0 IO-APIC-edge
  8: 0 0 0 1 IO-APIC-edge rtc0
  9: 0 0 0 0 IO-APIC-fasteoi acpi
 12: 0 0 0 4 IO-APIC-edge i8042
 14: 0 0 2 3582 IO-APIC-edge pata_amd
 15: 0 0 0 0 IO-APIC-edge pata_amd
 19: 0 0 0 3 IO-APIC-fasteoi ohci1394
 20: 0 0 0 477 IO-APIC-fasteoi ohci_hcd:usb3, nvidia
 21: 0 0 1 1660 IO-APIC-fasteoi ehci_hcd:usb2, HDA Intel
 22: 0 0 0 1 IO-APIC-fasteoi ehci_hcd:usb1
 23: 0 0 11 7448 IO-APIC-fasteoi ohci_hcd:usb4
2298: 0 0 58 50716 PCI-MSI-edge eth0
2299: 0 0 16 7431 PCI-MSI-edge ahci
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 22949 13508 10719 30490 Local timer interrupts
RES: 14107 7407 9277 7849 Rescheduling interrupts
CAL: 156 180 173 49 Function call interrupts
TLB: 1146 877 877 881 TLB shootdowns
SPU: 0 0 0 0 Spurious interrupts
ERR: 1
MIS: 0
[/code]

[code]lsusb
Bus 002 Device 004: ID 05ac:021d Apple, Inc.
Bus 002 Device 002: ID 05ac:1005 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt Wheel
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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
[/code]

Notice that nvidia is sharing an irq with my usb hub # 3.

I had my mouse plugged into usb hub 3 and I had freezing.
I simply moved my mouse to hub 4 and no more freezing.

It seems it is an irq problem for me.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Since this bug report, I have experienced recurrences of this bug at least six times as of April 1, 09.

Fully updated too.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Also I have noticed that when this bug occurs, the keyboard still works until you replug it in--at which time it receives no power. All deviced plugged into usb ports when the mouse stops responding still receive power unless they are unplugged and then plugged back in--then they don't receive any power.
The mouse seems to be the only device that doesn't respond at all.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :
description: updated
description: updated
tags: added: mouse
description: updated
Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Here is my dmesg and lsusb output after the bug occurs

description: updated
Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :
Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Well a strange thing just happened...
After about 25 occurrences of this bug only affecting my mouse, it just happened to my keyboard and not my mouse.

Since my keyboard wasn't working, I was able to go into Sys., Admin.,Log File Viewer and paste the following output of kern.log:

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Could this be the problem?
Apr 6 17:19:29 CUbNix kernel: [ 725.073540] usb 4-1: reset low speed USB device using ohci_hcd and address 2
Apr 6 17:19:32 CUbNix kernel: [ 728.553535] usb 4-1: reset low speed USB device using ohci_hcd and address 2
Apr 6 17:19:34 CUbNix kernel: [ 730.385532] usb 4-1: reset low speed USB device using ohci_hcd and address 2
Apr 6 17:19:35 CUbNix kernel: [ 730.717539] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:35 CUbNix kernel: [ 731.149539] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:35 CUbNix kernel: [ 731.577544] usb 4-1: reset low speed USB device using ohci_hcd and address 2
Apr 6 17:19:36 CUbNix kernel: [ 731.909537] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:36 CUbNix kernel: [ 732.340126] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:37 CUbNix kernel: [ 732.769548] usb 4-1: reset low speed USB device using ohci_hcd and address 2
Apr 6 17:19:37 CUbNix kernel: [ 733.177531] usb 4-1: device not accepting address 2, error -62
Apr 6 17:19:37 CUbNix kernel: [ 733.500564] usb 4-1: reset low speed USB device using ohci_hcd and address 2
Apr 6 17:19:38 CUbNix kernel: [ 733.909635] usb 4-1: device not accepting address 2, error -62
Apr 6 17:19:38 CUbNix kernel: [ 733.909726] usb 4-1: USB disconnect, address 2
Apr 6 17:19:38 CUbNix kernel: [ 734.141553] usb 4-1: new low speed USB device using ohci_hcd and address 3
Apr 6 17:19:38 CUbNix kernel: [ 734.325525] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:38 CUbNix kernel: [ 734.612040] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:39 CUbNix kernel: [ 734.892036] usb 4-1: new low speed USB device using ohci_hcd and address 4
Apr 6 17:19:39 CUbNix kernel: [ 735.081058] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:39 CUbNix kernel: [ 735.368276] usb 4-1: device descriptor read/64, error -62
Apr 6 17:19:40 CUbNix kernel: [ 735.649002] usb 4-1: new low speed USB device using ohci_hcd and address 5
Apr 6 17:19:40 CUbNix kernel: [ 736.057516] usb 4-1: device not accepting address 5, error -62
Apr 6 17:19:40 CUbNix kernel: [ 736.233532] usb 4-1: new low speed USB device using ohci_hcd and address 6
Apr 6 17:19:40 CUbNix kernel: [ 736.640045] usb 4-1: device not accepting address 6, error -62
Apr 6 17:19:40 CUbNix kernel: [ 736.640083] hub 4-0:1.0: unable to enumerate USB device on port 1

Revision history for this message
Jacob Harrison (fictional-truth) wrote :

Having the same issue, but my lsusb hangs after the mouse stops working.

It seems random, but it's never happened while the system was idle. I've noticed it stop while watching full screen flash videos (ala hulu.com), playing Nexuiz, and consistantly when I try to open more than one pdf at a time.

Hope that helps.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Could this bug be related?
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355155

 It seems uninstalling the nvidia drivers solves this problem (so far).

Revision history for this message
/dev/null (arndt-stedler) wrote :

I have the same here on an ASRock K10N78FullHD-hSLI mainboard (nvidia 8200 chipset)
but furthermore sometimes my soundcard is just not responding.

I could make out the following:
USB (OHCI-part) and VGA 8200 share the same IRQ 21
    and
USB(EHCI-part) and audio ALC1200 (onBoard) share IRQ 22

It seems to be an IRQ-sharing problem (probably with USB?)
Taking the latest nvidia graphics drivers (180.51) make it happen less often, but it still happens.

By the way i am using an AMD X3-(8650) Processor and 4 GB RAM
 - /dev/null

Revision history for this message
/dev/null (arndt-stedler) wrote :
Download full text (5.1 KiB)

It happened again... here are the log-messages
(Even the screen freezes, i had to CTRL-ALT-DEL):

/var/log/messages;
May 9 20:57:08 phoenix -- MARK --
May 9 20:57:50 phoenix kernel: [15662.357624] usb 1-5: USB disconnect, address 3
May 9 20:58:19 phoenix bonobo-activation-server (arndt-9020): could not associate with desktop session: Failed to connect to socket /tmp/dbus-bVRrHeGdWb: Connection refused
May 9 20:58:36 phoenix kernel: [15708.786331] apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac)
May 9 20:58:36 phoenix kernel: [15708.786337] apm: disabled on user request.
May 9 20:58:41 phoenix exiting on signal 15

/var/kern.log
May 9 16:38:58 phoenix kernel: [ 129.972124] ppdev0: unregistered pardevice
May 9 20:57:50 phoenix kernel: [15662.357624] usb 1-5: USB disconnect, address 3
May 9 20:58:36 phoenix kernel: [15708.786331] apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac)
May 9 20:58:36 phoenix kernel: [15708.786337] apm: disabled on user request.

/var/log/syslog
May 9 20:17:01 phoenix /USR/SBIN/CRON[8843]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 9 20:19:54 phoenix dhclient: DHCPREQUEST of 192.168.11.102 on eth1 to 192.168.11.254 port 67
May 9 20:19:54 phoenix dhclient: DHCPACK of 192.168.11.102 from 192.168.11.254
May 9 20:19:54 phoenix dhclient: bound to 192.168.11.102 -- renewal in 3051 seconds.
May 9 20:37:08 phoenix -- MARK --
May 9 20:57:08 phoenix -- MARK --
May 9 20:57:50 phoenix kernel: [15662.357624] usb 1-5: USB disconnect, address 3
May 9 20:58:14 phoenix init: tty4 main process (5267) killed by TERM signal
May 9 20:58:14 phoenix init: tty5 main process (5268) killed by TERM signal
May 9 20:58:14 phoenix init: tty2 main process (5271) killed by TERM signal
May 9 20:58:14 phoenix init: tty3 main process (5274) killed by TERM signal
May 9 20:58:14 phoenix init: tty6 main process (5275) killed by TERM signal
May 9 20:58:14 phoenix init: tty1 main process (6872) killed by TERM signal
May 9 20:58:19 phoenix bonobo-activation-server (arndt-9020): could not associate with desktop session: Failed to connect t
o socket /tmp/dbus-bVRrHeGdWb: Connection refused
May 9 20:58:36 phoenix kernel: [15708.786331] apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac)
May 9 20:58:36 phoenix kernel: [15708.786337] apm: disabled on user request.
May 9 20:58:37 phoenix mysqld[5783]: 090509 20:58:37 [Note] /usr/sbin/mysqld: Normal shutdown
May 9 20:58:37 phoenix mysqld[5783]:
May 9 20:58:37 phoenix mysqld[5783]: 090509 20:58:37 InnoDB: Starting shutdown...
May 9 20:58:37 phoenix mysqld[5783]: 090509 20:58:37 InnoDB: Shutdown completed; log sequence number 0 43655
May 9 20:58:37 phoenix mysqld[5783]: 090509 20:58:37 [Note] /usr/sbin/mysqld: Shutdown complete
May 9 20:58:37 phoenix mysqld[5783]:
May 9 20:58:37 phoenix mysqld_safe[9202]: ended
May 9 20:58:40 phoenix bluetoothd[6598]: bridge pan0 removed
May 9 20:58:40 phoenix bluetoothd[6598]: Stopping SDP server
May 9 20:58:40 phoenix bluetoothd[6598]: Exit
May 9 20:58:40 phoenix avahi-daemon[5686]: Got SIGTERM, quitting.
May 9 20:58:40 phoenix avahi-daemon[5686]: Leaving mDNS multicast group on interface eth1.IPv4 wi...

Read more...

Revision history for this message
Jacob Harrison (fictional-truth) wrote :

This problem is exceedingly frustrating. It will be a non-issue for a month and then it's happened three times today. It does seem to happen only when the computer is under a large load, It never seems to happen at under 50% usage on both cores, most of the time when the usb stops working and I think to glance over at conky, it seems at least one core is above 90% usage (ram usage at around 750 megs - 1 gig). I've noticed that my lsusb no longer hangs after it happens, however it's spitting out the exact same information it does when the usb ports work.

I'm running Jaunty 64 bit, on an AMD x2, with 4gigs of ram and an Nvidia 7900gs (not sure if that helps any).

Revision history for this message
Chris Oliver (excid3) wrote :

I have been experiencing the same problem. Upgrading to the proposed kernel in Jaunty 32 bit did not have this happen for almost a month and then it has happened 3 times in the past 2 days. Also boot hangs on the bluetooth module occasionally which seems to happen on reboot after this had happened on the old kernel. It has only hung on bluetooth once since upgrading to the other kernel.

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote :
Download full text (12.6 KiB)

I have also been experiencing this problem since upgrading to Jaunty. My keyboard and mouse are attached through the same USB receiver. The mouse will stop responding, but the keyboard will continue to work. I did notice, however, that the multimedia keys on the keyboard no longer respond after the occurrence.

lsusb just hangs - it cannot be killed with Ctrl+C.

dmesg shows usb disconnect. Unplugging the device and plugging it back in will result in the keyboard being unresponsive as well. Connecting a new mouse is useless - the device does not receive power. However, connecting my mini USB bluetooth dongle does receive power and is recognized by the OS.

This issue occurs seemingly randomly and forces me to use a PS/2 mouse - incredibly frustrating.

Anyway, prepare for a buttload of information.

------------------------------------------------------------------------------

$ lsusb
Bus 004 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

------------------------------------------------------------------------------

$ lsusb -v
root@mikegerwitz-pc:/home/mikegerwitz# lsusb -v

Bus 004 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x046d Logitech, Inc.
  idProduct 0xc505 Cordless Mouse+Keyboard Receiver
  bcdDevice 17.11
  iManufacturer 1 Logitech
  iProduct 2 USB Receiver
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 59
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 98mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 1 Boot Interface Subclass
      bInterfaceProtocol 1 Keyboard
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.10
          bCountryCode 0 Not supported
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 63
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transf...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

Installing the 2.6.30 kernel from here http://kernel.ubuntu.com/~kernel-ppa/mainline/ fixes this problem for me so far.

Everyone here should give it a shot.

I've only been using it for a day, but so far it's working nicely.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.1 KiB)

hey great! i have since moved to debian for the time being to get some
actual stability :P its working great as well. i never went with fedora
because i love deb based distros so much better. let me know how it goes
after a week of usage but i think ill probably stick with the debian
squeeze/sid setup that i've got right now. thanks for the update!

On Fri, Jun 12, 2009 at 6:52 PM, Chem. Imbalance
<email address hidden>wrote:

> Installing the 2.6.30 kernel from here http://kernel.ubuntu.com/~kernel-
> ppa/mainline/ <http://kernel.ubuntu.com/%7Ekernel-%0Appa/mainline/> fixes
> this problem for me so far.
>
> Everyone here should give it a shot.
>
> I've only been using it for a day, but so far it's working nicely.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev
> a1)
> 0...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: usb ports randomly shut off Jaunty beta

2.6.30 is a no-go.

Started freezing yesterday.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (4.7 KiB)

Dang. I've been running Debian Lenny and it has been treating me very
nicely. Using 2.6.29 and the 180.44 nvidia driver with no issues so
far...but we shall see.

On Mon, Jun 15, 2009 at 5:35 PM, Chem. Imbalance
<email address hidden>wrote:

> 2.6.30 is a no-go.
>
> Started freezing yesterday.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev
> a1)
> 00:07.0 Audio device: nVidia Corporation MCP78S [GeForce 8200] High
> Definition Audio (rev a1)
> 00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge
> (rev a1)
> 00:09.0 SATA controller: nVidia Corporation MCP78S [GeForce 8200] AHCI
> Controller (rev a2)
> 00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200]
> Ethernet (rev a2)
> 00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200]...

Read more...

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote : Re: usb ports randomly shut off Jaunty beta

Most recent nVidia drivers (185.18.14) does not solve the issue.

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote :

I would also like to add that it seems the issue is recurring more often. I cannot go an hour without the problem. This is a very severe issue - I'm unable to use my Ubuntu box productively and find myself spending much of my time on my work-issued Windows PC, which lacks a vast majority of the tools I need more my development.

When using a KVM switch to switch between my work and home PCs, the mouse first goes, then the keyboard. When switching to the Windows PC, they're re-activated (re-powered). Switching back, no power. The USB mouse that was not connected to the KVM switch continues to operate properly. Previous to the KVM switch being installed, the USB mouse attached directly to the computer would have the same issue.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

@ Chris Oliver

I just moved to Debian Lenny today and what a breath of fresh air!

I compiled a version of 2.6.30 from the Debian source and all is going nicely.

I like Debian. I'm probably just gonna stay with it.

Btw, I'm using "Testing", the rolling release not "Squeeze".

Good luck to all.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.0 KiB)

@ Chemical Imbalance

Great! I'm glad to hear it. I'll no longer be using Ubuntu as I really just
need stability. I'm using a mix of Squeeze and Sid.

So if it's not the kernel and it's not the nvidia driver. What do you think
it might be?

On Tue, Jun 16, 2009 at 9:53 PM, Chem. Imbalance
<email address hidden>wrote:

> @ Chris Oliver
>
> I just moved to Debian Lenny today and what a breath of fresh air!
>
> I compiled a version of 2.6.30 from the Debian source and all is going
> nicely.
>
> I like Debian. I'm probably just gonna stay with it.
>
> Btw, I'm using "Testing", the rolling release not "Squeeze".
>
> Good luck to all.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev
> a1)
> 00:07.0 Audio device: nVidia Corporation MCP78S [GeForce 8200] High
> Definition Audio ...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: usb ports randomly shut off Jaunty beta

I don't know what it could be. Perhaps the ubuntu kernel has some buggy patches or untested features enabled?

I'm content on staying with Debian as well except for the "Stable vs. Unstable Conundrum".

Stable is old and even Testing is buggy. My gksu and nm-applet are broken in Testing.

I switched to wicd and still can't resolve the gksu issue.

How are things on your side?

What method are you using to backport Sid packages to Testing?

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.1 KiB)

I'll give you my sources.list in a bit that you can check out.
Everything seems to be working perfectly fine for me. I got the
repositories off a friend who is a big debian user. Using his sources
I haven't had a single problem (other than being on dialup :P )

On 6/17/09, Chem. Imbalance <email address hidden> wrote:
> I don't know what it could be. Perhaps the ubuntu kernel has some buggy
> patches or untested features enabled?
>
> I'm content on staying with Debian as well except for the "Stable vs.
> Unstable Conundrum".
>
> Stable is old and even Testing is buggy. My gksu and nm-applet are
> broken in Testing.
>
> I switched to wicd and still can't resolve the gksu issue.
>
> How are things on your side?
>
> What method are you using to backport Sid packages to Testing?
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops responding
> after a seemingly random amount of time. All the usb ports it turns out
> shut off--I've tried plugging various devices in all ports after the mouse
> stops responding and they are all without power. (edit:) However, all the
> devices still work except for the mouse until you replug them in--then they
> have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring before
> except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue occurs
> (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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:06.0 IDE interf...

Read more...

Revision history for this message
Chris Oliver (excid3) wrote :
Download full text (6.0 KiB)

So last night, I was using WinXP on my desktop that has been having
the issues...and all of a sudden it blue screened with a usbhub.sys
error. I wonder if it is an actual hardware issue.

Here is my sources.list:

deb http://mirror.peer1.net/debian/ testing main contrib non-free
deb http://mirror.peer1.net/debian/ unstable main contrib non-free
deb http://debian.dc-uoit.net/debian-multimedia testing main
deb http://security.debian.org/ testing/updates main contrib non-free
deb http://ftp.us.debian.org/debian lenny main contrib non-free
deb http://security.debian.org/ lenny/updates main contrib non-free

On 6/17/09, Chris Oliver <email address hidden> wrote:
> I'll give you my sources.list in a bit that you can check out.
> Everything seems to be working perfectly fine for me. I got the
> repositories off a friend who is a big debian user. Using his sources
> I haven't had a single problem (other than being on dialup :P )
>
> On 6/17/09, Chem. Imbalance <email address hidden> wrote:
>> I don't know what it could be. Perhaps the ubuntu kernel has some buggy
>> patches or untested features enabled?
>>
>> I'm content on staying with Debian as well except for the "Stable vs.
>> Unstable Conundrum".
>>
>> Stable is old and even Testing is buggy. My gksu and nm-applet are
>> broken in Testing.
>>
>> I switched to wicd and still can't resolve the gksu issue.
>>
>> How are things on your side?
>>
>> What method are you using to backport Sid packages to Testing?
>>
>> --
>> usb ports randomly shut off Jaunty beta
>> https://bugs.launchpad.net/bugs/350065
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in Ubuntu: New
>>
>> Bug description:
>> On Jaunty beta (and previous alphas) I notice that my mouse stops
>> responding
>> after a seemingly random amount of time. All the usb ports it turns out
>> shut off--I've tried plugging various devices in all ports after the
>> mouse
>> stops responding and they are all without power. (edit:) However, all
>> the
>> devices still work except for the mouse until you replug them in--then
>> they
>> have no power.
>>
>> Intrepid works perfectly on this machine with this bug never occuring
>> before
>> except in the Jaunty alphas and beta.
>>
>> Also, all my usb ports (according to my mobo manual) should be USB 2.0
>> compliant. For some reason, Ubuntu is not detecting all of the hubs as
>> 2.0.
>> My motherboard is an Asus M3N78-Pro.
>>
>> I'm using the latest nVidia driver from Jaunty--180.44
>>
>> NOTE: the following attachments/terminal outputs are before the issue
>> occurs
>> (since my mouse doesn't work when the bug happens).
>> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
>> occurs.
>> --------------------------------------
>> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009
>> x86_64
>> GNU/Linux
>> --------------------------------------
>> Jaunty beta
>> --------------------------------------
>> lscpi:
>>
>> 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: ...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: usb ports randomly shut off Jaunty beta

Thanks for the sources.list.

I hope this isn't a hardware issue.

What motherboard do you have?

I haven't had any issues with XP on my machine.

No blue screens or freezes at all, even with the nvidia drivers.

I don't use XP much however.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (4.9 KiB)

I've got the M4N78. I have not had any issues in XP until the other
night. I'm starting to wonder what really is causing the problem. Do
you have a USB hub connected to your computer? I am wondering if that
is causing problems with my other USB devices.

On 6/19/09, Chem. Imbalance <email address hidden> wrote:
> Thanks for the sources.list.
>
> I hope this isn't a hardware issue.
>
> What motherboard do you have?
>
> I haven't had any issues with XP on my machine.
>
> No blue screens or freezes at all, even with the nvidia drivers.
>
> I don't use XP much however.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops responding
> after a seemingly random amount of time. All the usb ports it turns out
> shut off--I've tried plugging various devices in all ports after the mouse
> stops responding and they are all without power. (edit:) However, all the
> devices still work except for the mouse until you replug them in--then they
> have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring before
> except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue occurs
> (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)
> 00:07.0 Audio device: nVidia Corporation MCP78S [GeForce 8200] High
> Definition Audio (rev a1)
> 00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 82...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: usb ports randomly shut off Jaunty beta

I don't use any external usb hubs with any of my pc's.

Motherboard manufacturers are known for using cheap internal usb hubs on their mobos though.

I've heard of people having issues with cheap internal hubs.

The thing is that only Jaunty has given me this problem.

XP, Hardy, BSD, and Intrepid work perfectly with my M3N78-PRO.

I did have a fairly new keyboard die on me with this desktop however. Maybe a voltage issue?

This is a pretty cryptic bug. It might also be a BIOS setting conflict.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.6 KiB)

Well, I spoke too soon, Debian just stopped my USB mouse. Keyboard kept
working, unplugged both and neither get power just like always.

It could very well be cheap internal hubs. I wouldn't put it past them. I
couldn't get Hardy to work because it would not detect the onboard Nvidia
8300 to install the nvidia drivers to use my dual monitors. I hope that my
keyboard or mouse don't die because of this mobo.

I messed around with some BIOS stuff as well and am running 0905 which is
the latest driver for it to no avail. Looks like I'll just be using XP...but
even on XP I got BSOD'd by the usbhub.sys driver. I just can't trust this
much.

On Sat, Jun 20, 2009 at 5:33 PM, Chem. Imbalance
<email address hidden>wrote:

> I don't use any external usb hubs with any of my pc's.
>
> Motherboard manufacturers are known for using cheap internal usb hubs on
> their mobos though.
>
> I've heard of people having issues with cheap internal hubs.
>
> The thing is that only Jaunty has given me this problem.
>
> XP, Hardy, BSD, and Intrepid work perfectly with my M3N78-PRO.
>
> I did have a fairly new keyboard die on me with this desktop however.
> Maybe a voltage issue?
>
> This is a pretty cryptic bug. It might also be a BIOS setting conflict.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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...

Read more...

Revision history for this message
Chris Oliver (excid3) wrote :
Download full text (6.1 KiB)

Someone on Fedora 11 said that their USB keyboard would stop working in the
same manner as ours. He removed a USB extension cable that he was using and
that fixed the problem. I'm wondering if our issue is relatively similar.

On Tue, Jun 23, 2009 at 7:41 PM, Chris Oliver <email address hidden> wrote:

> Well, I spoke too soon, Debian just stopped my USB mouse. Keyboard kept
> working, unplugged both and neither get power just like always.
>
> It could very well be cheap internal hubs. I wouldn't put it past them. I
> couldn't get Hardy to work because it would not detect the onboard Nvidia
> 8300 to install the nvidia drivers to use my dual monitors. I hope that my
> keyboard or mouse don't die because of this mobo.
>
> I messed around with some BIOS stuff as well and am running 0905 which is
> the latest driver for it to no avail. Looks like I'll just be using XP...but
> even on XP I got BSOD'd by the usbhub.sys driver. I just can't trust this
> much.
>
>
> On Sat, Jun 20, 2009 at 5:33 PM, Chem. Imbalance <
> <email address hidden>> wrote:
>
>> I don't use any external usb hubs with any of my pc's.
>>
>> Motherboard manufacturers are known for using cheap internal usb hubs on
>> their mobos though.
>>
>> I've heard of people having issues with cheap internal hubs.
>>
>> The thing is that only Jaunty has given me this problem.
>>
>> XP, Hardy, BSD, and Intrepid work perfectly with my M3N78-PRO.
>>
>> I did have a fairly new keyboard die on me with this desktop however.
>> Maybe a voltage issue?
>>
>> This is a pretty cryptic bug. It might also be a BIOS setting conflict.
>>
>> --
>> usb ports randomly shut off Jaunty beta
>> https://bugs.launchpad.net/bugs/350065
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in Ubuntu: New
>>
>> Bug description:
>> On Jaunty beta (and previous alphas) I notice that my mouse stops
>> responding after a seemingly random amount of time. All the usb ports it
>> turns out shut off--I've tried plugging various devices in all ports after
>> the mouse stops responding and they are all without power. (edit:) However,
>> all the devices still work except for the mouse until you replug them
>> in--then they have no power.
>>
>> Intrepid works perfectly on this machine with this bug never occuring
>> before except in the Jaunty alphas and beta.
>>
>> Also, all my usb ports (according to my mobo manual) should be USB 2.0
>> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
>> My motherboard is an Asus M3N78-Pro.
>>
>> I'm using the latest nVidia driver from Jaunty--180.44
>>
>> NOTE: the following attachments/terminal outputs are before the issue
>> occurs (since my mouse doesn't work when the bug happens).
>> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
>> occurs.
>> --------------------------------------
>> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009
>> x86_64 GNU/Linux
>> --------------------------------------
>> Jaunty beta
>> --------------------------------------
>> lscpi:
>>
>> 00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory
>> Controller (rev a2)
>> 00:01.0 IS...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: usb ports randomly shut off Jaunty beta

My mouse and keyboard are directly connected to the usb hubs on the motherboard.

No cables here.

I went back to Jaunty because Debian started doing the same thing.

Right now I just put up with rebooting every time it freezes (every few hours, sometimes it goes upwards of 6).

Revision history for this message
Mike Gerwitz (mikegerwitz) wrote :

My motherboard came with additional USB ports that may be connected optionally. I removed it on the 19th after reading the above posts, and I have not had any problems since. While I'd like to give it a bit more time, it does seem to hint at a hardware issue. When I have the time I will attempt to see if it is simply the USB header on the motherboard that is causing the problem, or if the problem occurs regardless of which header it is connected to.

I do still have my case's USB ports connected to the motherboard without problems. For those who do have USB ports on their case (or any other external USB ports), try disconnecting them and see if it resolves the issue. If so, try connecting it to a different header. Seeing as how this problem occurred daily for myself, this is a huge improvement. I haven't had to reboot since.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.4 KiB)

I realized I have never plugged the mouse into a different USB port. I do
not have optional ports (not that I know of). I will play around with it and
see.

On Sat, Jun 27, 2009 at 4:08 AM, Mike Gerwitz <email address hidden> wrote:

> My motherboard came with additional USB ports that may be connected
> optionally. I removed it on the 19th after reading the above posts, and
> I have not had any problems since. While I'd like to give it a bit more
> time, it does seem to hint at a hardware issue. When I have the time I
> will attempt to see if it is simply the USB header on the motherboard
> that is causing the problem, or if the problem occurs regardless of
> which header it is connected to.
>
> I do still have my case's USB ports connected to the motherboard without
> problems. For those who do have USB ports on their case (or any other
> external USB ports), try disconnecting them and see if it resolves the
> issue. If so, try connecting it to a different header. Seeing as how
> this problem occurred daily for myself, this is a huge improvement. I
> haven't had to reboot since.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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...

Read more...

Revision history for this message
/dev/null (arndt-stedler) wrote : Re: usb ports randomly shut off Jaunty beta

After I attached a fan (Arctic Cooler 3) on the "Northbridge" on my ASRock K10N78FullHD-hSLI it seems to be (as far as i can say right now) better. I haven't had any USB issues lately.
I am using Ubuntu with kernel "2.6.30-020630-generic" and NVIDIA-Linux-x86-185.18.14 driver [NVIDIA-Linux-x86-185.18.14-pkg1.run]
But every time i attach another USB-Stick or my camera i am still anxious :-(

I now hope it might be only an temperature issue. (I had this before on another ASRock mainboard... wrong usage of heat-conductive paste on shipping (one spot in the middle and that was it...))

I will report whether the system will run smooth and stable now.

arndt@hiveserver:~$ uptime
 08:52:46 up 1 day, 11:43, 2 users, load average: 0.00, 0.07, 0.18

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.6 KiB)

I may try it on mine as well. The mobo itself runs cool at 36C (maybe that's
hot for a mobo?) but the processor is at 50C normally with stock heatsink
and probably somewhat messed up thermal paste. It is running hotter than
when I first built the machine so this could definitely be a heat issue. If
I remember right, it was about 40C when I first turned it on and was
monitoring idle temps. Would make sense if it was a heat issue.

On Fri, Jul 3, 2009 at 1:53 AM, /dev/null <email address hidden> wrote:

> After I attached a fan (Arctic Cooler 3) on the "Northbridge" on my ASRock
> K10N78FullHD-hSLI it seems to be (as far as i can say right now) better. I
> haven't had any USB issues lately.
> I am using Ubuntu with kernel "2.6.30-020630-generic" and
> NVIDIA-Linux-x86-185.18.14 driver [NVIDIA-Linux-x86-185.18.14-pkg1.run]
> But every time i attach another USB-Stick or my camera i am still anxious
> :-(
>
> I now hope it might be only an temperature issue. (I had this before on
> another ASRock mainboard... wrong usage of heat-conductive paste on
> shipping (one spot in the middle and that was it...))
>
> I will report whether the system will run smooth and stable now.
>
> arndt@hiveserver:~$ uptime
> 08:52:46 up 1 day, 11:43, 2 users, load average: 0.00, 0.07, 0.18
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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: nVid...

Read more...

Revision history for this message
/dev/null (arndt-stedler) wrote : Re: usb ports randomly shut off Jaunty beta

Nope... Attaching a fan to the northbridge was not a solution.
i resized the VLC Window when suddenly the mouse died. The keyboard was still functional (Num-Lock light reacted as expected) but the screen did not react as it should. VLC did still play the movie but ALT+F2 did not show up the starter. It took about 45 seconds before my screen reacted to my keyboard again. Luckily i was able to shutdown the system correctly.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.1 KiB)

Well crap. This bug is really aggravating me. And yet it is not a problem in
Fedora for Chemical Imbalance. Maybe it's time I contact Asus and see if
they know of the issue seeing as we can't resolve it. :(

On Sat, Jul 4, 2009 at 12:07 PM, /dev/null <email address hidden> wrote:

> Nope... Attaching a fan to the northbridge was not a solution.
> i resized the VLC Window when suddenly the mouse died. The keyboard was
> still functional (Num-Lock light reacted as expected) but the screen did not
> react as it should. VLC did still play the movie but ALT+F2 did not show up
> the starter. It took about 45 seconds before my screen reacted to my
> keyboard again. Luckily i was able to shutdown the system correctly.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev
> a1)
> 00:07.0 ...

Read more...

Revision history for this message
/dev/null (arndt-stedler) wrote : Re: usb ports randomly shut off Jaunty beta

For what i have seen so far it might be an IRQ or IRQ sharing problem.
Does anybody encounter this problem when using an external graphics card?
It seems that this bug occurs randomly (in my case it seems to be connected with a video player. It does not matter whether driver i use (nvidia or nv or vesa) sometimes when this bug occurs and i do not shut down, but RESTART, my onboard soundcard is malfunctioning too (no sound at all).
Just a wild guess: When there is the "right" combination of Interrupts the system just drops one of them or signals a complete wrong state.
As soon as i have a little spare money i buy a PCIe card to test it.

Revision history for this message
Chris Oliver (excid3) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta
Download full text (5.3 KiB)

Just talked to a friend who seems to have had the same issue. He thinks its
related to X11 and mentioned writing the xorg.conf from scratch fixed it for
him. Anyone tried this yet? I haven't surprisingly.

On Sat, Jul 4, 2009 at 1:03 PM, /dev/null <email address hidden> wrote:

> For what i have seen so far it might be an IRQ or IRQ sharing problem.
> Does anybody encounter this problem when using an external graphics card?
> It seems that this bug occurs randomly (in my case it seems to be connected
> with a video player. It does not matter whether driver i use (nvidia or nv
> or vesa) sometimes when this bug occurs and i do not shut down, but RESTART,
> my onboard soundcard is malfunctioning too (no sound at all).
> Just a wild guess: When there is the "right" combination of Interrupts the
> system just drops one of them or signals a complete wrong state.
> As soon as i have a little spare money i buy a PCIe card to test it.
>
> --
> usb ports randomly shut off Jaunty beta
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 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
...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: usb ports randomly shut off Jaunty beta

I think I found the solution to my freezing at the least.

I believe it is an issue with IRQ assignment and sharing. I posted in a thread about this on the ubuntuforums.

Here are my /proc/interrupts and my lsusb:

[code]cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3
  0: 102 0 0 3 IO-APIC-edge timer
  1: 0 0 0 2 IO-APIC-edge i8042
  4: 0 0 0 1 IO-APIC-edge
  7: 1 0 0 0 IO-APIC-edge
  8: 0 0 0 1 IO-APIC-edge rtc0
  9: 0 0 0 0 IO-APIC-fasteoi acpi
 12: 0 0 0 4 IO-APIC-edge i8042
 14: 0 0 2 3582 IO-APIC-edge pata_amd
 15: 0 0 0 0 IO-APIC-edge pata_amd
 19: 0 0 0 3 IO-APIC-fasteoi ohci1394
 20: 0 0 0 477 IO-APIC-fasteoi ohci_hcd:usb3, nvidia
 21: 0 0 1 1660 IO-APIC-fasteoi ehci_hcd:usb2, HDA Intel
 22: 0 0 0 1 IO-APIC-fasteoi ehci_hcd:usb1
 23: 0 0 11 7448 IO-APIC-fasteoi ohci_hcd:usb4
2298: 0 0 58 50716 PCI-MSI-edge eth0
2299: 0 0 16 7431 PCI-MSI-edge ahci
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 22949 13508 10719 30490 Local timer interrupts
RES: 14107 7407 9277 7849 Rescheduling interrupts
CAL: 156 180 173 49 Function call interrupts
TLB: 1146 877 877 881 TLB shootdowns
SPU: 0 0 0 0 Spurious interrupts
ERR: 1
MIS: 0
[/code]

[code]lsusb
Bus 002 Device 004: ID 05ac:021d Apple, Inc.
Bus 002 Device 002: ID 05ac:1005 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt Wheel
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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
[/code]

Notice that nvidia is sharing an irq with my usb hub # 3.

I had my mouse plugged into usb hub 3 and I had freezing.
I simply moved my mouse to hub 4 and no more freezing.

It seems it is an irq problem for me.

Good luck all.

Revision history for this message
Jacob Harrison (fictional-truth) wrote :

I checked mine but I'm having trouble making heads or tails of it.

vox@deep-thought:~$ cat /proc/interrupts
           CPU0 CPU1
  0: 109 0 IO-APIC-edge timer
  1: 1 1 IO-APIC-edge i8042
  7: 1 0 IO-APIC-edge parport0
  8: 0 0 IO-APIC-edge rtc0
  9: 0 0 IO-APIC-fasteoi acpi
 12: 0 4 IO-APIC-edge i8042
 14: 1223 224552 IO-APIC-edge pata_amd
 15: 4603 311438 IO-APIC-edge pata_amd
 16: 10968 3438101 IO-APIC-fasteoi ivtv0, nvidia
 19: 0 3 IO-APIC-fasteoi ohci1394
 20: 29320 19806697 IO-APIC-fasteoi eth0
 21: 6588 1415625 IO-APIC-fasteoi ohci_hcd:usb2
 22: 1 5 IO-APIC-fasteoi ehci_hcd:usb1
 23: 12219 2816957 IO-APIC-fasteoi sata_nv, Intel ICH
NMI: 0 0 Non-maskable interrupts
LOC: 8675368 9504512 Local timer interrupts
RES: 2613587 1455029 Rescheduling interrupts
CAL: 9067 3618 Function call interrupts
TLB: 298819 353968 TLB shootdowns
SPU: 0 0 Spurious interrupts
ERR: 1
MIS: 0

vox@deep-thought:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 006: ID 03f0:5411 Hewlett-Packard Officejet 4300
Bus 002 Device 008: ID 046d:c227 Logitech, Inc.
Bus 002 Device 007: ID 046d:c226 Logitech, Inc.
Bus 002 Device 005: ID 046d:c223 Logitech, Inc. G15 Keyboard / USB Hub
Bus 002 Device 004: ID 056a:0042 Wacom Co., Ltd Intuos 2 6x8
Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Bus 002 Device 002: ID 046d:c041 Logitech, Inc.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

That's before changing usb ports on the mouse, I believe my mouse is one of the "Logitech, Inc." entires but since my keyboard has two useb ports on it as well I'm afriad I can't really tell which it is. I'm assuming it's the ID 046d:c223, because after switching usb ports that's the device that moved.

This is after switching the mouse to a different usb port:

vox@deep-thought:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 009: ID 046d:c041 Logitech, Inc.
Bus 002 Device 006: ID 03f0:5411 Hewlett-Packard Officejet 4300
Bus 002 Device 008: ID 046d:c227 Logitech, Inc.
Bus 002 Device 007: ID 046d:c226 Logitech, Inc.
Bus 002 Device 005: ID 046d:c223 Logitech, Inc. G15 Keyboard / USB Hub
Bus 002 Device 004: ID 056a:0042 Wacom Co., Ltd Intuos 2 6x8
Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I'm assuming since it stayed on bus 2

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

It looks like nvidia is sharing an irq with your IVTV device. I'm assuming that's a usb tv tuner?

Try plugging your tuner into another port.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

I'm going to mark this SOLVED since I have the solution and its been three days and no freezing whatsoever.

Good luck to everyone else. Check your irq assignments with "cat /proc/interrupts" and check what nvidia is sharing an irq with. Look at your lsusb and move whatever device it is sharing with to another hub/port.

This at least works for me.

description: updated
tags: added: solved
summary: - usb ports randomly shut off Jaunty beta
+ usb ports randomly shut off Jaunty beta (SOLVED)
description: updated
Revision history for this message
Jacob Harrison (fictional-truth) wrote :

Actually, it's a pci tv tuner card. Would moving it to a different pci slot help be something to try or would they all share one irq? Removing it all together is an option, I haven't used it since switching to Ubuntu, and even with vista and xp, I didn't use it often. Could it be sata_nv (which I'm assuming is a hard drive) and intel ICH (the southbridge chip after a little research) sharing an irq, I've noticed the mouse stops working periodically when I'm transfering large amounts of files from my IDE drive to my SATA drive. Since I can't move the southbridge obviously, I suppose I could try the other SATA connector. But first, since Chem's bug seems to have been solved by resolving the conflict with the nvidia graphics card, I guess I'll start by removing the Tuner card.

Since I've failed to do it in any amount of detail, I'll post a more specific system profile, maybe we can find something similar about all the systems having the bug.
Mobo: Foxconn C51GU01 North: Geforce 6100 South: nForce 410
Western Digital 320 GB 7200 RPM PATA Hard Drive
A more recent Western Digital (I think)160 gb SATA HDD
4gb pc 400 SDRAM
XFX Geforce 7900GS
16X Double-Layer Multi-Format DVD/R/RW/CD-R/W Drive900GS
AMD Athlon™ 64 4200+ Processor
Logitech G15 keyboard
Logitech G5 mouse

Not really sure if it's relevant now, but I had almost an entire month go by without the mouse shutting off so I'm not getting my hopes up just yet.

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :

That's what I would do. Remove the tuner for say, a week, and see what happens.

Good luck.

Revision history for this message
Jacob Harrison (fictional-truth) wrote :

Didn't work for me, completely removed the TV tuner and still having the issue, I switched the printer and mouse when I plugged them back in without realizing it, and only figured out I was still having the issue today when I was doing some printing. I can deal with it being the printer, I'd rather not have to restart the computer every 30 pages I print, but at least I can still click things.

I'm going to try swapping the sata plugs and if still happens, I think I'm going to decide that I can't have anything that works the way it's supposed to, rip the drive out, find a usb enclosure, and reinstall Ubuntu on the old drive.

Adil Arif (adisari06)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Aleksis (aleksis-doma) wrote :

For those desperate for a viable workaround while the problem persists, I recommend trying the following as it works for me.

# sudo modprobe -r usbmouse && sudo modprobe -i usbmouse

That works for my mouse — it can then be plugged into any usb port and will work, this workaround isn't almighty though since my usb storage works in neither of the ports. So I fix it in the same fashion:

# sudo modprobe -r usb-storage && sudo modprobe -i usb-storage

I get the module names by asking modprobe (modprobe -l usb*).
Don't know what would work for other devices or if there's a way to reset all usb stuff at once.
Also, creating a custom command for these lines is sweet.

Revision history for this message
markusd112 (markusd112) wrote :
Download full text (3.6 KiB)

I have similiar problems with ubuntu 9.10 and my Shuttle Barebone SN78SH7 and the integrated nvidia GeForce 8200 graphic card: sometimes the usb bus hangs up so mouse and keybord doesn't respond any longer. When disconnecting it from usb bus, there seems to be no power on the bus (optical mouse is dark).

Another great problem with it: sometimes the system hangs up completeley: the screen changes in a text mode and it is full of colored blocks.
When rebooting it, the shuttle start screen and grub is displayed properly. When changing in graphics mode again, the colored screen is displayed again and the system hangs. After cut it from power for about 30 secondes everything works fine again.

It seems to be a problem when the system is working with a high workload (e.g. virtual box is running and several other tasks).

Nvidia has the same interrupt as usb2, but in the usb2 port there is no device connected. How do I change the interrupts?

Here is my interrupt list and a lsusb:

root@server:~# cat /proc/interrupts
           CPU0 CPU1 CPU2 CPU3
  0: 45 0 0 9 IO-APIC-edge timer
  1: 0 0 0 2 IO-APIC-edge i8042
  6: 0 0 0 2 IO-APIC-edge floppy
  7: 1 0 0 0 IO-APIC-edge parport0
  8: 0 0 0 1 IO-APIC-edge rtc0
  9: 0 0 0 0 IO-APIC-fasteoi acpi
 12: 0 0 0 4 IO-APIC-edge i8042
 14: 0 0 55 1526 IO-APIC-edge pata_amd
 15: 0 0 0 0 IO-APIC-edge pata_amd
 17: 0 0 0 3 IO-APIC-fasteoi ohci1394
 20: 0 0 1 1907 IO-APIC-fasteoi ohci_hcd:usb3, HDA Intel
 21: 0 0 0 1387 IO-APIC-fasteoi ehci_hcd:usb2, nvidia
 22: 0 0 2 11364 IO-APIC-fasteoi ehci_hcd:usb1
 23: 0 0 1 128 IO-APIC-fasteoi ohci_hcd:usb4
 26: 0 0 4 14165 PCI-MSI-edge ahci
 27: 0 0 0 881 PCI-MSI-edge eth0
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 48350 21055 21335 52518 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
CNT: 0 0 0 0 Performance counter interrupts
PND: 0 0 0 0 Performance pending work
RES: 8313 7529 7732 4982 Rescheduling interrupts
CAL: 221 219 208 95 Function call interrupts
TLB: 1532 1198 1001 841 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 5 5 ...

Read more...

Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote : Re: [Bug 350065] Re: usb ports randomly shut off Jaunty beta (SOLVED)
Download full text (10.6 KiB)

I have had the same problems sometimes with the messed up screen after
booting. It stopped after I updated my nVidia drivers from their page [
http://www.nvidia.com/Download/index.aspx?lang=en-us].
Right now I'm using this beta driver:
http://www.nvidia.com/object/linux_display_amd64_195.22.html.
I've had no more messed up screens since.

As for the interrupts problem, that is strange. It looks like there aren't
any conflicts. I don't know much about changing interrupts, but I know that
some BIOSes let you change them manually.

Sorry if I couldn't be of much help.

Mit freundlichen Grüßen,
CD

On Thu, Dec 10, 2009 at 12:55 PM, Markus Drexelius <email address hidden>wrote:

> I have similiar problems with ubuntu 9.10 and my Shuttle Barebone
> SN78SH7 and the integrated nvidia GeForce 8200 graphic card: sometimes
> the usb bus hangs up so mouse and keybord doesn't respond any longer.
> When disconnecting it from usb bus, there seems to be no power on the
> bus (optical mouse is dark).
>
> Another great problem with it: sometimes the system hangs up completeley:
> the screen changes in a text mode and it is full of colored blocks.
> When rebooting it, the shuttle start screen and grub is displayed properly.
> When changing in graphics mode again, the colored screen is displayed again
> and the system hangs. After cut it from power for about 30 secondes
> everything works fine again.
>
> It seems to be a problem when the system is working with a high workload
> (e.g. virtual box is running and several other tasks).
>
> Nvidia has the same interrupt as usb2, but in the usb2 port there is no
> device connected. How do I change the interrupts?
>
> Here is my interrupt list and a lsusb:
>
> root@server:~# cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3
> 0: 45 0 0 9 IO-APIC-edge timer
> 1: 0 0 0 2 IO-APIC-edge i8042
> 6: 0 0 0 2 IO-APIC-edge floppy
> 7: 1 0 0 0 IO-APIC-edge
> parport0
> 8: 0 0 0 1 IO-APIC-edge rtc0
> 9: 0 0 0 0 IO-APIC-fasteoi acpi
> 12: 0 0 0 4 IO-APIC-edge i8042
> 14: 0 0 55 1526 IO-APIC-edge
> pata_amd
> 15: 0 0 0 0 IO-APIC-edge
> pata_amd
> 17: 0 0 0 3 IO-APIC-fasteoi
> ohci1394
> 20: 0 0 1 1907 IO-APIC-fasteoi
> ohci_hcd:usb3, HDA Intel
> 21: 0 0 0 1387 IO-APIC-fasteoi
> ehci_hcd:usb2, nvidia
> 22: 0 0 2 11364 IO-APIC-fasteoi
> ehci_hcd:usb1
> 23: 0 0 1 128 IO-APIC-fasteoi
> ohci_hcd:usb4
> 26: 0 0 4 14165 PCI-MSI-edge ahci
> 27: 0 0 0 881 PCI-MSI-edge eth0
> NMI: 0 0 0 0 Non-maskable interrupts
> LOC: 48350 21055 21335 ...

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Chem.,

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/lucid.

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 350065

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Chem. Imbalance (moonlightpastel-deactivatedaccount) wrote :
Download full text (7.7 KiB)

Hi,

It is no longer an issue as of Jaunty as far as I can tell.

On Fri, Mar 12, 2010 at 12:50 PM, Jeremy Foshee <<email address hidden>
> wrote:

> Hi Chem.,
>
> 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/lucid.
>
> 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 350065
>
> 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.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> usb ports randomly shut off Jaunty beta (SOLVED)
> https://bugs.launchpad.net/bugs/350065
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> {SOLVED--see below}
> On Jaunty beta (and previous alphas) I notice that my mouse stops
> responding after a seemingly random amount of time. All the usb ports it
> turns out shut off--I've tried plugging various devices in all ports after
> the mouse stops responding and they are all without power. (edit:) However,
> all the devices still work except for the mouse until you replug them
> in--then they have no power.
>
> Intrepid works perfectly on this machine with this bug never occuring
> before except in the Jaunty alphas and beta.
>
> Also, all my usb ports (according to my mobo manual) should be USB 2.0
> compliant. For some reason, Ubuntu is not detecting all of the hubs as 2.0.
> My motherboard is an Asus M3N78-Pro.
>
> I'm using the latest nVidia driver from Jaunty--180.44
>
> NOTE: the following attachments/terminal outputs are before the issue
> occurs (since my mouse doesn't work when the bug happens).
> (EDIT): I have attached my lsusb and dmesg out put also AFTER the bug
> occurs.
> --------------------------------------
> uname: 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 10:01:17 UTC 2009 x86_64
> GNU/Linux
> --------------------------------------
> Jaunty beta
> --------------------------------------
> lscpi:
>
> 00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory
> Controller (rev a2)
> 00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200...

Read more...

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Chem,
     Thank you for following up with me on this. I will mark this bug a Fix Released.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
juancherru (juancherru) wrote : apport-collect data

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: VT1708B Analog [VT1708B Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: juan 2200 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 21'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:1106e721,10438345,00100100 HDA:10de0002,10de0101,00100000'
   Controls : 38
   Simple ctrls : 19
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=4c1a25a8-1b84-4415-8fe5-a82f950a2866
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-20-generic root=UUID=3c3edcdc-0b8b-4fae-abdd-08742f6f0ac8 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_AR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-20-generic i686
UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev pulse pulse-access sambashare saned video www-data
dmi.bios.date: 11/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1407
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd11/12/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
juancherru (juancherru) wrote : AlsaDevices.txt
Revision history for this message
juancherru (juancherru) wrote : AplayDevices.txt
Revision history for this message
juancherru (juancherru) wrote : BootDmesg.txt
Revision history for this message
juancherru (juancherru) wrote : Card0.Amixer.values.txt
Revision history for this message
juancherru (juancherru) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
juancherru (juancherru) wrote : Card0.Codecs.codec.3.txt
Revision history for this message
juancherru (juancherru) wrote : CurrentDmesg.txt
Revision history for this message
juancherru (juancherru) wrote : Lspci.txt
Revision history for this message
juancherru (juancherru) wrote : Lsusb.txt
Revision history for this message
juancherru (juancherru) wrote : PciMultimedia.txt
Revision history for this message
juancherru (juancherru) wrote : ProcCpuinfo.txt
Revision history for this message
juancherru (juancherru) wrote : ProcInterrupts.txt
Revision history for this message
juancherru (juancherru) wrote : ProcModules.txt
Revision history for this message
juancherru (juancherru) wrote : UdevDb.txt
Revision history for this message
juancherru (juancherru) wrote : UdevLog.txt
Revision history for this message
juancherru (juancherru) wrote : WifiSyslog.txt
Revision history for this message
juancherru (juancherru) wrote : XsessionErrors.txt
tags: added: apport-collected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.