From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209411] When retrieving string descriptor from mobile device returns eproto error
Date: Wed, 30 Sep 2020 15:15:13 +0000 [thread overview]
Message-ID: <bug-209411-208809-QiOCtjqz4p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209411-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209411
--- Comment #15 from rachithas104@gmail.com ---
(In reply to Alan Stern from comment #14)
> You can get the descriptor values by running "lsusb -v".
>
> If the phone fails when you reset it, you should change your program. Don't
> issue the reset command!
>
> Why did you open this bug report in the first place?
Since the device with 4.14 kernel works and 4.19 fails,I opened whether there
is any protocol change ,so that I can change my program accrordingly,I am
seeing this in syslog when issued reset command
kernel: [85237.846504] usb 1-1.2: reset high-speed USB device number 19 using
ehci-pci
kernel: [85238.146480] usb 1-1.2: device descriptor read/64, error -71
kernel: [85238.558551] usb 1-1.2: reset high-speed USB device number 19 using
ehci-pci
kernel: [85239.062496] usb 1-1.2: device not accepting address 19, error -71
kernel: [85239.350498] usb 1-1.2: reset high-speed USB device number 19 using
ehci-pci
kernel: [85240.544425] usb 1-1.2: usbfs: USBDEVFS_CONTROL failed cmd ctxusb
rqt 128 rq 6 len 255 ret -71
0 kernel: [85240.838479] usb 1-1.2: reset high-speed USB device number 19 using
ehci-pci
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-30 15:15 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 17:51 [Bug 209411] New: When retrieving string descriptor from mobile device returns eproto error bugzilla-daemon
2020-09-28 17:49 ` [Bug 209411] " bugzilla-daemon
2020-09-28 17:49 ` [Bug 209411] New: " Greg KH
2020-09-29 14:35 ` [Bug 209411] " bugzilla-daemon
2020-09-29 14:38 ` bugzilla-daemon
2020-09-29 16:04 ` bugzilla-daemon
2020-09-29 16:23 ` bugzilla-daemon
2020-09-29 16:24 ` bugzilla-daemon
2020-09-29 16:40 ` bugzilla-daemon
2020-09-30 11:05 ` bugzilla-daemon
2020-09-30 11:06 ` bugzilla-daemon
2020-09-30 11:06 ` bugzilla-daemon
2020-09-30 14:47 ` bugzilla-daemon
2020-09-30 14:52 ` bugzilla-daemon
2020-09-30 14:53 ` bugzilla-daemon
2020-09-30 15:04 ` bugzilla-daemon
2020-09-30 15:15 ` bugzilla-daemon [this message]
2020-09-30 15:37 ` bugzilla-daemon
2020-09-30 15:41 ` bugzilla-daemon
2020-09-30 15:43 ` bugzilla-daemon
2020-09-30 15:44 ` bugzilla-daemon
2020-09-30 19:25 ` bugzilla-daemon
2020-10-02 16:02 ` bugzilla-daemon
2020-10-02 16:04 ` bugzilla-daemon
2020-10-02 16:46 ` bugzilla-daemon
2020-10-05 13:53 ` bugzilla-daemon
2020-10-05 14:38 ` bugzilla-daemon
2020-10-05 14:48 ` bugzilla-daemon
2020-10-07 4:54 ` bugzilla-daemon
2020-10-10 18:02 ` bugzilla-daemon
2020-10-11 1:15 ` bugzilla-daemon
2020-10-11 4:27 ` bugzilla-daemon
2020-10-11 8:13 ` bugzilla-daemon
2020-10-11 14:13 ` bugzilla-daemon
2020-10-12 12:49 ` bugzilla-daemon
2020-10-12 12:50 ` bugzilla-daemon
2020-10-12 14:47 ` bugzilla-daemon
2020-10-12 16:25 ` bugzilla-daemon
2020-10-12 16:49 ` bugzilla-daemon
2020-10-12 18:30 ` bugzilla-daemon
2020-10-12 18:50 ` bugzilla-daemon
2020-10-13 0:24 ` bugzilla-daemon
2020-10-13 4:09 ` bugzilla-daemon
2020-10-13 5:10 ` bugzilla-daemon
2020-10-13 6:02 ` bugzilla-daemon
2020-10-13 6:21 ` bugzilla-daemon
2020-10-13 6:25 ` bugzilla-daemon
2020-10-13 6:37 ` bugzilla-daemon
2020-10-13 17:51 ` bugzilla-daemon
2020-10-13 17:55 ` bugzilla-daemon
2020-10-13 17:56 ` bugzilla-daemon
2020-10-13 17:58 ` bugzilla-daemon
2020-10-14 3:56 ` bugzilla-daemon
2020-10-14 13:24 ` bugzilla-daemon
2020-10-14 18:43 ` bugzilla-daemon
2020-10-14 18:49 ` bugzilla-daemon
2020-10-14 18:56 ` bugzilla-daemon
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=bug-209411-208809-QiOCtjqz4p@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@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).