[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54BD1B70.5090305@linux.intel.com>
Date: Mon, 19 Jan 2015 16:57:52 +0200
From: Mathias Nyman <mathias.nyman@...ux.intel.com>
To: Josh Boyer <jwboyer@...oraproject.org>,
Robert Hancock <hancockrwd@...il.com>
CC: Greg KH <gregkh@...uxfoundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux-usb <linux-usb@...r.kernel.org>
Subject: Re: 3.18 regression: Error while assigning device slot ID, USB3 devices
not detected
On 19.01.2015 15:47, Josh Boyer wrote:
> On Mon, Jan 19, 2015 at 8:33 AM, Greg KH <gregkh@...uxfoundation.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@...uxfoundation.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists