Arch Linux

sanjuchopra

Member

From: Gurgaon,INDIA

Registered: 2010-08-01

Posts: 33

over-current condition on port 3

i got a new notebook asus k53sm.I installed Arch linux on it and everytime on  boot  get this error

hub 4-1:1.0: over-current condition on port 3
hub 4-1:1.0: over-current condition on port 4

nothing is connected to usb port,even then i get this error.
I want to know is there any motherboard problem (when i plug usb flash drive it works fine)  ???

nomorewindows

Member

Registered: 2010-04-03

Posts: 3,542

Re: over-current condition on port 3

I've seen it when something that is part of the package is unplugged (some accessory board) it reports over-current.  Hopefully nothing on the motherboard that supposed to be there is accidently unplugged.

---

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

rb3

Member

Registered: 2012-09-17

Posts: 9

Re: over-current condition on port 3

I have the same problem/messages for my Asus K43SM laptop, bought 5 days ago. I had the store I bought it from check it out, and they used a separate hard-drive with Windows XP installed to see if an error would pop up. Windows XP did not report any USB errors, but Arch does. Is this safe to ignore?

When I bought the laptop, I had the RAM upgraded. Perhaps a connection was loosened in the process of installing the RAM? Here is the part of my

# lsusb -v

output that bothers me:

Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x8087 Intel Corp.
  idProduct          0x0024 Integrated Rate Matching Hub
  bcdDevice            0.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             6
  wHubCharacteristic 0x0009
    Per-port power switching
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent      0 milli Ampere
  DeviceRemovable    0x00
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0100 power
   Port 2: 0000.0303 lowspeed power enable connect
   [color=#FF0000]Port 3: 0000.0008 oc[/color]
   [color=#FF0000]Port 4: 0000.0008 oc[/color]
   Port 5: 0000.0100 power
   Port 6: 0000.0100 power
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Notice Ports 3 and 4 near the bottom of the message.

Everything works so far, though I have not yet tested the battery. I will post if having the battery disconnected might be causing this error.

EDIT: lsusb -v shows the same error with the battery plugged and charging.

Last edited by rb3 (2012-09-17 15:11:13)

bernarcher

Forum Fellow

From: Germany

Registered: 2009-02-17

Posts: 2,281

Re: over-current condition on port 3

rb3 please use [ code ] tags instead of [ quote ] ones for your listings.

---

To know or not to know ...
... the questions remain forever.