Linux Usb Error Messages

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this linux usb error 71 site About Us Learn more about Stack Overflow the company Business Learn more linux usb error 110 about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix

Usb Device Not Accepting Address Error 71

& Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it

Usb Error Codes Linux

works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Where can I find a list of USB error codes? up vote 2 down vote favorite Every time I boot Debian, the boot log shows a bunch of xhci_hcd problems, and messages like usb 3-13: hub failed to enable device, error -22 usb 3-13: device descriptor usb error code list read/8, error -61 I'm having a hard time finding out what these error codes actually mean, though. Is there anywhere that lists what all of these error codes mean? debian boot drivers usb documentation share|improve this question asked Mar 19 '15 at 18:27 Eric Dand 1135 Hmmm....you'll probably end up looking at the driver source code for the definitive answer. –mdpc Mar 19 '15 at 18:30 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote accepted The first one is EINVAL (a standard POSIX C error) inverted. If you are curious it's from line 4218 in [src]/drivers/usb/core/hub.c (v. 3.19): 4217 if (udev->state != USB_STATE_DEFAULT) 4218 return -EINVAL; The other one is from the hub_port_init() function in the same file. These kinds of error messages aren't really intended to provide more information to end users than what's there ("hub failed to enable device"), however. They're used in debugging, possibly including if you were to file a bug report. If you were hoping for documentation that will explain the problem in detail I think you are out of luck. Part of the reason for this is perhaps that there may

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site

Usb Error 32

About Us Learn more about Stack Overflow the company Business Learn more about usb eproto error hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is device descriptor read/64 error 32 a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The http://unix.stackexchange.com/questions/191272/where-can-i-find-a-list-of-usb-error-codes best answers are voted up and rise to the top How to understand and debug USB issues with Linux up vote 1 down vote favorite I’m having an odd problem with a cheap "reverse USB hub" —not sure what the technical name might be— named a Tek Republic TUS-200 USB Sharing Switch. it has one USB port for devices, and two host ports that i can http://superuser.com/questions/875922/how-to-understand-and-debug-usb-issues-with-linux connect two computers and then a switch that conects the device to one computer or another. I use it as a KVM with one usb keyboard and two computers) It works fine on Windows but that may just be because the laptop I’m using has one USB bus per port... more on that later. On Linux, Debian 7 3.2.0-4-amd64, it works fine, until there is a considerable data transfer on another device on the same usb bus. For example, copying a large file to a pen drive. I’m almost sure it has to do with grounding on the reverse-usb, because that does not happen when it is connected to only one computer. But the question here is not so much to debug said device, but to make sense of the Linux kernel USB system log messages, as I never had to deal with them, and now I could not find absolutely nothing explaining it in layman terms. Here it is: As soon as I start to transfer to a pen drive on the same USB bus that the reverse-hub is, I get this on dmesg: Feb 8 16:36:51 dotmatrix kernel: [10807.868649] generic-usb 0003:04D9:0114.0006: can't reset

Canada. flickr Links BitBucket Blogger eBay Drive2 Etsy Facebook Flattr Flickr GitHub Google+ Kroogi Last.fm LinkedIn ohloh Postcrossing Tumblr Twitter YouTube Paul Philippov home is where ~/ is Instead of a resumé Contacts How to fix "device not accepting address" https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error 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 usb error 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 linux usb error 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 6 years ago) Article tags: linux, usb Comments // 78 Click here to leave a comment ThiasJ over 5 years ago Thank you SO much!!! I thought I had to buy a new HDD! will smith about 5 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 5 years ago Yep. Saved me a bunch of time as well. Thanks a bunch for posting this. dardino over 4 years ago some one knows how to fix the problem without rebooting? Sergei Kirjanov over 4 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 4 years ago Worked for me, thanks! :-D. A soft reboot on didn't appear to fix it, so defin