From: "Renato S. Yamane" <renatoyamane@mandic.com.br>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Renato S. Yamane" <renatoyamane@mandic.com.br>,
Jiri Kosina <jikos@jikos.cz>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] Error -71 on device descriptor read/all
Date: Wed, 20 Jun 2007 08:07:13 -0300 [thread overview]
Message-ID: <46790A61.5070107@mandic.com.br> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0706191456030.2552-100000@iolanthe.rowland.org>
Alan Stern wrote:
> Does the mouse work correctly, even with ehci-hcd loaded?
Yes.
And sorry, but I don't have any other USB2.0 device to test.
I try with my cel phone (Motorola V3i) in this night (GMT-3).
> If it does then don't worry about the -71 error. It appears to be
> transient and it's not necessarily fatal.
In my dmesg today, I see this:
usb 1-1: can't set config #1, error -71
When I remove and input (again) my Mouse, I see this in /var/log/messages:
kernel: usb 1-1: USB disconnect, address 3
kernel: usb 1-1: new low speed USB device using uhci_hcd and address 4
kernel: usb 1-1: configuration #1 chosen from 1 choice
kernel: input: Microsoft Microsoft 3-Button Mouse with IntelliEye? as
/class/input/input8
kernel: input: USB HID v1.00 Mouse [Microsoft Microsoft 3-Button Mouse
with IntelliEye?] on usb-0000:00:1d.0-1
Regards,
Renato S. Yamane
next prev parent reply other threads:[~2007-06-20 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 14:45 Renato S. Yamane
2007-06-19 14:58 ` Jiri Kosina
2007-06-19 15:37 ` Renato S. Yamane
2007-06-19 15:55 ` Jiri Kosina
2007-06-19 18:59 ` [linux-usb-devel] " Alan Stern
2007-06-20 11:07 ` Renato S. Yamane [this message]
2007-06-20 14:06 ` Alan Stern
2007-06-20 17:29 ` Chuck Ebbert
2007-06-19 16:17 ` Chuck Ebbert
2007-06-19 17:02 ` [linux-usb-devel] " Oliver Neukum
2007-06-19 17:36 ` Paul Walmsley
2007-06-19 18:56 ` Oliver Neukum
2007-06-19 19:04 ` Alan Stern
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=46790A61.5070107@mandic.com.br \
--to=renatoyamane@mandic.com.br \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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
Powered by JetHome