linux-kernel - Re: Weird USB over-current messages in recent kernels...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1107061048160.1995-100000@iolanthe.rowland.org>
Date:	Wed, 6 Jul 2011 10:52:02 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Valdis.Kletnieks@...edu
cc:	linux-kernel@...r.kernel.org, <linux-usb@...r.kernel.org>
Subject: Re: Weird USB over-current messages in recent kernels...

On Tue, 5 Jul 2011 Valdis.Kletnieks@...edu wrote:

> 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:

> 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?

That message was added recently, which may explain why you haven't seen 
it before.

For more debugging, please collect a usbmon log for bus 2 or bus 6 (see 
Documentation/usb/usbmon.txt).  In fact, you might try doing this for 
an earlier kernel as well.

It may be that your host controllers claim that an over-current
condition exists when it really doesn't, or it may be that those ports
are wired incorrectly and really do have an over-current condition.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/