Linux over current condition

Arch Linux

You are not logged in.

#1 2013-06-27 11:09:14

[Solved] USB Over-current condition on port 3 and 4

Hello everyone,
I finally booted up arch from my HD, however the problems doesn’t end (welcome to arch for me)
And arch greeted me with the following message:(may not be exacly the same):

Fast TSC callibration failed.
usb-0.0.0.0(do not remember numbers) Over-current condition on port 3
usb-0.0.0.0(do not remember numbers) Over-current condition on port 4

Then I logged it, startx and everything seem to work fine for now.
However the message is bugging me.

Can you please help me(or at least show me the way) to fix this.
NOTE: I’ve got linux mint 14 installed and it doesn’t seem to have such problems.

NOTE2: this is what I got from lsusb -v: (from arch)
http://pastebin.com/FNLVeufn (line 141,142)

P.S. Actually I’ve got the feeling that arch is just printing this without a real problem.

P.S.2: This is laptop Asus-K53SV. Thus all usbs that are visible are working(I’ve got 2x 2.0 usbs and 1x 3.0)

Last edited by Nickie (2013-06-30 09:25:24)

#2 2013-06-27 13:48:57

Re: [Solved] USB Over-current condition on port 3 and 4

That message can hint to a broken / defective usb-port. Maybe you have two front-usb slots registered as port 3 and port 4? I’ve seen broken front-usb slots before, but this is just a guess. Try disconnecting them from the motherboard.

#3 2013-06-30 09:25:09

Re: [Solved] USB Over-current condition on port 3 and 4

For everyone with laptop ASUS (K53 and others also):

For some reason linux thinks that there is over-current condition on port 3 and 4.
This is probably a false alarm. Nothing to worry about.

After changing different versions of the kernels and trying on different machines the result was that all laptops K53(there are many ppl with this laptop around me) gives positive result(overcurrent), tough the message is hidden by default on some versions of the kernel(with dmesg it’s still there).\

Marking as solved.

#4 2014-06-26 10:09:40

Re: [Solved] USB Over-current condition on port 3 and 4

Even I have Asus K53SM laptop and I can confirm the issue. As noted here, I hope that this is just a warning and will not cause any problems!

#5 2014-08-17 07:05:23

Re: [Solved] USB Over-current condition on port 3 and 4

I can confirm that this error message has been present ever since I got my K53SC back in 2011. Nothing to worry about, I’d rather call this a false alarm, because none of the connected devices (cameras, smartphones, pendrives, external drives, portable mp3 players) were damaged over the years. By the way, these over-current condition warnings are related to the USB 2.0 ports, not the one USB 3.0.

#6 2014-08-17 18:54:37

Re: [Solved] USB Over-current condition on port 3 and 4

It really means that your device is drawing more current from the port than it negotiated for. On a USB port, a device is not permitted to draw more than 100mA at the time it is connected to the host. During discovery, the device tells the host how much current it requires for full operation. The host can then authorize the device to draw that much current, or not — based on how much current is available. On USB 2.0 the maximum permitted draw is 500mA, but only after negotiation. Your device is ignoring the current limitations and your host is protesting. USB 3.0 permits 150mA initially, and 900mA max unless it supports the newer battery charger extensions, in which case one can draw up to 1800mA after negotiation.

Last edited by ewaller (2014-08-17 18:54:57)

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#7 2015-05-26 18:51:04

Re: [Solved] USB Over-current condition on port 3 and 4

I also have a laptop with the same problem — Asus K53SC => over current condition on port . . .
I get this message even if I disable the USB ports from BIOS and I know there is no real issue with the ports.

Please tell me how to get pass this message and log into the system. Do I have to load the kernel manually? And if so, how do I do that?

Источник

USB 2-1 Over-Current message

I recently upgraded my system from 16.04 to 17.04 and I am now constantly receiving the message (looping in ctrl+alt=F1 and in dmesg:

I’ve looked around and found that it is usually an empty warning and all my USB ports are working and intact.

I have tried editing /etc/default/grub with «GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash,ehci_hcd.ignore_oc=1» but the warning still shows up.

I’ve also tried looking at the other topics similar to mine and haven’t found a solid solution/ set of instructions on inserting the ignore_oc command.

I’m new to Ubuntu/Linux in general so if you need anything from me let me know!

Any help would be greatly appreciated!

Okay, so i’ve been looking through some log files and found the message starts after it has detected my keyboard. I’ve posted the output below but still have no idea how to go about resolving this.

2 Answers 2

It appears to be a typo, you need to use spaces as delimiter of multiple boot options (as in «quiet splash»). So instead of

GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash ehci_hcd.ignore_oc=1″

You can check whether it worked by running

after the reboot. If it yields «Y», the boot parameter was set; if it yields «N» something went wrong, check spelling (musst be all lower case) and whether you indeed ran

after setting the option and before the restart.

By the way: why the downvote?

Over current condition is related to abnormal current flow higher than expected. This is a hardware problem in your USB port (or other component related to USB). In most of the cases, this is caused by dust/humidity (Remember that most of dust is, in general, dead skin and it is a very good humidity holder).

You shouldn’t simply ignore this condition. There is an electrical issue in your motherboard. If the ports are attached by cable, you can pull it out. Otherwise, if the ports are soldered in the MB, it will be more difficult to sane.

My first attempt to resolve is do a very very detailed clean on the motherboard. Works in the majority of the cases.

Some rare cases, the ports need to be replaced. In only one, I solved by replacing a capacitor.

Источник

Thread: over-current issue with USB 2.0 ports

Thread Tools

Display

over-current issue with USB 2.0 ports

My system (on Ubuntu 14.04) is no longer shutting down/restarting/suspending since a problem with all usb 2.0 ports occurred. (all of a sudden all usb 2.0 were without power. Luckily, the usb 3.0 ports are still working) In fact, the system stays stuck on «over-current condition on port 1 and 2» which is very annoying since only prolonged pushing on the power button can shutdown the notebook.
dmesg :
[ 282.314980] hub 2-1:1.0: over-current condition on port 2
[ 282.522964] hub 2-1:1.0: over-current condition on port 1
.
I already tried adding ehci_hcd.ignore_oc=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grubbut this is of no use.
I just want it to ignore any faults so that it can shutdown or reboot.

Re: over-current issue with USB 2.0 ports

Look inside the USB ports with a flashlight. A bent wire, or dirt could be shorting them out. If the ports are shorted, then the ACPI system which is the BIOS control of power will be unhappy.

You can turn off power to the USB ports using the acpitool.

Unumquodque potest reparantur. Patientia sit virtus.

Re: over-current issue with USB 2.0 ports

Hello,
I have the same issue with Ubuntu 14.04.2, and only with it. I have no problems with Windows.
I have even tried Ubuntu 12.04, but it revealed other serius bugs (for me), so naw I am on 14.04.2 again and on every boot I have that error message.
What I think is that this is not a hardware problem, but a bug or something in Ubuntu itself. I have a Nvidia optimus tecnology
which is a pain with linux.

Re: over-current issue with USB 2.0 ports

Are you getting the error message with nothing plugged into the USB ports?

Welcome to the forums.

Unumquodque potest reparantur. Patientia sit virtus.

Re: over-current issue with USB 2.0 ports

I think I have found the source of the problem. As I mentioned before I have intel+nvidia graphics, and, as I install the Nvidia proprietary drivers I get this error at reboot. Now I am pretty sure there is a bug within Nvidia drivers, or something. So I removed them and installed Noveau instead and then the error message was gone.
However there is another issue: Noveau doesn’t work well on my machine with bumblebee, so I have only the discrete card working.

Источник

Fedora over-current condition on port 1

When I boot up my Fedora 18, I got this message > [1.817675] hub 2-1:1-0: over-current condition on port 1 shown on the screen. Right after the Fedora logo disappear, and it is not yet boot into Fedora.

I was stuck now since I could not do anything, could anyone please advice what should I do for this problem? Before this issue was happened, I just download the necessary development package for LibreOffice using this command > su -c ‘yum-builddep libreoffice’ , I hope this is not the root cause of the problem.

2 Answers 2

It sounds like a USB device is trying to draw too much current. Has nothing to do with LibreOffice. You may be able to see the message again with dmesg .

lsusb -v will show each device and their power draws. That should find it for you.help you track it down!

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

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

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.

So if you determine that the message is benign you can disable it using the ignore_oc option.

Источник

Linux over current condition

• Home
• :
• QorIQ Processing Platforms
• :
• Layerscape
• :
• usb over-current condition on ls1021a board

usb over-current condition on ls1021a board

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

we ran into this issue on a ls1021a based custom board. Design is very similar to the

TWR board. But without the USB 3.0 hub.

During boot the linux kernel reports an over-current condition and port power is then disabled. So no USB devices are detected:

[ 3028.127516] hub 1-0:1.0: USB hub found

[ 3028.129991] hub 1-0:1.0: 1 port detected

[ 3028.143710] hub 2-0:1.0: USB hub found

[ 3028.146156] hub 2-0:1.0: 1 port detected

[ 3028.449817] hub 1-0:1.0: over-current condition on port 1

[ 3028.669099] hub 2-0:1.0: over-current condition on port 1

The kernel comes from the SDK 1.9 with only minor changes in its configuration.

The SDHC field in the RCW is set to 3 (for DRVVBUS/PWRFAULT). Our USB power switch is connected to these pins. DRVVBUS is low and PWRFAULT is high. That’s the problem.

We changed the RCW[SHDC] to 1 so that the DRVVBUS can be controlled as GPIO. As GPIO we could enable DRVVBUS, the 5V were switched on and finally USB devices were detected.

So where does this over-current condition comes from? What might cause this strange problem?

USB does also not work in u-boot. But it does on the TWR board.

Источник