From: Peter Stuge <peter@stuge.se>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [GIT PULL] USB driver fixes for 3.18-rc7
Date: Sun, 30 Nov 2014 23:15:24 +0100 [thread overview]
Message-ID: <20141130221524.20566.qmail@stuge.se> (raw)
In-Reply-To: <CA+55aFyJunLbQPBgUf4rhZN0vbaj7hpK3Jwqwqf-S7A2-LLhFA@mail.gmail.com>
Linus Torvalds wrote:
> I seem to get this problem possibly more commonly at boot these days:
> usb 1-6: device descriptor read/64, error -71
> xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
> usb 1-6: hub failed to enable device, error -22
Since my upgrade to 98e8d2e0 from something a bit older I also get
-71 error messages on boot and on resume, however this is older
hardware with only ehci-pci.
In my case some of the descriptors coming back from the device are bogus
when the device is first seen. The device then disconnects, and when it
is seen again by the kernel, nearly one second later, the descriptors
are fine and there are no errors. vid/pid change from hardware ODM to
OEM, suggesting that my device simply isn't ready when Linux first
talks with it.
//Peter
next prev parent reply other threads:[~2014-11-30 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 22:40 Greg KH
2014-11-30 19:47 ` Linus Torvalds
2014-11-30 22:15 ` Peter Stuge [this message]
2014-12-02 18:18 ` Greg KH
2014-12-03 16:02 ` Mathias Nyman
2014-12-11 18:47 ` Greg KH
2014-12-12 17:45 ` Mathias Nyman
2014-12-12 17:58 ` [PATCH] xhci: Check if slot is already in default state before moving it there Mathias Nyman
2015-04-07 16:32 ` [GIT PULL] USB driver fixes for 3.18-rc7 Tony Luck
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=20141130221524.20566.qmail@stuge.se \
--to=peter@stuge.se \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®