From: Adrian Bunk <bunk@stusta.de>
To: Marc Perkel <marc@perkel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: usb device descriptor read/64, error -110
Date: Tue, 31 Oct 2006 00:54:30 +0100 [thread overview]
Message-ID: <20061030235429.GO27968@stusta.de> (raw)
In-Reply-To: <45468ABC.1060100@perkel.com>
On Mon, Oct 30, 2006 at 03:29:00PM -0800, Marc Perkel wrote:
> Running the latest FC6 kernel based on 2.6.18.1. What does this error mean?
>
> device descriptor read/64, error -110
>
> Is this a kernel bug? Thanks in advance?
That's a timeout.
Your bug report lacks any any information for further debugging your
problem.
- When does it occur?
- What is failing?
- Please send the output of "dmesg -s 1000000".
And please read and follow REPORTING-BUGS in the kernel sources before
sending your next bug report.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-10-30 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 23:29 usb device descriptor read/64, error -110 Marc Perkel
2006-10-30 23:54 ` Adrian Bunk [this message]
2006-10-30 23:59 ` Marc Perkel
2006-10-31 1:14 ` Adrian Bunk
2006-10-31 1:20 ` Marc Perkel
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=20061030235429.GO27968@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
/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