(In reply to comment #3)
> Can you provide dmesg from failed suspend on 64-bit kernel? I bet it will fail
> differently than 32-bit kernel.
>
> 2 256MB cards + 32-bit kernel without CONFIG_HIGHMEM4G (only 876 MB of RAM
> directly accessible) = fail. Maybe it's fixable, but I wouldn't count on it.
Marcin: I take it you are referring to failure to suspend due to vmalloc failures in the nouveau driver? Indeed, Daniel has verified that this problem can be avoided by using a 64-bit kernel or by passing vmalloc=128M to the kernel (see the reference bug in Launchpad for details).
When that issue is avoided the system does appear to suspend successfully, but then hangs when resuming.
(In reply to comment #3)
> Can you provide dmesg from failed suspend on 64-bit kernel? I bet it will fail
> differently than 32-bit kernel.
>
> 2 256MB cards + 32-bit kernel without CONFIG_HIGHMEM4G (only 876 MB of RAM
> directly accessible) = fail. Maybe it's fixable, but I wouldn't count on it.
Marcin: I take it you are referring to failure to suspend due to vmalloc failures in the nouveau driver? Indeed, Daniel has verified that this problem can be avoided by using a 64-bit kernel or by passing vmalloc=128M to the kernel (see the reference bug in Launchpad for details).
When that issue is avoided the system does appear to suspend successfully, but then hangs when resuming.