From: Valdis.Kletnieks@vt.edu
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Weird USB over-current messages in recent kernels...
Date: Tue, 05 Jul 2011 18:08:30 -0400 [thread overview]
Message-ID: <61130.1309903710@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
Seen during boot the last few days on my laptop:
running 3.0.0-rc4-mmotm0622:
Jul 2 13:08:37 turing-police kernel: [ 2.788108] hub 2-0:1.0: over-current condition on port 1
Jul 2 13:08:37 turing-police kernel: [ 2.990088] hub 2-0:1.0: over-current condition on port 2
Jul 2 13:08:37 turing-police kernel: [ 3.193073] hub 6-0:1.0: over-current condition on port 1
Jul 2 13:08:37 turing-police kernel: [ 3.395088] hub 6-0:1.0: over-current condition on port 2
running 3.0.0-rc5-mmotm0630:
Jul 5 09:43:36 turing-police kernel: [ 203.686082] hub 6-0:1.0: over-current condition on port 1
Jul 5 09:43:36 turing-police kernel: [ 203.969179] hub 6-0:1.0: over-current condition on port 2
Jul 5 09:43:36 turing-police kernel: [ 204.217077] hub 6-0:1.0: over-current condition on port 1
The problem? I don't see any devices that would *cause* the condition:
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 413c:2513 Dell Computer Corp.
Bus 001 Device 003: ID 413c:2513 Dell Computer Corp.
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 001 Device 005: ID 045e:0023 Microsoft Corp. Trackball Optical
Bus 001 Device 006: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
The device 5 and 6 on bus 1 are attached to the docking station, the Jul 2 boot
was undocked and those two devices weren't present. Nobody home on bus 2 or 6
at any time, as far as I can tell.
Any ideas?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2011-07-05 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 22:08 Valdis.Kletnieks [this message]
2011-07-06 14:52 ` Alan Stern
2011-07-06 15:38 ` Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61130.1309903710@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®