Date:	Mon, 19 Jan 2015 18:53:30 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Josh Boyer <jwboyer@...oraproject.org>
Cc:	Mathias Nyman <mathias.nyman@...ux.intel.com>,
	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 Mon, Jan 19, 2015 at 9:40 AM, Josh Boyer <jwboyer@...oraproject.org> wrote:
> On Mon, Jan 19, 2015 at 9:57 AM, Mathias Nyman
> <mathias.nyman@...ux.intel.com> wrote:
>> 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
>
> OK.  We're tracking this in the bug Robert filed here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1183289
>
> The patch should be in the next Fedora kernel build, so hopefully we
> can get back to you soon.

The patched build seems to fix the problem with the ports not
recognizing SuperSpeed devices. I do get these errors in dmesg now
though, which also weren't in 3.17:

[    0.881967] usb: failed to peer 1-9-port1 and 2-5-port1 by location
(1-9-port1:none) (2-5-port1:usb1-port11)
[    0.881968] usb 1-9-port1: failed to peer to 2-5-port1 (-16)
[    0.881969] usb: port power management may be unreliable
[    0.881993] usb: failed to peer 1-9-port2 and 2-5-port2 by location
(1-9-port2:none) (2-5-port2:usb1-port12)
[    0.881994] usb 1-9-port2: failed to peer to 2-5-port2 (-16)
[    0.882015] usb: failed to peer 1-9-port3 and 2-5-port3 by location
(1-9-port3:none) (2-5-port3:usb1-port13)
[    0.882016] usb 1-9-port3: failed to peer to 2-5-port3 (-16)
[    0.882037] usb: failed to peer 1-9-port4 and 2-5-port4 by location
(1-9-port4:none) (2-5-port4:usb1-port14)
[    0.882038] usb 1-9-port4: failed to peer to 2-5-port4 (-16)

Full dmesg is attached to this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1183289
--
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