From: Parag Warudkar <kernel-stuff@comcast.net>
To: Jeff Wiegley <jeffw@cyte.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10 USB devices generate descriptor read error?
Date: Fri, 28 Jan 2005 21:20:08 -0500 [thread overview]
Message-ID: <41FAF2D8.1060207@comcast.net> (raw)
In-Reply-To: <41FAEF8F.9010809@cyte.com>
Known one - It's non fatal. All your devices should work fine. If you
want you can try loading usbcore.ko with module parameter
old_scheme_first=y and see if it goes away.
Parag
Jeff Wiegley wrote:
> Is anybody else having a similar problem as the
> following...
>
> My USB keydrives use to work fine in 2.6.9.
> Since I upgraded to 2.6.10 now they just
> generate a device descriptor read error.
>
> Specifically:
>
> /var/log/kern.log.0:Jan 26 18:18:18 mail kernel: usb 4-2.1:
> device descriptor read/64, error -32
>
> Also I noticed that a new Sigmatel based USB IRDA
> device also produces similar messages...
>
> /var/log/kern.log:Jan 27 12:31:19 mail kernel: usb 2-2: device
> descriptor read/64, error -71
>
> Is this a known problem or is it just me?
>
> I noticed that the precompiled debian 2.6.10 kernel
> works with at least the usb flash drive ok. But my
> compiled version produces the above.
>
> But I don't think I changed any relevant kernel config
> items from 2.6.9 to 2.6.10 and I've compiled lots of
> USB enabled kernels before so I'd like to think I'm
> not an idiot but maybe I missed a new option or
> something.
>
> Please help,
>
> - Jeff
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2005-01-29 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 2:06 2.6.10 USB devices generate descriptor read error? Jeff Wiegley
2005-01-29 2:20 ` Parag Warudkar [this message]
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=41FAF2D8.1060207@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=jeffw@cyte.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.