Problem in xHCI Host Controller, usb3

[Marcin Janowski]

When i connect any device to usb3 port in dmesg i have:
[ 2.860792] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.860797] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 2.861029] xhci_hcd 0000:05:00.0: irq 41 for MSI/MSI-X
[ 2.861035] xhci_hcd 0000:05:00.0: irq 42 for MSI/MSI-X
[ 2.861041] xhci_hcd 0000:05:00.0: irq 43 for MSI/MSI-X
[ 2.861046] xhci_hcd 0000:05:00.0: irq 44 for MSI/MSI-X
[ 2.861051] xhci_hcd 0000:05:00.0: irq 45 for MSI/MSI-X
[ 2.861203] usb usb3: Manufacturer: Linux 3.13.0-24-generic xhci_hcd
[ 2.861370] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 2.861373] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 2.864438] usb usb4: Manufacturer: Linux 3.13.0-24-generic xhci_hcd
[14313.782879] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[14446.166980] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[41482.213335] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[48164.448973] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[48255.410114] usb 3-1: new full-speed USB device number 6 using xhci_hcd
[48260.611548] xhci_hcd 0000:05:00.0: Timeout while waiting for address device command
[48283.799187] xhci_hcd 0000:05:00.0: Stopped the command ring failed, maybe the host is dead
[48283.873175] xhci_hcd 0000:05:00.0: Host not halted after 16000 microseconds.
[48283.873178] xhci_hcd 0000:05:00.0: Abort command ring failed
[48283.874290] xhci_hcd 0000:05:00.0: HC died; cleaning up
[48289.072908] xhci_hcd 0000:05:00.0: Timeout while waiting for a slot
[48289.072922] xhci_hcd 0000:05:00.0: Abort the command ring, but the xHCI is dead.
[48294.070375] xhci_hcd 0000:05:00.0: Timeout while waiting for a slot
[48294.070388] xhci_hcd 0000:05:00.0: Abort the command ring, but the xHCI is dead.
[48299.067776] xhci_hcd 0000:05:00.0: Timeout while waiting for a slot
[48299.067790] xhci_hcd 0000:05:00.0: Abort the command ring, but the xHCI is dead.

I found this about this bug:
"This may be a known regression. Please try reverting these commits:

7dd09a1af2c7 xhci: replace xhci_write_64() with writeq()
e8b373326d8e xhci: replace xhci_read_64() with readq()

The reverts will be sent to the USB subsystem maintainer's tree today,
and will land in 3.14-rc2."
from: http://permalink.gmane.org/gmane.linux.usb.general/102627

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: wmp 5654 F.... pulseaudio
                      wmp 10950 F.... pulseaudio
CurrentDesktop: KDE
Date: Sun Sep 28 10:26:01 2014
HibernationDevice: RESUME=UUID=30c5dceb-9e4b-4fed-aede-2d8abfbcd8aa
InstallationDate: Installed on 2013-03-14 (562 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121006)
MachineType: Acer Aspire 3830TG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=adaa4e7b-97d1-49fe-be92-1b9755930eb6 ro quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.6
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-22 (158 days ago)
dmi.bios.date: 08/14/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM30_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.modalias: dmi:bvnAcer:bvrV1.12:bd08/14/2012:svnAcer:pnAspire3830TG:pvrV1.12:rvnAcer:rnJM30_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12:
dmi.product.name: Aspire 3830TG
dmi.product.version: V1.12
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Marcin Janowski, thank you for reporting this and helping make Ubuntu better. When you personally tested reverting the commit mentioned, what effect did it have?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]