linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: T?nu Samuel <tonu@jes.ee>, linux-usb@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: USB3.0 ?PD720200 complains about over-current
Date: Fri, 15 Oct 2010 10:12:17 -0700	[thread overview]
Message-ID: <20101015171217.GA22299@kroah.com> (raw)
In-Reply-To: <1286985669.4853.14.camel@x41.itrotid.ee>

On Wed, Oct 13, 2010 at 07:01:09PM +0300, T?nu Samuel wrote:
> Hi!
> 
> I know, this is place where only Gods speak and others not. But I am
> sure there is something odd I found and someone here can take care of
> it.

For usb specific stuff like this, try using the
linux-usb@vger.kernel.org mailing list.

> In situation when nothing is connected to any USB ports Ubuntu 10.04.1
> stock kernel complains:
> spider@spider:~$ zcat /var/log/kern.log.2.gz | grep -i current | head
> Sep 29 23:30:12 spider kernel: [    9.048388] hub 8-0:1.0: over-current
> change on port 1
> Sep 29 23:30:12 spider kernel: [    9.152036] hub 8-0:1.0: over-current
> change on port 2
> Sep 29 23:30:12 spider kernel: [    9.256038] hub 8-0:1.0: over-current
> change on port 3
> Sep 29 23:30:12 spider kernel: [    9.360037] hub 8-0:1.0: over-current
> change on port 1
> Sep 29 23:30:12 spider kernel: [    9.464036] hub 8-0:1.0: over-current
> change on port 2
> Sep 29 23:30:12 spider kernel: [    9.570621] hub 8-0:1.0: over-current
> change on port 3
> Sep 29 23:30:12 spider kernel: [    9.672037] hub 8-0:1.0: over-current
> change on port 1
> Sep 29 23:30:12 spider kernel: [    9.776038] hub 8-0:1.0: over-current
> change on port 2
> Sep 29 23:30:12 spider kernel: [    9.880049] hub 8-0:1.0: over-current
> change on port 3
> Sep 29 23:30:13 spider kernel: [    9.984041] hub 8-0:1.0: over-current
> change on port 1
> spider@spider:~$ 
> 
> This runs forever and makes computer busy forever just running those
> messages. I verified same behavior exists with vanilla 2.6.35.7.
> Disabling USB3.0 in BIOS turns off problem and all USB2 ports remain to
> work. So probably this is xHCI driver who complains. I looked bit around
> in source and see it is copied from USB2 code and possibly USB3 has
> something different. I've read USB3 can supply more power, so possibly
> something here has changed.

Do you have the xhci driver loaded for the USB 3.0 controller?

> My hardware:
> 
> Motherboard ASUS M4A88T-I Deluxe
> http://www.asus.com/product.aspx?P_ID=jGAoIFEziW5sPYy7
> 
> it has USB3 chip "NEC D720200F1" on it:
> http://digi.physic.ut.ee/mw/images/d/de/20100926_digi_007.png
> 
> NEC is joined Renesas, so this is his link for datasheet etc:
> http://www2.renesas.com/usb/en/product/upd720200.html
> 
> If you propose patch, I can give him test run.

Any xhci developers have an idea?

thanks,

greg k-h

      parent reply	other threads:[~2010-10-15 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 16:01 BUG: USB3.0 µPD720200 complains about over-current Tõnu Samuel
2010-10-13 18:27 ` Tõnu Samuel
2010-10-15 17:12 ` Greg KH [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=20101015171217.GA22299@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tonu@jes.ee \
    /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;
as well as URLs for NNTP newsgroup(s).