Leann, I ran with nvidia-glx-173 with turning on /sys/power/pm_trace to 1. Upon trying to resume from suspend (to ram), the screen did not come back, nor did my Ethernet device. I was therefore unable to capture a dmesg after trying to resume from suspend.
I then got dmesg logs (before and after the suspend) for the open source driver and nvidia-glx-177 with turning /sys/power/pm-trace to 1. For the open source driver, I didn't notice anything spectacular in the logs... For the nvidia-glx-177 driver I get a nice stack trace, but knowing that the nvidia driver is binary only, there doesn't seem like much I can do. (See logs2.tar.gz: nvidia_177/dmesg_after_pm_trace_on). Looking at the end of this file, it looks like compiz.real was making a call to the nvidia driver. After realising this, I then disabled compiz (see logs: logs2.tar.gz: nvidia_177_compiz_off/dmesg_after_pm_trace_on_no_compiz). Even with disabling compiz, video does not seem to resume. If there's any other data I can grab for you guys, please let me know. Thanks! ** Attachment added: "logs2.tar.gz" http://launchpadlibrarian.net/19068877/logs2.tar.gz -- Toshiba Tecra A9 (Nvidia) does not resume properly from hibernation with 2.6.24-19 https://bugs.launchpad.net/bugs/241407 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
