From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Josh Boyer <jwboyer@fedoraproject.org>,
Robert Hancock <hancockrwd@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux-usb <linux-usb@vger.kernel.org>
Subject: Re: 3.18 regression: Error while assigning device slot ID, USB3 devices not detected
Date: Mon, 19 Jan 2015 16:57:52 +0200 [thread overview]
Message-ID: <54BD1B70.5090305@linux.intel.com> (raw)
In-Reply-To: <CA+5PVA5bTAh+qi7VjUE8XUx-XvgmzoV0RvrqTkBBR_kf+D-CKQ@mail.gmail.com>
On 19.01.2015 15:47, Josh Boyer wrote:
> On Mon, Jan 19, 2015 at 8:33 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> On Mon, Jan 19, 2015 at 08:28:19AM -0500, Josh Boyer wrote:
>>> On Sun, Jan 18, 2015 at 1:25 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>>>> On Sun, Jan 18, 2015 at 12:08:18AM -0600, Robert Hancock wrote:
>>>>> I've got an Intel Haswell-based system with a Gigabyte Z87X-D3H motherboard
>>>>> under Fedora 21. After updating to the 3.18.2-200 Fedora kernel, I noticed
>>>>> some errors in dmesg and at least some of my USB3 ports don't recognize any
>>>>> USB3 devices plugged into them:
>>>>>
>>>>> [ 0.560838] xhci_hcd 0000:00:14.0: Error while assigning device slot ID
>>>>> [ 0.560912] xhci_hcd 0000:00:14.0: Max number of devices this xHCI host
>>>>> supports is 32.
>>>>> [ 0.560990] usb usb2-port2: couldn't allocate usb_device
>>>>> [ 0.561098] xhci_hcd 0000:00:14.0: Error while assigning device slot ID
>>>>> [ 0.561163] xhci_hcd 0000:00:14.0: Max number of devices this xHCI host
>>>>> supports is 32.
>>>>> [ 0.561239] usb usb2-port5: couldn't allocate usb_device
>>>>> [ 0.561344] xhci_hcd 0000:00:14.0: Error while assigning device slot ID
>>>>> [ 0.561409] xhci_hcd 0000:00:14.0: Max number of devices this xHCI host
>>>>> supports is 32.
>>>>> [ 0.561484] usb usb2-port6: couldn't allocate usb_device
>>>>>
>>>>> This worked fine under 3.17. Is this a known problem?
>>>>
>>>> Yes it is, should be fixed in Linus's tree now and will be backported to
>>>> the latest 3.18-stable tree in a week or so.
>>>
>>> Do you happen to know the commit id?
>>
>> f161ead70fa6a62e432dff6e9dab8e3cfbeabea6
>
> Thanks!
>
Tell me if this fixed the issue.
I got this gut feeling this might be something else.
It should have failed in 3.17 as well
-Mathias
next prev parent reply other threads:[~2015-01-19 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 6:08 3.18 regression: Error while assigning device slot ID, USB3 devices not detected Robert Hancock
2015-01-18 6:25 ` Greg KH
2015-01-19 13:28 ` Josh Boyer
2015-01-19 13:33 ` Greg KH
2015-01-19 13:47 ` Josh Boyer
2015-01-19 14:57 ` Mathias Nyman [this message]
2015-01-19 15:40 ` Josh Boyer
2015-01-20 0:53 ` Robert Hancock
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=54BD1B70.5090305@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hancockrwd@gmail.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.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