Computer frequently fails to resume after upgrade to NVIDIA 180.44 driver.

[Sam]

Binary package hint: nvidia-180-kernel-source

Suspend/resume had been working great until I installed some updates last night. One of them was the new 180.44 nvidia drivers. Now when the system tries to resume, it frequently ends up freezing with the capslock light blinking.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard HP Pavilion dv2500 Notebook PC
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.39
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=fb03883a-9df2-4405-a6fa-e9d2cfcde373 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.39-generic
SourcePackage: linux
Tags: resume suspend
Title: [Hewlett-Packard HP Pavilion dv2500 Notebook PC] suspend/resume failure [non-free: nvidia]
UserGroups:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
     Subsystem: Hewlett-Packard Company Device [103c:30cd]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400M GS [10de:0427] (rev a1)
     Subsystem: Hewlett-Packard Company Device [103c:30cd]

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.