suspend does not work on toshiba satellite pro p100

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

I should also point out that I followed the instructions at:
https://wiki.ubuntu.com/DebuggingKernelSuspend

and found the following in the dmesg output:
[ 24.438899] Magic number: 3:31:554
[ 24.438961] hash matches device ptya0
[ 24.439029] hash matches device PNP0C0F:05

I read on https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86852 that the ptya0 thing may be a false positive, but the following line might be relevant? How can I identify which device this is?

Also, this laptop possesses an Nvidia chip so I followed the instructions at:
https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend

but saw no change unfortunately.

Hope this info helps you.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.22.

I am assigning this bug to the 'ubuntu-kernel-acpi' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Hum... It seems there is not so much Toshiba laptops in ubuntu test labs? Thats bad as their laptop hardware is usually good at testing linux-acpi tolerance to bios (claiming they are acpi ones! They may be kidding!) coded by the cream of the worst programmers using their foots. A real shame for a compagny that co-authored acpi! OK... I stop complaining about Toshiba, will never buy anything from them again, that's all...

And let's go to the facts:
This bug (looks like it, we should have had /var/log/message attached to make sure) looks still there in Hardy (and must lasts since Dapper+powersaved, even if the same fix had to be done in a different place).

See hereunder:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.24/+bug/230184

The good news is that there must be someone in freedesktop using toshiba laptops, because they commited the fix in the hal in april.

Again, consider getting that in 8.04.1!

Regards

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Suspend seems to work reliably on Toshiba P100 since about a week. So there is an update, maybe 1st week of november, that solved the problem on up to date Hardy 8.04.1

I suppose last kernel modules update to have solved the suspend to ram issue on this laptop.

The only remaining problem with suspend on this one is sound that doesn't come back at resume: Even reloading intel-hda/alsa or other sound related modules does not help. Even closing and re-open the user session does not help. Only a full restart makes sound work again. As this computer may have several amplifier stages (and last one controlled by a phisical volume cursor on the front of the laptop), I suspect one is correctly powered after a fresh boot by the bios, but power is not restored by bios after being switched off by a STR. In XP, no such problem: I think the power restore must be managed by the driver or by some ACPI WMI extensions linux does not manage?

If someone have found how to solve this (code or DSDT hack), please let it know to teams in charge of this bug.

With Hardy 2.6.24-21 kernel suspend was reliable on Toshiba p100... But 2.6.24-22 there is a regression: S2R only works first time and hangs after that...

Should be nice to keep a positive progress scheme: Since Hardy release, it's one step forward... and one step backward :o(

Regards

Can you comment if this is still an issue with the more recent Intrepid Ibex 8.10 release which contains a 2.6.27 based kernel. You should be able to test using a LiveCD. Please let us know your results. Thanks.

You know... It's now about 3 years I've got this laptop running Linux and several versions. None of them had a reliable support. Sometimes one kernel version is reliable, the next one not.

You try to put some hooks/quirks... next time they will not work because someone decided suspend must migrate to another software architecture (pm-utils) just when previous one was starting to work! And so it is with ipw migration to less than before iwl wireless drivers... nvidia always broken by some in-kernel API changes (maybe this should be called Greg KH GPL-bis, to annoy non free driver providers... but the problem is it also upset users: ask Microsoft what it cost to annoy users after Vista!).

It's an endless job and I regret but I have a personal computer just to use it reliably without so much hassle... I'm even considering coming back to windows if seven works nicely. Or maybe become an Apple client, who knows?

Linux is nice in many aspects, but it's going too fast with no need... and no time/consideration for reliability. Maybe it's a consequence of having get rid of unstable/stable kernel release scheme?

To conclude, I'm not going to try another version. Just next LTS if this one start to get out of problems quickly.

Thanks for the feedback. I'm going to close this for now then. Please feel free to reopen later if the issue still remains.