From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: Weird USB over-current messages in recent kernels...
Date: Wed, 06 Jul 2011 19:38:20 +0400 [thread overview]
Message-ID: <4E14816C.7070001@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1107061048160.1995-100000@iolanthe.rowland.org>
Hello.
Alan Stern 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.
Wasn't there a similar dev_err() message before that patch that added this
message (the previous message was printed on any over-current signal change)?
> 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.
If it's EHCI driver, there's module option to suppress over-current
checking, called 'ignore_oc'. It should help with bogus over-current signalling...
> Alan Stern
WBR, Sergei
prev parent reply other threads:[~2011-07-06 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 22:08 Weird USB over-current messages in recent kernels Valdis.Kletnieks
2011-07-06 14:52 ` Alan Stern
2011-07-06 15:38 ` Sergei Shtylyov [this message]
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=4E14816C.7070001@mvista.com \
--to=sshtylyov@mvista.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.