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/
[email protected] [email protected]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228406
Title:
[LENOVO 3249CTO] suspend/resume failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1228406/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
