[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671457
Tested with most recent (daily) mainline kernel build:
linux-image-2.6.38-999-generic_2.6.38-999.201102021140_i386.deb
Resumed failed again, though this time, I got the flashing keyboard
lights indicating a kernel panic. In earlier kernels, the keyboard
lights did not blink.
Following the
Removed 'needs-upstream-testing' tag per post #5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/671457
Title:
Hard freeze on resume after suspend to ram, Atom D525
--
ubuntu-bugs mailing list
Hi E,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the
This bug is not distribution-specific I see the same problem with
various kernels on the ga-d525-tud booting a gentoo system. Kernels I
tested included 2.6.35,2.6.36 and 2.6.37 (all directly from kernel.org).
I always tried to suspend with no drivers loaded and insided the shell
of an initial ram
--
Hard freeze on resume after suspend to ram, Atom D525
https://bugs.launchpad.net/bugs/671457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Performed a test suspend:
echo core /sys/power/pm_test
echo mem /sys/power/state
Resumed successfully.
--
Hard freeze on resume after suspend to ram, Atom D525
https://bugs.launchpad.net/bugs/671457
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Performed a resume trace
(https://wiki.ubuntu.com/DebuggingKernelSuspend)
No hash matches entries in dmesg output. Interestingly, my system
clock was not corrupted after reboot, suggesting the system didn't even
get far enough along during the resume to write a pm trace to the clock.
--
Hard
