usb 3-2: device descriptor read/64, error -71

Bug #1565292 reported by Cristian Aravena Romero
This bug report is a duplicate of:  Bug #1437492: boot stalls on USB detection errors. Edit Remove
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Committed
High
Tim Gardner
Xenial
In Progress
Undecided
Tim Gardner
Yakkety
Fix Committed
High
Tim Gardner

Bug Description

dmesg:

[ 98.157161] usb 3-2: device descriptor read/64, error -71
[ 98.429199] usb 3-2: device descriptor read/64, error -71
[ 98.645163] usb 3-2: new low-speed USB device number 8 using xhci_hcd
[ 98.813245] usb 3-2: device descriptor read/64, error -71
[ 99.085274] usb 3-2: device descriptor read/64, error -71
[ 99.301244] usb 3-2: new low-speed USB device number 9 using xhci_hcd
[ 99.302701] usb 3-2: Device not responding to setup address.
[ 99.506725] usb 3-2: Device not responding to setup address.
[ 99.709269] usb 3-2: device not accepting address 9, error -71
[ 99.821261] usb 3-2: new low-speed USB device number 10 using xhci_hcd
[ 99.822718] usb 3-2: Device not responding to setup address.
[ 100.026715] usb 3-2: Device not responding to setup address.
[ 100.229308] usb 3-2: device not accepting address 10, error -71
[ 100.229444] usb usb3-port2: unable to enumerate USB device
[ 125.831555] usb 3-1: new full-speed USB device number 11 using xhci_hcd
[ 125.943618] usb 3-1: device descriptor read/64, error -71
[ 126.159606] usb 3-1: device descriptor read/64, error -71
[ 126.375599] usb 3-1: new full-speed USB device number 12 using xhci_hcd
[ 126.487663] usb 3-1: device descriptor read/64, error -71
[ 126.703656] usb 3-1: device descriptor read/64, error -71
[ 126.919658] usb 3-1: new full-speed USB device number 13 using xhci_hcd
[ 126.919969] usb 3-1: Device not responding to setup address.
[ 127.123998] usb 3-1: Device not responding to setup address.
[ 127.327681] usb 3-1: device not accepting address 13, error -71
[ 127.439718] usb 3-1: new full-speed USB device number 14 using xhci_hcd
[ 127.440049] usb 3-1: Device not responding to setup address.
[ 127.644028] usb 3-1: Device not responding to setup address.
[ 127.847719] usb 3-1: device not accepting address 14, error -71
[ 127.847819] usb usb3-port1: unable to enumerate USB device

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: caravena 1792 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sat Apr 2 12:35:30 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (251 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-16-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-16-generic N/A
 linux-backports-modules-4.4.0-16-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 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'.

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/v4.6-rc2-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems like the issue fixed with https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/include/linux/usb.h?id=feb26ac31a2a5cb88d86680d9a94916a6343e9e6 and which might be the cause of upower delays/locks and unity-settings-daemon segfaults users are seeing on xenial

Changed in linux (Ubuntu):
importance: Medium → High
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Tim Gardner (timg-tpi)
status: New → In Progress
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Yakkety):
status: Confirmed → Fix Committed
assignee: nobody → Tim Gardner (timg-tpi)
tags: added: kernel-da-key
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.