Comment 24 for bug 754711

Boy, that machine just has all sorts of problems with graphics. Kind of makes it hard to decide what to pound on first.

I checked, and we aren't carrying any patches to nouveau in the natty kernel. So I'm a bit puzzled why you see different behavior with natty (with vmalloc size increased) versus mainline unless it's due to something external to nouveau. Looking closer at the pm_trace it seems that it really only traces device resume and not suspend, so it's a bit interesting that pm_trace showed anything at all. Makes me wonder if something went wrong elsewhere in suspend and then the machine hung in the nouveau code while trying to back out of the failed suspend.

Probably the most effective thing to do at this point is to open upstream bug reports against the issues you see when running a mainline build. If you don't mind filing the bugs yourself it might be easier since you actually have the hardware, otherwise I can do it. The appropriate location for the upstream bug reports is:

https://bugs.freedesktop.org/