Toshiba Tecra A9 (Nvidia) does not wake up from suspend

This laptop also has an issue waking up from hibernation. The computer hangs when starting back up.

As far as I know, this is still an issue (Even for the Ubuntu 8.10 Release candidate) I have posted my logs here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/241407

There may be a quirk applicable to this hardware (affects: hal-info); see lshal.

I'm just posting some of the relevant logs and information that John included in bug 241407.

John wrote:
"I did a fresh install of the (final) Ubuntu 8.10 and hibernate works for me (using the binary Nvidia 177 driver.. I did not try using 173 or the open source driver). Unfortunately suspend still does not work. :(

After installing (final) Ubuntu 8.10, I booted up a live session from the latest and greatest Ubuntu 8.10 CD and tried to do suspend/resume (as you suggested). Video did not come back upon trying to resume my laptop."

From John:

"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 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."

Attached is dump from lshal on my Toshiba Tecra A9 using Ubuntu 8.10 (with all the latests updates):

jwoo@aji:~$ uname -a
Linux aji 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
jwoo@aji:~$ lshal > lshal_output_ubuntu810

I then manually overwrote following two keys with fake values:
system.hardware.serial
battery.serial

Hopefully you guys don't need these values.

Thanks,

John

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug was reported a while ago but there hasn't been any recent comments or updates. Is this still an issue with the latest pre-release of Jaunty 9.04? Refer to http://www.ubuntu.com/testing/jaunty/beta . Please let us know.

There has been quite a bit of development done w.r.t. suspend/resume. It would be good to know if this has been fixed in the latest release.

I also have a Tecra A9 with Nvidia graphics and it doesn't wake up from suspend either. I'm running the Jaunty release with all the updates.

I've got a Tecra M9 running Ubuntu 9.10 that won't wake up after suspend

Hrm, per the "Launchpad Janitor" (over a year ago):

    Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as
    part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to
    https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

perhaps the reason there has been on update to this bug since that message was posted is because the Ubuntu developers have washed their hands of it and abandoned it. Very nice.

FWIW, this still happens on Karmic (current stable) and my Tecra M9 with an:

01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 130M (rev a1)

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

@Jeremy,

There has been no comments because nobody has responded to my latest comments and nobody had done anything to progress this issue towards resolution.

You cannot simply close a bug because users have made updates and developers have ignored them. That doesn't change the fact that this bug is still relevant.

This bug still happens on Lucid so it's still valid and should still be open, until somebody actually does something to resolve it.

Setting back to Incomplete. What more needs to happen?

Brian, I removed the expired tag and added the suspend resume tags. You're not the only one bitten with suspend/resume issues. Unfortunately, that's about all I can do for you at this moment but if you might want to check this one out: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/502376

However, a lot of the ones I found seem to involve nVidia chips, and IIRC, your A9 has Intel graphics...

hi Brian,
    Apologies for that. It appears that there is a bug in the script I am using. Odd that it expired this twice. I am looking into why that was.

As to what is needed, please run:
apport-collect -p linux 203251
from the command line so that we can get the current state of your machine's environment. Once that has been completed, please test the latest upstream mainline kernel from the Kernel PPA (information here: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds) and let me know the results of your testing.

Apologies for the confusion.

Thanks!

~JFo

Just a comment to see if can_expire gets reset.