linux-kernel - Re: 3.18 regression: Error while assigning device slot ID, USB3 devices not detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150118062531.GA8968@kroah.com>
Date:	Sat, 17 Jan 2015 22:25:31 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	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 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.

thanks,

greg k-h
--
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/