On Fri, Jul 08, 2011 at 03:16:20PM -0000, Arnon Klein wrote: > It looks like it is a wireless device module issue. I'm using 11.04 with > out-of-the-box kernel 2.6.38-8-generic . > > Patching up /usr/lib/pm-utils/sleep.d/55NetworkManager > with : > > case "$1" in > hibernate|suspend) > suspend_nm > modprobe -r ath9k > ;; > thaw|resume) > modprobe ath9k > resume_nm > ;; > *) exit $NA > ;; > esac > > solved this, and my N150 is now returning from suspend.
That's interesting. When I investigated I saw that the hang was most definitely happening prior to resuming devices, so I'm not sure what the relationship is. A lot of things seemed to make the problem harder to trigger without completely eliminating it though; the hang appears to be very timing sensitive. If you're interested you could try running an automated S3 test to see whether you can trigger a hang. The following would do 100 S3 iterations (you'll probably need to run 'sudo apt-get install fwts' first): fwts s3 --s3-multiple=100 I'm no longer in posession of one of these machines to try it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640100 Title: Maverick fails to wake up on Samsung N150 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/640100/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
