On Thu, Oct 10, 2013 at 09:32:24AM -0000, Colin King wrote:
> Steve, just to factor out some of the pm-utils complexity can you boot
> into 3.11.0-4 and switch to a console and try:
> echo mem | sudo tee /sys/power/state
> and see if that works.
That's a great question. Last night, my results were:
- booted into 3.11.0-4
- switched to VT1
- laptop plugged into the dock (so, on A/C power)
- echo mem > /sys/power/state
- worked, resumed successfully.
- ran pm-suspend
- worked, resumed successfully.
- unplugged the laptop from the dock
- ran pm-suspend again
- failed
- booted into 3.11.0-12
- kept the laptop unplugged from the dock
- switched to VT1
- echo mem > /sys/power/state
- resumed successfully
- pm-suspend
- resumed successfully
- switched to X
- pm-suspend
- failed
So I took some time today to test a bit more systematically, and take notes
as I went. The notes are below, but the summary is: whatever has changed to
make suspend unreliable on my laptop, it appears *not* to be the OS. I've
rolled back the kernel, and I've even rolled back userspace, to raring, and
the problem is still reproducible.
I wonder whether Ubuntu didn't do something to trigger this behavior change,
but if it did, it's now persistent somewhere in nvram.
So if nobody else is reporting similar problems, I guess this is specific to
my hardware and not a kernel bug.
3.11.0-12: docked, X, pm-suspend: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on -
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, X, pm-suspend: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on; takes a long time to POST; does not reach the bootloader -
- power off -
- power on -
3.11.0-4: docked, console, echo mem: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, console, pm-suspend: success
3.11.0-4: docked, console, pm-suspend: fail
- power on -
3.11.0-4: docked, console, pm-suspend: fail
- power on -
3.11.0-4: docked, console, pm-suspend: fail
- power on -
3.11.0-4: docked, console, pm-suspend: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on -
3.11.0-4: docked, console, echo mem: fail
- power on -
3.8.0-19: docked, console, echo mem: success
3.8.0-19: docked, console, echo mem: fail
- power on -
3.8.0-19: docked, console, echo mem: success
3.8.0-19: docked, console, echo mem: success
3.8.0-19: docked, console, echo mem: success, but video did not come back up
after resume
- power off -
- power on -
3.8.0-19: docked, console, echo mem: success
3.8.0-19: docked, console, echo mem: fail
- power on -
3.8.0-19: docked, console, echo mem: fail
- power on -
3.8.0-19: undocked, console, echo mem: success, but video did not come back up
after resume
- power off -
- power on -
3.8.0-19: docked, console, echo mem: fail
- power on -
reinstalled raring on a separate partition.
3.8.0-19: undocked, console, echo mem: fail
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1228406
Title:
[LENOVO 3249CTO] suspend/resume failure
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The laptop frequently suspends/resumes successfully; it's been
suspended/resumed probably at least a dozen times since the last
reboot. I've seen intermittent suspend/resume failures before with
previous kernel versions.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-7-generic 3.11.0-7.14
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: vorlon 4171 F.... pulseaudio
/dev/snd/pcmC0D0p: vorlon 4171 F...m pulseaudio
Date: Fri Sep 20 16:16:06 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=f6ab3c43-61b4-4af7-bf03-fa3b147a1de0
InstallationDate: Installed on 2010-09-24 (1092 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
InterpreterPath: /usr/bin/python3.3
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 3249CTO
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-7-generic
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon
not responding.
RelatedPackageVersions:
linux-restricted-modules-3.11.0-7-generic N/A
linux-backports-modules-3.11.0-7-generic N/A
linux-firmware 1.114
SourcePackage: linux
Title: [LENOVO 3249CTO] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-05-06 (137 days ago)
UserGroups:
WifiSyslog:
dmi.bios.date: 08/23/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET52WW (1.22 )
dmi.board.name: 3249CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3249CTO
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
