[LENOVO 20A7005JMB] suspend/resume failure

[Void]

It seems the resume only works with usb3 disabled

cat /proc/version_signature => Ubuntu 3.13.0-17.37-generic 3.13.6

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

------

When going to suspend on an X1 Carbon (20a7) the suspend seems to work, however, the adaptives keys stays on, and the system does not respond to power key press.

Needing forced shutdown instead this might be related with usb2/usb3 automatic routing

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: boot/vmlinuz-3.13.0-17-generic]
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lightdm 1399 F.... pulseaudio
                      xavier 2013 F.... pulseaudio
 /dev/snd/controlC1: lightdm 1399 F.... pulseaudio
                      xavier 2013 F.... pulseaudio
Date: Thu Mar 13 08:59:31 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2014-03-12 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312)
InterpreterPath: /usr/bin/python3.4
MachineType: LENOVO 20A7005JMB
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=b414b609-9cf2-4f83-a337-5ff6bad17ac9 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-17-generic N/A
 linux-backports-modules-3.13.0-17-generic N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [LENOVO 20A7005JMB] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/13/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GRET32WW (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20A7005JMB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGRET32WW(1.09):bd02/13/2014:svnLENOVO:pn20A7005JMB:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7005JMB:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20A7005JMB
dmi.product.version: ThinkPad X1 Carbon 2nd
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Void (xdecock)]

More infos:

There is 3 settings in bios regarding usb3:

Disabled, enabled, auto

The system only suspend on disabled.

PS: thinkpad_acpi is blacklisted to keep access to the adaptive bar altough the patch on the thinkpad_acpi list does work

[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.13 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.14-rc6-trusty/

[Void (xdecock)]

High,

using 3.13 Upstream line, the bug is the same, using 3.14 Xorg cannot start the screen

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel