continuous error message to kernel log

[brettatoms]

I get the following message continuously in the kernel logger.

[64002.409295] hub 5-0:1.0: over-current change on port 1
[64002.513134] hub 5-0:1.0: over-current change on port 2
[64002.616987] hub 5-0:1.0: over-current change on port 3
[64002.720925] hub 5-0:1.0: over-current change on port 5
[64002.824755] hub 5-0:1.0: over-current change on port 6
[64002.928515] hub 3-0:1.0: over-current change on port 1
[64003.032352] hub 3-0:1.0: over-current change on port 2
[64003.136201] hub 2-0:1.0: over-current change on port 1
[64003.240044] hub 2-0:1.0: over-current change on port 2
[64003.343998] hub 1-0:1.0: over-current change on port 1
[64003.447795] hub 1-0:1.0: over-current change on port 2

The numbers on the left starts at 0 on boot and continuously counts up. I see the message run nonstop on all my virtual terminals(Ctrl-Alt-F1/F2/F3...), see it from sudo cat /proc/kmsg and from the dmesg command.

This causes constant load on my computer and if I'm doing anything else on my computer that creates heavy load, like installing new packages, then it becomes painful to do anything else.

I don't know the type of the counter that is keeping track of this number but I assume it would eventually overflow.

Using Feisty Beta - Linux kernel 2.6.20.14.12

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[brettatoms (brettatoms)]

$ uname -a
Linux licuala 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux

[brettatoms (brettatoms)]

Let me know if there's any other information I can provide.

[brettatoms (brettatoms)]

If I toggle the kernel's uhci module then the output stops. Attached is the relevant part of dmesg when I run the following:
$ sudo modprobe uhci_hcd ; sleep 2 ; sudo modprobe -r uhci_hcd

This is with no devices connected the the USB ports.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[brettatoms (brettatoms)]

I was having this problem with all kernel versions in 8.10 and although it seems to be more random than predictable I haven't experienced this bug since my upgrade to 9.04. Feel free to open close this bug and I will reopen it if need be.

[Leann Ogasawara (leannogasawara)]

Closing this for now based on the previous comment. Thanks.

[Benjamin Geese (ben-8409)]

This bug seems to affect me.

There are some differences: My messages look like this:
Apr 8 18:13:35 ben-laptop kernel: [ 2036.248127] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:35 ben-laptop kernel: [ 2036.496123] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:35 ben-laptop kernel: [ 2036.744141] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:40 ben-laptop kernel: [ 2041.304043] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:40 ben-laptop kernel: [ 2041.952116] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:41 ben-laptop kernel: [ 2042.200135] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:41 ben-laptop kernel: [ 2042.448122] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:41 ben-laptop kernel: [ 2042.696100] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:42 ben-laptop kernel: [ 2043.440105] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:42 ben-laptop kernel: [ 2043.688089] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:42 ben-laptop kernel: [ 2043.936098] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:43 ben-laptop kernel: [ 2044.184101] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:43 ben-laptop kernel: [ 2044.432089] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:43 ben-laptop kernel: [ 2044.680098] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:45 ben-laptop kernel: [ 2046.168100] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:45 ben-laptop kernel: [ 2046.416093] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:45 ben-laptop kernel: [ 2046.664333] hub 2-0:1.0: over-current change on port 2
Apr 8 18:13:47 ben-laptop kernel: [ 2048.365345] hub 2-0:1.0: over-current change on port 2

The numbers are always the same.
This did not happen in 9.04 to me.

[llawwehttam (llawwehttam)]

This is generally fixed by enabling USB LEGACY MODE in the BIOS.

If not it can be early signs of a PSU failing and the motherboard turning off USB devices to protect them.