Bug 212169 - "hub 1-0:1.0: over-current change on port" messages.
Summary: "hub 1-0:1.0: over-current change on port" messages.
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 4.4
Hardware: i686 Linux
Target Milestone: ---
: ---
Assignee: Pete Zaitcev
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-25 14:12 UTC by Chris Lalancette
Modified: 2010-06-07 05:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-07 05:42:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmidecode from affected HP ML70 system (36.39 KB, text/plain)
2006-10-25 14:12 UTC, Chris Lalancette
no flags Details

Description Chris Lalancette 2006-10-25 14:12:56 UTC
+++ This bug was initially created as a clone of Bug #124114 +++

Description of problem:

Customer is seeing messages of this sort:

Aug 25 16:31:10 fclassdb kernel: hub 4-0:1.0: over-current change on port 2

while using the RHEL-4 U4 kernel.  Unloading both the ehci_hcd and uhci_hcd
modules caused the messages to stop printing; however, having either of the two
modules (or both) installed caused these messages.  The hardware is an HP ML70
i686 machine; I'll attach the dmidecode here as well.

Comment 1 Chris Lalancette 2006-10-25 14:12:58 UTC
Created attachment 139347 [details]
dmidecode from affected HP ML70 system

Comment 3 Chris Lalancette 2006-12-12 18:33:06 UTC
     Do you know if these messages are relatively benign, or if they are
actually a problem?  The customer doesn't have any USB devices installed, and is
wondering whether this indicates a problem or if it's just a false positive.

Chris Lalancette

Comment 4 Pete Zaitcev 2006-12-19 04:58:25 UTC
Chis asks, if these messages are benign. The answer: depends. They do not
affect operation of devices which are plugged into ports and enumerated.
But they are not entirely harmless, for two reasons.

#1: khubd is stuck for 500ms every time this happens, so this delays the
processing of connects and disconnects;

#2: As part of the recovery from the overcurrent, power is re-enabled
on all ports. If hub has coarsely grained power, this may affect other
ports. I don't know if this is an issue on ML70.

Navid asks, if there's a hardware problem. Yes, it's likely, although
it may be a firmware problem. These messages happen (most likely) if
(a) the southbridge's harness is improperly designed and/or implemented
and shunts the power to the ground, or (b) the descriptors of the hub
do not match the actual hardware and we access ports which do not exist.

Neither of these should be fatal, it's the recovery which makes it bad.
We should not fill up the logs with these messages.

What to do? I don't know right away. We cannot ignore overcurrent
indications. So, ideally we ought to devise a way to detect a broken
port and somehow disable it (until... what? reboot?)

Comment 5 Pete Zaitcev 2006-12-21 00:15:11 UTC
Chris, do you know of a way to get access to a system with this symptom?
I need to experiment, maybe get usbmon traces.

Comment 6 Chris Lalancette 2006-12-21 03:24:30 UTC
     Not off-hand, although it is a certified system so we must have some
around.  Let me email a few people and find out...I'll get back to you.

Chris Lalancette

Comment 12 RHEL Product and Program Management 2007-05-09 09:07:57 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 14 RHEL Product and Program Management 2007-09-07 19:39:25 UTC
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time.  This request will be
reviewed for a future Red Hat Enterprise Linux release.

Note You need to log in before you can comment on or make changes to this bug.