How to fix "device not accepting address" error

If Linux suddenly happen to fail to recognize a USB drive, check dmesg for errors. Once you see a bunch of errors like

usb 1-5: device descriptor read/64, error -32  
usb 1-5: new high speed USB device using ehci_hcd and address 21  
usb 1-5: device not accepting address 21, error -32

most probably it’s a result of hardware failure rather than a driver or kernel bug. USB has an over-current protection, which gets triggered when power consumption from the port is too high.

Unplug all USB devices from PC, turn power off, and wait a minute or two. Plug everything back and boot into Linux.

I spent the whole morning, until found out why. I hope that this message will save someone a few hours, and nerves.

PS: Actual errors may vary. You may see different port and/or error code. Ex.:

usb 3-1: device descriptor read/64, error -62

or

usb 4-2: device descriptor read/64, error -71

or

usb 2-3: device descriptor read/64, error -101

but the root of the problem is the same.

Published on October 21, 2010 (almost 7 years ago)

Article tags: linux, usb

Comments (85)

ThiasJ about 6 years ago

Thank you SO much!!! I thought I had to buy a new HDD!

will smith about 6 years ago

God bless you! I was tearing my hair out trying to fix an error -62 problem that was disabling any usb device I plugged in after I had removed a usb sound card. Unplugging the computer and leaving it unplugged for a couple of minutes fixed it, thank you! No one else seems to have discovered this, I've been reading other posts talking about unloading modules, and many other more complicated troubleshooting methods and fixes when I found your page. Many, many thanks to you!

JonW almost 6 years ago

Yep. Saved me a bunch of time as well. Thanks a bunch for posting this.

dardino over 5 years ago

some one knows how to fix the problem without rebooting?

Sergei Kirjanov over 5 years ago

I had similar problem (error message).
USB devices (webcam and /dev/sdX) somehow conflicted.
How?
May be not just ¨Plug everything back¨, but play with minimal sets of devices.

Kris over 5 years ago

Worked for me, thanks! :-D. A soft reboot on didn't appear to fix it, so definitely power off/unplug/power on.

Yusuke over 5 years ago

How can this be fixed, i mean, plug and play, like it's supposed to be?
Coz works fine on Windows, so how can be a Hardware issue if it's only on some software that i have this problem?!

dato000 about 5 years ago

thank you very much!!!
gracias sensei!!!

Finally I got my mouse working in archbang!!!

Bob about 5 years ago

I got to agree with Yusuke, I mean I'm glad it helped you and these other people that comment, but that's just bonkers.

As an Android developer, I have a stack of devices here. I plug some in, and get those "device descriptor read/64, error #" messages, yet, without doing anything to the system and using the same usb cable, I can plug in any assortment of ~40 other devices and they all get properly enumerated and show up via lsusb and are ready to work with. In this scenario I assume it's something like the host is sending an initialization command that the target is ignoring or improperly answering during the usb handshake, and the host gives up.

This is not what the issue is. If the overcurrent safety tripped, the port would be unusable.

Glad it works for you guys, though!

Carlos C Soto almost 5 years ago

Thanks! I had try with "irqpoll" kernel parameter and disabling USB but nothing work...
What you wrote here solve the problem. Thanks a lot!

sobol almost 5 years ago

I encountered this problem connecting the Arduino MEGA 2560 to the ALIX 2d13 SBC. Although Arduino UNO worked fine, the above mentioned error appeared when I connected the MEGA. After connecting an external 12V power supply to the Arduino, everything works like charm. Thanks a lot for pointing me in the right direction!

R. Boyer over 4 years ago

Thanks. I encountered a similar problem with error code 110. Your solution worked for me.

joee over 4 years ago

great, I was struggling with clonezilla and my new hdd

Ciprian over 4 years ago

God bless you, man! You're a genius! :)

chromewavez over 4 years ago

AWESOME!!! Thanks...so many other forums recommended scripts, turning off USB power management, etc, etc. But your solution worked!

wenjing over 4 years ago

I almost had a headache due to error code 110 this morning. You saved me, God bless you, the method works for me!!!

PJ Brunet over 4 years ago

That fixed it for me. I had my phone plugged into my laptop (charging) while listening to the radio on my phone, while the laptop was on. Power-hungry little phone!

Shev77 about 4 years ago

Thank you very much!

bill about 4 years ago

Thanks for this too!! SAved me some big headaches!

scillystuff about 4 years ago

Great, just what I was after. Satnav with completely flat battery wouldn't mount as mass storage, due to high recharge on the port.

nick about 4 years ago

Hey, thanks a lot man. I had problem with my mouse at start up because of this thing. Happened just after a fresh new Ubuntu install first update. So thought it was a driver problem...

Found many related discussion, logitech wireless bug, mouse not starting needing to be re-plugged to start, but nothing matching or solving my own mouse issue. Searching for the error message was not really helpful either, until finding out your post.

Brilliant; I was tired to search on Ubuntu forums for a special mouse bug, and to try different version to find back the old drivers -all of course without success.

Anyway. So thanks. Wishing google would put your page first when researching that error message. Cheers!

Philipp about 4 years ago

I cant belive that actually worked...

Nabeel Moidu almost 4 years ago

Paul, had this same issue and my USB keyboard wouldn't power on. Since this is now the landing for google, can you add that changing the USB ports on the lap can work in some cases. I had a logitech USB keyboard on a ThinkPad T420 and apart from the lower right USB port all others threw this error.

kapetr almost 4 years ago

I have interesting experience:

I have long (5m) USB extension cable.

On some devices connected on it, no problem.
But on others I get:

-------------------
ct 5 08:19:44 zly-hugo kernel: [ 806.363995] usb 1-1.3: new low-speed USB device number 13 using ehci_hcd
Oct 5 08:19:46 zly-hugo kernel: [ 808.504620] usb 1-1.3: device not accepting address 13, error -32
Oct 5 08:19:46 zly-hugo kernel: [ 808.576687] usb 1-1.3: new low-speed USB device number 14 using ehci_hcd
Oct 5 08:19:46 zly-hugo kernel: [ 808.648583] usb 1-1.3: device descriptor read/64, error -32
Oct 5 08:19:46 zly-hugo kernel: [ 808.824313] usb 1-1.3: device descriptor read/64, error -32
Oct 5 08:19:46 zly-hugo kernel: [ 809.000051] usb 1-1.3: new low-speed USB device number 15 using ehci_hcd
Oct 5 08:19:47 zly-hugo kernel: [ 809.407275] usb 1-1.3: device not accepting address 15, error -32
----------------

If I put the SAME device direct in PC, in the SAME port (as 5m cable was) the device is recognized correctly!!!

=> it may be timing problem or power loss over long cable !

Jose A. García almost 4 years ago

yes!! yes!! yes!! awesome!! 2 days looking for a solution. Fantastic!! I was about to throw in the towel and assuming that my system takes 4 minutes more to start, when I came to your page.

Thank you!!!

Brian Hames almost 4 years ago

I have a multi-card reader with addition USB ports & alternate power and it was driving me nuts - it worked before and didn't now. I just disconnected the power and re-connected the hub and it was fine. Then reconnected power.

Michael Butler over 3 years ago

unplugging it & plugging it back in didn't solve it for me. Restarting didn't help either. My mouse would still randomly disconnect and never reconnect again. I'm currently investigating this solution: askubuntu.com/questions/62315/lost-wireless-mouse-connection-when-laptop-is-on-battery In other words, I'm blacklisting the USB suspend feature for this mouse device.

Jonathan Young over 3 years ago

I fixed this error using a different (shorter) USB cable. So it was a hardware issue. I have also experienced issues with cables on serial/usb protocols for GPS devices

mamboze over 3 years ago

Hi, I had an issue with a Asus Xonar U3 audio device, which I posted on in the ubuntu forums

Your comments on USB over-current protection being tripped were right on and guided me to solving the problem.

Thanks and best regards

Johann over 3 years ago

Thank you very much !

Coben over 3 years ago

Thanks so much!!!

stands2reason over 3 years ago

Saw this error trying to use an Arduino. Makes sense that it was an over-currenting problem. Connected it to a powered USB hub and it was detected normally, no restart required.

Ashwin Nanjappa over 3 years ago

I was tearing my hair out on this error. None of the USB ports on my system were working. They worked fine on Windows though.

After reading your post, I noted that the notebook had been running on for many days now. I powered it down and left it for 15 minutes. Powered back on and the USB worked!

Thanks so much! :-)

diyhouse over 3 years ago

Sorry,.. this does not work for me,.. my device pulls 35mA @ 5volts,.. this should never blow any over current trips,.. even with in-rush surge power up,.. something else is going on here,.. and I do not know what!!

Sid Choudhari about 3 years ago

Thankx, budy it's helps a lot...!

kamran almost 3 years ago

thanks man... you saved me hours.. i had an issue with the integrated camera, ubuntu wasn't able to find it, and was getting usb device descriptor errors.. ur solution solved the problem.

gregorIO over 2 years ago

Works! Thank you!
Universal serial bull! :D

Pat over 2 years ago

Tu parles d'une solution de merde. Eteindre/allumer et c'est reparti..super le mec !

Jesper K. over 2 years ago

Hello.
I have a similar error on a home-built system, but the error code is "-104", which I cannot seem to find addressed anywhere.
Does anybody know if this is still related to power shortage etc., or something completely different?
Thanks!

Paul Philippov over 2 years ago

Jesper, you can look up error codes in /usr/include/asm-generic/errno-base.h file. Error -104 means connection reset by peer. But that is what software returns. What causes the error is another story. It can be a shorted USB port.

Jesper K. over 2 years ago

Thanks a lot for your quick response. ;-)
My problem is that I'm the Hardware-guy, while my ESW-guy is no longer working here. Just a short follow-up: Who is the "peer" at this point - the Host controller itself, the hub(s) underway or the Device recently attached)
Thanks.

Paul Philippov over 2 years ago

Jesper, I guess that in order to be reset by the peer the connection has to be initiated by the host first. I see it like your USB port sent the initial request but did not receive an answer. Maybe it is the device you're trying to connect to the port causes the error? Did you try to connect any other device to the port while watching dmesg?

Isabele AA over 2 years ago

This doesn't work for me, but I'll leave here the solution that I fund in:
"unix.stackexchange.com/questions/72625/why-is-usb-not-working-in-linux-when-it-works-in-uefi-bios"

I hope that this would help someone.

"It seems with newer Gigabyte mainboards (at least) there is a BIOS option called IOMMU Controller that is disabled by default and gives no clue or indication as to what it is for.

Enabling this setting and rebooting "magically" restores all my USB and networking problems in a 64-bit Linux OS (doesn't matter which one)."

If this also doesn't work, yu can try adding "iommu=soft" to the kernel command line.

comphilip over 2 years ago

Thank you SO much!!! I almost want to throw the HDD.

Michel Andre over 2 years ago

Bonjour
Merci beaucoup car, suite migration Ubuntu 15.4 , j'avais ces messages d'erreurs et un démarrage très difficile.
Merci!!!

heavymerchant over 2 years ago

You Sir, are my saviour. Thank you!

Andreas Gantner over 2 years ago

I spent hours on trying to get rid of "device not accepting address .." ... not even your solution worked. Finally, I installed Linux Mint and all USB port work like a charm.

Fred - Brazil over 2 years ago

Got rid off those error messages and incredible decrease boot time. This's really crazy!!!
Thank you very much!!!

lezard fsnlenneth about 2 years ago

I'm having this problem too trying to boot the latest clonezilla live on a usb stick on a z97 deluxe board. What happens is the kb works fine in text mode but when it gets to the gui, both the kb and mouse do not function. It is driving me bats!!!

Andreas S. about 2 years ago

Thanks, helped me to safe a lot of time!

Gui Ambros almost 2 years ago

This has been annoying me for weeks. I've tried unplugging all USB devices, rebooted, connected via SSH, and... nothing. The error was still there. I've tried rebooting at least 15 times, to no avail. Even tried uninstalling drivers, but still the same.

I have rebooted many times using hard reset (i.e., cycling the power button), so I read this with skepticism and disdain. I was absolutely sure this "isn't my case", as I've used soft and hard reset. But hey, I was desperate, and had nothing to lose.

Turned it physically off (using the switch in the power supply), and left it off for 3-4 minutes. Turned it back on, checked dmesg and... it was clean! No more annoying "device not accepting address xx, error -32".

Rebooted 4-5 times more, just to make sure it wasn't just coincidence; no, it really fixed it. Connected all USB devices back, and everything is now working fine.

So, to all fellow smarty pants out there that think you know better: save yourself some headache and give it a try.

In hindsight, it's pretty obvious now that the power button doesn't cut the power to the USB hub, so if you tripped the over-current protection, you need a full power off to reset it.

Otto almost 2 years ago

I had error -71 and the above solution did not help.

I eventually traced it to a faulty USB cable

Stephen almost 2 years ago

@Isabelle AA, thanks so much for your post! I've been tearing my hair out all morning trying to get my USB ports to work and this fixed it!

Gorfo almost 2 years ago

Thank you so much. It solved my issue.
I was desesperating from finding the root cause of my issue.

chivi almost 2 years ago

Nice short article. As it actually should be.

Unfortunately it did not solve my issue, but as soon as I read here the error explanation - about over-current protection - I found root cause for my case.

For those guys, whom the first method (recommended by Paul) did not help, try to use a shorter cable to attach your device. It may sounds strange, but in my case I found a series of connect/disconnect events into dmesg and syslog as well. This behavior is a typical (as per my understanding) if you have a low-pass filter in between the usb port and the device attached - this low-pass filter (just a basic RC chain) is the result of combination of high input impedance and capacity caused by your cable. By using shorter (0.1m instead of 1m) cable did eventually solve the issue for me, but not power plug/unplug games...

But this is not a SW issue for sure...

Awesome Donkey almost 2 years ago

Unfortunately this didn't work for me...

[ 11.225438] usb 1-3: device descriptor read/all, error -110
[ 11.337524] usb 1-3: new high-speed USB device number 3 using xhci_hcd
[ 21.480411] usb 1-3: device descriptor read/all, error -110
[ 21.592532] usb 1-3: new high-speed USB device number 4 using xhci_hcd
[ 26.615914] usb 1-3: device descriptor read/8, error -110
[ 31.743439] usb 1-3: device descriptor read/8, error -110
[ 31.959689] usb 1-3: new high-speed USB device number 5 using xhci_hcd
[ 36.983086] usb 1-3: device descriptor read/8, error -110
[ 42.110574] usb 1-3: device descriptor read/8, error -110
[ 42.214694] usb usb1-port3: unable to enumerate USB device

Joey almost 2 years ago

Thank you very much for this post! I often have problems with my USB ports - they don't detect my USB mouse. Usually, it's just a matter of rebooting, but today that wasn't working. Then I read this post and turned my computer off, connected my computer to the main power source, unplugged my USB mouse, then turned my computer back on - and then it worked! My USB was detected straight away. Maybe I need to have my computer connected to the charger (via cable) when I turn it on. Thanks again :)

Jack over 1 year ago

I have the same problem like Awesome Donkey. Raspbian starts, bbut the peripherals are not working.

Vishal over 1 year ago

Thanks.
Not working for me!

How can I disconnect every USB thing () if I'm using a laptop which lists webcam,KBD as USB connection which can not be disconnected?

Marco over 1 year ago

Thank you so much! I was worried that my keyboard might be dead

leegold over 1 year ago

Tearing huge hunks of hair out of my head. A long-distance usb wifi adapter would not connect. Trying everything I was about to throw in the towel. You saved me. Thanks!

joel over 1 year ago

Merci beaucoup

dan over 1 year ago

Thank You !!

Sławek over 1 year ago

Thank you, it helped me also!

passed by over 1 year ago

Thank you for this, to me i changed the USB to front panel and everything worked i guess it was drawing too much power from the back ports

Hiker over 1 year ago

Thank you, you solve my issue on kernel 4.4.18 (no probs under kernel 4.2)

big.foot over 1 year ago

Thank you!

twsh over 1 year ago

Thank you very much, I thought my hardware was becoming faulty.

PR over 1 year ago

Cables... length is less important than quality because various issues come into play: impedance, capacitance, shielding, susceptibility to crosstalk (often solved by twisting matched pairs), etc. Had this problem with a short 24" cable. Switched to a better quality 60" cable which works.

Juan jose about 1 year ago

¡¡Muchas gracias!!

Necesité + de un minuto pero funcionó

**********************

Thank you very much!!

+ I needed a minute but it works

Jeffrey Lebowski about 1 year ago

As always, French people show great charm, education and nice attitude (Pat). In addition to speaking in their language only, in a place where everyone is using another one, both because they are too proud with their 'grandeur' to "submit to the Anglo-Americans" and to insult people hoping not to be understood.

However, I thank Paul for his post, but I must report it did not work for me. Another thing however did.

After safely removing an ext4 USB3.0 pen drive when a text file inside it was open, the drive would not mount anymore. Detected by `fdisk -l` with no problem, mount would alway fail, with a lot of different 'device not accepting address #' error codes (-62, -101 and whatnot), in addition to error loading journal, I/O error sector #, Failed to read block at offset #, Command completion event does not match command and so on, you name it.

Tried removing current and battery from my laptop for a lot of time to no avail, tried plugging in the key in other computers and still no cigar, tried wall-connecting the USB key (crazy idea) and not a chance, Lance.

Then, a simple idea striked me: e2fsck. Journal recovered, inodes number corrected, and after a 2 second wait my drive was read. Mount worked intantly.

Greetings from Italy!

Jeffrey Lebowski about 1 year ago

And sorry for all the typos...

Jacob Buscher about 1 year ago

Thanks you so much! Five years later this post is still helping people!

Nic about 1 year ago

Thanks you so much Paul.
I was getting mad.

Nic
Perth, Australia

John A about 1 year ago

Oh for pete sake, can it really be that easy?!!

I put a powered usb hub between my USB DVD reader and my computer and that seems to have solved the problem of -71 errors.

Of course It appears my USB 3.0 device is now down to a USB 1.1 speed.

Too much power draw!!

Rolder 12 months ago

Thank you. For a moment i thought i had 6 usb hdd failures.

Churchland 11 months ago

Thanks for this fix, strange bug. I had to turn off the power at the PS like someone in the comments suggested.

usbguy 10 months ago

I sometimes get this with one of my USB flash drives, but usually unplugging and replugging without rebooting has worked. I still have to run fsck whenever this happens. I don't know why the drive runs out of power sometimes.

Alexander 9 months ago

I had

usb 1-1.3: device descriptor read/all, error -32

usb 1-1.3: device not accepting address 83, error -32

usb 1-1.3: can't set config #1, error -32

and several other similar error messages on my Lenvov Thinkpad X220 after 6 years of using this machine. The following steps did not solve the problem: Switching off and on, Reinstalling the system and flashing the UEFI/BIOS.

The following solved the problem on my Thinkpad X220:
Underneath the fingerprint scanner there are (might be) unused cables without insulation (I believe they have RF connectors). I believe these cables are meant to connect an optional cellular module. If you don't have a cellular module these cables touch the circuit board and cause shorts. I insulated the open connector with shrinkable tubing. The errors are gone now.

Good luck,

Pauli 8 months ago

Thank you! You just saved me alot of time.

Chirag Chauhan 7 months ago

supppeeerrrbbb!!!! You make my day

shadow 6 months ago

Dear Paul,
I'm having usb 2-1.6: device descriptor read/64, error -32 and for me it has nothing to do with hardware malfunction.
The error only occurs upon booting Debian (both Jessie and Stretch) or old versions of Ubuntu and it's derivatives. After updating Ubuntu to newer version the error vanishes.
How the error works: If some of my peripherals ( Razer Naga mouse, Razer Black Widow chroma keyboard) are connected to a USB port while GRUB is booting OS the error occurs and I cannot use the devices. If I disconnect them just for the booting of Linux period and connect them back when it's loaded, everything works correctly. Also devices work in BIOS/UEFI before Linux starts booting.
As Debian uses old packages I can only suspect that it's a bug in one of the packages. It doesn't occur in Ubuntu as it uses up to date packages.
The problem is I don't know which package to update, I'm hardly an expert... :/

Dennis 6 months ago

Thanks, finally I found the right solution. Other threads directed me in a wrong direction (USB autosuspend) but this log had the right solution. In my case, I had to remove the laptop battery since this is also a power source.

Alexander 4 months ago

I've got a problem. I got this message on my Aspire V15 Nitro and I can't fully power it down, because the battery can't be removed and the battery is a power source.

Maybe I'll have to let it run out of power...

Paul Philippov 4 months ago

Alex, you still can disconnect the battery but it will require you to partially disassemble the laptop. Or you could give it a good load to drain the battery faster, and then, after it shuts down, wrap the laptop in a plastic bag and stash in a fridge for a while. Cold temp would lower batteries leftover voltage further and hopefully make the protection to reset. We used this method to reset German carded car radios in 90s. Just remember to not power up your laptop while it's still cold. Let it warm up to the room temperature for a couple hours to let any residue humidity to evaporate.