continuous error message to kernel log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
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(
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
Changed in linux-source-2.6.20: | |
assignee: | brian-murray → ubuntu-kernel-team |
status: | Needs Info → Confirmed |
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. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
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:/