[gutsy] suspend to ram fail, can't unload nvidia & ipw3945

the "upload" should be "unload"

marsteel:
You can only unload modules when they are no longer in use. In the case of the nvidia module this means while X is still running you won't be able to unload the nvidia module. These days it *should be* possible to suspend while the nvidia module is still running but many old scripts still expect the user to kill off X and because this was the only workaround that worked with a high degree of success in the past.

Thanks for taking the time to report this bug and helping to make Ubuntu better.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
5. Please also attach '/var/log/kern.log.0' to your bug report after reproducing the problem.
For your reference, the full description of procedures for ACPI bug reports is available at https://wiki.ubuntu.com/DebuggingACPI . Thanks in advance!

A recent updated kernel 2.6.22-7-generic has resolved the suspend to ram
problem. Now I can STR my laptop when using ubuntu gutsy.:D

gary@gary-laptop:~$ uname -a
Linux gary-laptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686
GNU/Linux

On 7/13/07, Brian Murray <email address hidden> wrote:
>
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better.
> Please include as attachments the following additional information, if you
> have not already done so (please pay attention to lspci's additional
> options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command 'uname -a' in your next
> response. It should be one, long line of text which includes the exact
> kernel version you're running, as well as the CPU architecture.
> 2. Please run the command 'dmesg > dmesg.log' and attach the resulting
> file 'dmesg.log' to this bug report.
> 3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach
> the resulting file 'lspci-vvnn.log' to this bug report.
> 4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the
> resulting file 'dmidecode.log' to this bug report.
> 5. Please also attach '/var/log/kern.log.0' to your bug report after
> reproducing the problem.
> For your reference, the full description of procedures for ACPI bug
> reports is available at https://wiki.ubuntu.com/DebuggingACPI . Thanks in
> advance!
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Assignee: (unassigned) => Brian Murray
> Status: New => Incomplete
>
> --
> [gutsy] suspend to ram fail, can't unload nvidia & ipw3945
> https://bugs.launchpad.net/bugs/119698
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
To infinity and beyond
http://magang.name

I marking this bug as Fixed Released based on your comments that this now works with an updated kernel. For future reference you can change the status of your own bug reports by clicking on the package name, in this case linux-source-2.6.22, and then choosing a different Status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/BugSquad/ManagingStatus . Thanks again!

I am experiencing this issue in Ubuntu Feisty.

cat nhibernate.log

Starting suspend at Sat Sep 1 21:25:30 CEST 2007
hibernate: [01] Executing CheckLastResume ...
hibernate: [01] Executing CheckRunlevel ...
hibernate: [01] Executing LockFileGet ...
hibernate: [01] Executing NewKernelFileCheck ...
hibernate: [10] Executing EnsureSysfsPowerStateCapable ...
hibernate: [11] Executing XHacksSuspendHook1 ...
hibernate: [59] Executing RemountXFSBootRO ...
hibernate: [89] Executing SaveKernelModprobe ...
hibernate: [91] Executing ModulesUnloadBlacklist ...
Some modules failed to unload: nvidia
hibernate: Aborting suspend due to errors in ModulesUnloadBlacklist (use --force to override).
hibernate: [90] Executing ModulesLoad ...
hibernate: [89] Executing RestoreKernelModprobe ...
hibernate: [85] Executing XHacksResumeHook2 ...
hibernate: [70] Executing ClockRestore ...
hibernate: [70] Executing ClockRestore ...
hibernate: [59] Executing RemountXFSBootRW ...
hibernate: [11] Executing XHacksResumeHook1 ...
hibernate: [01] Executing NoteLastResume ...
hibernate: [01] Executing LockFilePut ...
Resumed at Sat Sep 1 21:25:31 CEST 2007

Alberto - Feisty uses the 2.6.20 kernel which is significantly different than the 2.6.22 kernel. You would want to open a new bug report using linux-source-2.6.20 as the package.

The description appears to refer to the hibernate script, which is not used by default and is certainly not recommended. I've reassigned it to that, since it seems to be trying to unload the nvidia module - this isn't going to work while X is running.