4.13 USB 03f0:3a1d HP hs2340 HSPA+ MobileBroadband fails to resume from S3 suspend

Bug #1744083 reported by TJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

On 16.04 with linux-image-lowlatency-hwe-16.04 a mini-PCIe form-factor GSM cellular modem fails to resume after S3 suspend:

[ 6632.711063] PM: resume of devices complete after 1659.009 msecs
[ 6632.711290] usb 7-2.1:1.0: rebind failed: -517
[ 6632.711306] usb 7-2.1:1.1: rebind failed: -517
[ 6632.711844] PM: Finishing wakeup.

lsusb
Bus 002 Device 003: ID 03f0:3a1d Hewlett-Packard
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tj 3968 F.... pulseaudio
CurrentDesktop: LXDE
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
MachineType: Dell Inc. XPS M1530
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-lowlatency root=/dev/mapper/VG_OS-ubuntu_16.04_rootfs ro pci=use_crs,realloc,assign-busses,pcie_scan_all acpi_osi=! "acpi_osi=Windows 2006" splash crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-lowlatency N/A
 linux-backports-modules-4.13.0-25-lowlatency N/A
 linux-firmware 1.157.15
Tags: xenial
Uname: Linux 4.13.0-25-lowlatency x86_64
UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago)
UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd plugdev root sudo users video wireshark
_MarkForUpload: True
dmi.bios.date: 11/19/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1530
dmi.sys.vendor: Dell Inc.

Revision history for this message
TJ (tj) wrote :
Revision history for this message
TJ (tj) wrote :
tags: added: apport-collected xenial
description: updated
Revision history for this message
TJ (tj) wrote : AlsaInfo.txt

apport information

Revision history for this message
TJ (tj) wrote : CRDA.txt

apport information

Revision history for this message
TJ (tj) wrote : CurrentDmesg.txt

apport information

Revision history for this message
TJ (tj) wrote : IwConfig.txt

apport information

Revision history for this message
TJ (tj) wrote : JournalErrors.txt

apport information

Revision history for this message
TJ (tj) wrote : Lspci.txt

apport information

Revision history for this message
TJ (tj) wrote : Lsusb.txt

apport information

Revision history for this message
TJ (tj) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
TJ (tj) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
TJ (tj) wrote : ProcEnviron.txt

apport information

Revision history for this message
TJ (tj) wrote : ProcInterrupts.txt

apport information

Revision history for this message
TJ (tj) wrote : ProcModules.txt

apport information

Revision history for this message
TJ (tj) wrote : PulseList.txt

apport information

Revision history for this message
TJ (tj) wrote : RfKill.txt

apport information

Revision history for this message
TJ (tj) wrote : UdevDb.txt

apport information

Revision history for this message
TJ (tj) wrote : WifiSyslog.txt

apport information

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-rc8

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

Confirmed the device is still found in 4.4.0-110 so looks like a regression. I'll test 41.5rc8 next.

Revision history for this message
TJ (tj) wrote :

Also works for 4.15.0-041500rc8-lowlatency (although now nouveau fails!)

Revision history for this message
TJ (tj) wrote :

Working so far with 4.13.0-30-lowlatency.

Beginning to suspect either it only happens after multiple suspend/resume cycles or the hardware got itself confused.

Will keep watch and investigate if it recurs.

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.