[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/576135
Ti
Dustan Ashley, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/cu
My T500 went from suspending pretty well at the start of the Maverick
cycle to incompetent right now.
Kernel 2.6.35-22 works when I hit the power button and choose suspend,
but locks up with the flashing moon when I close the lid.
Kernel -23 locks up with the flashing moon for both button and lid
I'm running both Lucid (v10.04) and Jaunty (v9.04) and have similar
symptoms on both. My hardware is a Lenovo Thinkpad X61-tablet
(7764-CTO).
On suspend:
** screen darkens
** LEDs blink
** rarely do I get a complete spin-down [see note 1 below]
** "new moon" LED left blinking (power off reboo
As reported by another poster in bug #550479
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550479/comments/9
A simple work around for this issue is to remove the SD or other media
card from the internal card reader on the front of the laptop. I had
forgotten I had an SD card in there (it's
I have tested with the Mainline Kernel
2.6.34-999-generic_2.6.34-999.201005081426 as well as the updated Ubuntu
Kernel 2.6.32-22-generic that was available today and both still have
the same behavior when I attempt to suspend to ram or disk.
Launchpad Bug #550479 has also been triaged and I feel w
** Tags added: kernel-power
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
Crash on Suspend to RAM in Lenovo T500 Laptop
https://bugs.launchpad.net/bugs/576135
You received this bug notification because you
Hi Dustan,
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 'needs-upstr
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/47901086/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/47901087/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/47901088/BootDmesg.txt
** Att