256.53: suspend to RAM broken on 2.6.36+ (GF 330M)

[mjanusz]

I'm using the 256.53 NVIDIA drivers for my GF 330 on a SONY Vaio F11 laptop (the 260.* line causes a kernel oops). Without the NVIDIA drivers, suspend-to-ram (via the hibernate-ram script) partially works with any recent kernel (2.6.34, 2.6.35, 2.6.26, 2.6.37-rc1) -- the machine is completely responsive over ssh after resuming, but the screen remains blank.

With 256.53 on 2.6.34, this problem is fixed and the display is properly restored after resume. Starting with 2.6.35, resuming no longer works. The machine suspends successfully, but as soon as any button is pressed, it reboots instead of resuming.

Please let me know if there is anything I can do to help debug this problem.

[XjCook]

I had similar problem, but when I added acpi_sleep=nonvs to grub, suspend is working right

[oyvind]

Originally Posted by XjCook

I had similar problem, but when I added acpi_sleep=nonvs to grub, suspend is working right

True, I need to use this option with kernel 2.6.35. But IIRC 2.6.36+ should not need it any more because of built in black-list (for instance, I don't need this option to suspend/resume correctly with 2.6.37).

[mjanusz]

Originally Posted by XjCook

I had similar problem, but when I added acpi_sleep=nonvs to grub, suspend is working right

It seems that this fixes the problem for me as well -- thanks for the hint!

[alessandro_ufms]

Wow, I had the same card and the same problem. The hint works here, on kernel 2.6.36.1 and nvidia 260.12.26. Thanks.

Will nvidia resolve this issue? It's seems the problem starts with 2.6.35 kernel that introduced the suspend to NVS area saving: http://www.spinics.net/lists/linux-acpi/msg29521.html