One little note from Debian:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635575#42 > Debian kernels do not include the intel_idle driver.
Whatever is going on, it's fairly widespread, and other people seem to see it: http://marc.info/?l=linux-kernel&m=131459136817352&w=2 Although, I do question if the bisect really found the cause, or this is just something spurious caused the bisect to point here. We also know that the chipset is quirky: http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4731fdcf6f7bdab3e369a3f844d4ea4d4017284d With CONFIG_INTEL_IDLE=y *AND* intel_idle.max_cstate=0, the system consistently suspend/resumes 2.6.39.4. With CONFIG_INTEL_IDLE=n, the system consistently suspend/resumes with 2.6.39.4. IOW, intel_idle triggers the problem, except when disabled at compile or runtime. acpi_idle seems OK. I bet Windows uses ACPI and that's why nobody sees this on Windows. Note: this is suspend/resume with Fn-F4, the lid, or from software. I can't get the "pull-down, then fiddle with the power button to resume" hack to work any more. ** Bug watch added: Debian Bug tracker #635575 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635575 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/674075 Title: Maverick won't resume (lucid will) on Lenovo S10-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/674075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
