Generic Usb Error Codes Linux

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 About Us Learn more about Stack Overflow the usb error code list company Business Learn more about hiring developers or posting ads with us Unix & Linux linux usb error 71 Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of usb device not accepting address error 71 Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the

Usb Eproto Error

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 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 linux usb error 110 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 not be any more accurate, detailed explanation that can be provided. Some things can fail the same way with a range of indeterminate potential causes. share|improve this answer answered Mar 19 '15 at 19:05 goldilocks 48k1098147 add a comment| Did you find this question interesting? Try our newsletter Sign up for our newsletter and get

1 Revised: 2004-Oct-21 2 3 This is the documentation of (hopefully) all possible error codes (and 4 their interpretation) that can be returned from usbcore. 5 6 Some of them are returned by the Host Controller Drivers (HCDs), which 7 device drivers only see through urb status usbcore. As a rule, all the HCDs should 8 behave the same

Urb Error Codes

except for transfer speed dependent behaviors and the 9 way certain faults are reported. 10 11 12 ************************************************************************** 13

Usb Error 32

* Error codes returned by usb_submit_urb * 14 ************************************************************************** 15 16 Non-USB-specific: 17 18 0 URB submission went fine 19 20 -ENOMEM no memory for allocation of internal structures 21 22 USB-specific: http://unix.stackexchange.com/questions/191272/where-can-i-find-a-list-of-usb-error-codes 23 24 -EBUSY The URB is already active. 25 26 -ENODEV specified USB-device or bus doesn't exist 27 28 -ENOENT specified interface or endpoint does not exist or 29 is not enabled 30 31 -ENXIO host controller driver does not support queuing of this type 32 of urb. (treat as a host controller bug.) 33 34 -EINVAL a) Invalid transfer type specified (or not http://lxr.free-electrons.com/source/Documentation/usb/error-codes.txt supported) 35 b) Invalid or unsupported periodic transfer interval 36 c) ISO: attempted to change transfer interval 37 d) ISO: number_of_packets is < 0 38 e) various other cases 39 40 -EXDEV ISO: URB_ISO_ASAP wasn't specified and all the frames 41 the URB would be scheduled in have already expired. 42 43 -EFBIG Host controller driver can't schedule that many ISO frames. 44 45 -EPIPE The pipe type specified in the URB doesn't match the 46 endpoint's actual type. 47 48 -EMSGSIZE (a) endpoint maxpacket size is zero; it is not usable 49 in the current interface altsetting. 50 (b) ISO packet is larger than the endpoint maxpacket. 51 (c) requested data transfer length is invalid: negative 52 or too large for the host controller. 53 54 -ENOSPC This request would overcommit the usb bandwidth reserved 55 for periodic transfers (interrupt, isochronous). 56 57 -ESHUTDOWN The device or host controller has been disabled due to some 58 problem that could not be worked around. 59 60 -EPERM Submission failed because urb->reject was set. 61 62 -EHOSTUNREACH URB was rejected because the device is suspended. 63 64 -ENOEXEC A c

communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://askubuntu.com/questions/653766/error-using-usb-flashdrive-what-usb-error-codes-mean the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions http://ftp.riken.jp/Linux/kernel/v2.2/patch-html/patch-2.2.18/linux_Documentation_usb_error-codes.txt.html Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's usb error how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error using usb flashdrive - what usb error codes mean? up vote 1 down vote favorite I have somewhat arbitrary errors when using a pendrive, as reported by dmesg: [ 306.904222] usb 2-3: new high-speed USB device number 7 usb error code using ehci-pci [ 321.080172] usb 2-3: string descriptor 0 read error: -110 [ 321.080191] usb 2-3: New USB device found, idVendor=125f, idProduct=c08a [ 321.080199] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 326.083021] usb 2-3: can't set config #1, error -110 My question is: what does the error code "-110" mean here? Pointer to the corresponding code of the Linux kernel can be helpful. It is non-deterministic. The pendrive will often work, but fails randomly both in my Desktop machine and in my Dell XPS12 laptop running Ubuntu 14.04. usb error-handling dmesg share|improve this question asked Jul 28 '15 at 15:28 Elias 1061 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Try something like the command below (in a terminal). strings /usr/src/linux-headers-3.13.0-74/include/uapi/asm-generic/errno.h Use uname-a to find out what kernel you are running, and use that in place of the 3.13.0-74 that is in my example. share|improve this answer answered Jan 3 at 11:19 Keith 1 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign

Orig file: v2.2.17/Documentation/usb/error-codes.txt Orig date: Thu Jan 1 01:00:00 1970 diff -u --new-file --recursive --exclude-from /usr/src/exclude v2.2.17/Documentation/usb/error-codes.txt linux/Documentation/usb/error-codes.txt @@ -0,0 +1,108 @@ +$Id: README.error-codes,v 1.1 1999/12/14 14:03:02 fliegl Exp $ + +This is the documentation of (hopefully) all possible error codes (and +their interpretation) that can be returned from the hostcontroller driver +and from usbcore. + +NOTE: +The USB_ST_* codes are deferred and are only listed for compatibility, new +software should use only -E* instead! + + + +************************************************************************** +* Error codes returned by usb_submit_urb * +************************************************************************** + +Non-USB-specific: + +USB_ST_NOERROR +0 URB submission went fine + +-ENOMEM no memory for allocation of internal structures + +USB-specific: + +-ENODEV specified USB-device or bus doesn't exist + +-ENXIO specified endpoint doesn't exist on the device + +USB_ST_URB_INVALID_ERROR +-EINVAL a) Invalid transfer type specified (or not supported) + b) Invalid interrupt interval (0<=n<256) + c) more than one interrupt packet requested + +-EAGAIN a) specified ISO start frame too early + b) (using ISO-ASAP) too much scheduled for the future + wait some time and try again. + +-EFBIG too much ISO frames requested (currently uhci>900) + +-EPIPE specified pipe-handle is already stalled + +-EMSGSIZE endpoint message size is zero, do interface/alternate setting + + +************************************************************************** +* Error codes returned by in urb->status * +* or in iso_frame_desc[n].status (for ISO) * +************************************************************************** + +USB_ST_NOERROR +0 Transfer completed successfully + +USB_ST_URB_KILLED +-ENOENT URB was canceled by unlink_urb + +USB_ST_URB_PENDING +-EINPROGRESS URB still pending, no results yet + (actually no error until now;-) + +USB_ST_BITSTUFF +USB_ST_INTERNALERROR +-EPROTO a) bitstuff error + b) unknown USB error + +USB_ST_CRC +-EILSEQ CRC mismatch + +-EPIPE a) babble detect + b) endpoint stalled + +USB_ST_BUFFERUNDERRUN +-ENOST buffer error + +USB_ST_NORESPONSE +USB_ST_TIMEOUT +-ETIMEDOUT transfer timed out, NAK + +USB_ST_REMOVED +-ENODEV device was removed + +USB_ST_SHORT_PACKET +-EREMOTEIO short packet detected + +USB_ST_P