From: Yan Seiner <yan@seiner.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: FAQ Somewhere? USB error messges
Date: Thu, 19 Feb 2009 12:59:28 +0000 [thread overview]
Message-ID: <499D57B0.90702@seiner.com> (raw)
In-Reply-To: <499CCE54.2020704@seiner.com>
Greg KH wrote:
> On Wed, Feb 18, 2009 at 07:13:24PM -0800, Yan Seiner wrote:
>
>> I have a device that has fallen off my usb hub. It now refuses to connect
>> with:
>>
>> Feb 18 18:57:21 selene kernel: [217569.165436] usb 2-4.4.4.4.4.3: new low
>> speed USB device using ehci_hcd and address 55
>> Feb 18 18:57:22 selene kernel: [217569.572035] usb 2-4.4.4.4.4.3: device
>> not accepting address 55, error -71
>> Feb 18 18:57:22 selene kernel: [217569.572366] hub 2-4.4.4.4.4:1.0: unable
>> to enumerate USB device on port 3
>>
>> I'm fairly sure it's not the device as I have two identical ones that work
>> fine in other hubs. I'm fairly sure it's not the hub as I have other
>> devices that work fine on that hub.
>>
>> So now I need to figure out what that error message means. Where can I
>> look up the error code?
>>
>
> Documentation/usb/error-codes.txt
>
>
That says things like:
-ENODEV specified USB-device or bus doesn't exist
-ENOENT specified interface or endpoint does not exist or
is not enabled
It has no information on translating 71 to E*. Unfortunately that
doesn't tell me what 71 is about. Grepping /usr/include for some of
those errors *still* doesn't tell me what error 71 is as it doesn't
appear anywhere.
Is there any reason why the hotplug subsystem has to throw those cryptic
errors with no pointers to any docs where we might be able to decipher
them? We're in userland; we don't deal with this on a daily basis, and
we have no clue where any of the info we need to understand those errors
lies.
--Yan
next prev parent reply other threads:[~2009-02-19 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 3:13 FAQ Somewhere? USB error messges Yan Seiner
2009-02-19 4:07 ` Greg KH
2009-02-19 12:59 ` Yan Seiner [this message]
2009-02-19 15:43 ` Greg KH
2009-02-19 16:11 ` Randy Dunlap
2009-02-19 16:20 ` Yan Seiner
2009-02-19 16:22 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=499D57B0.90702@seiner.com \
--to=yan@seiner.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).