USB devices not recognized after suspend to RAM

Bug #1744337 reported by Wolf Rogner
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

After a fresh reboot, USB devices / hard disks are recognized correctly.

After the first suspend to RAM, this recognition does not work any more.

USB Flash drives are recognized as xhci_hdc:
...
Jan 19 16:29:39 mbpr13b kernel: [ 4312.095869] usb 2-1: new SuperSpeed USB device number 20 using xhci_hcd
Jan 19 16:29:44 mbpr13b kernel: [ 4317.199585] usb 2-1: device descriptor read/8, error -110
Jan 19 16:29:44 mbpr13b kernel: [ 4317.307436] usb 2-1: new SuperSpeed USB device number 20 using xhci_hcd
Jan 19 16:29:49 mbpr13b kernel: [ 4322.575395] usb 2-1: device descriptor read/8, error -110
Jan 19 16:29:49 mbpr13b kernel: [ 4322.891260] usb 2-1: new SuperSpeed USB device number 21 using xhci_hcd
Jan 19 16:29:55 mbpr13b kernel: [ 4327.951076] usb 2-1: device descriptor read/8, error -110
Jan 19 16:29:55 mbpr13b kernel: [ 4328.058970] usb 2-1: new SuperSpeed USB device number 21 using xhci_hcd
...
but do not mount

Hard disks freeze the system

Android Phones don't get recognized as xhci_hdc instead of an external storage device:
...
Jan 19 16:34:17 mbpr13b kernel: [ 4589.934444] usb 1-1: new high-speed USB device number 4 using xhci_hcd
Jan 19 16:34:22 mbpr13b kernel: [ 4595.066102] usb 1-1: device descriptor read/64, error -110
Jan 19 16:34:37 mbpr13b kernel: [ 4610.681476] usb 1-1: device descriptor read/64, error -110
Jan 19 16:34:37 mbpr13b kernel: [ 4610.909265] usb 1-1: new high-speed USB device number 5 using xhci_hcd
Jan 19 16:34:43 mbpr13b kernel: [ 4616.057120] usb 1-1: device descriptor read/64, error -110

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-30-generic 4.13.0-30.33
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: wolf 1317 F.... pulseaudio
 /dev/snd/controlC0: wolf 1317 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 16:30:16 2018
HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
InstallationDate: Installed on 2017-10-20 (91 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-30-generic N/A
 linux-backports-modules-4.13.0-30-generic N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0171.B00.1708080033
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Wolf Rogner (war-rsb) wrote :
Revision history for this message
Wolf Rogner (war-rsb) wrote :

lsusb does not report devices

MicroPython board is not recognized either

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) 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.15 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.15-rc9

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.