On a laptop I see these errors on (most) resumes:
hub 3-0:1.0: over-current change on port 1
hub 3-0:1.0: over-current change on port 2
The error message doesn't explain what action should be taken. Neither
does the code surrounding this message. A quick look at the (large) USB
specification didn't make it clear to me why this should be an error.
All other over-current related messages in this file are at dev_dbg()
level. There are no obvious other problems with USB after resume. I have
no idea what an over-current change actually is, so it's just a guess
that this message can be downgraded to dev_dbg() level.
Signed-off-by: Paul Bolle <pebolle@xxxxxxxxxx>
---
drivers/usb/core/hub.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index d041c68..17ed38a 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -3412,7 +3412,7 @@ static void hub_events(void)
}
if (portchange & USB_PORT_STAT_C_OVERCURRENT) {
- dev_err (hub_dev,
+ dev_dbg (hub_dev,
"over-current change on port %d\n",
i);
clear_port_feature(hdev, i,
--
1.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
