XServer hungs after resuming in a Lenovo t61

Me too
Sony Vaio SZ450N
Nvidia GeForce GO 7400
NV driver

Stack trace of X

(gdb) bt
#0 0xb7ac28e2 in NVSync () from /usr/lib/xorg/modules/drivers//nv_drv.so
#1 0xb68caab9 in ?? () from /usr/lib/xorg/modules//libxaa.so
#2 0xb691118a in ?? () from /usr/lib/xorg/modules//libxaa.so
#3 0x0817f764 in ?? ()
#4 0xb691118a in ?? () from /usr/lib/xorg/modules//libxaa.so
#5 0x0817f764 in ?? ()
#6 0x081140b1 in miPaintWindow ()
#7 0x08114422 in miWindowExposures ()
#8 0x080df4d2 in ?? ()
#9 0x0812c3a4 in miHandleValidateExposures ()
#10 0x080d2fcc in ?? ()
#11 0xb68c9528 in ?? () from /usr/lib/xorg/modules//libxaa.so
#12 0x080f9478 in ?? ()
#13 0xb7ab75bc in ?? () from /usr/lib/xorg/modules/drivers//nv_drv.so
#14 0x080c7f08 in xf86Wakeup ()
#15 0x080912b2 in WakeupHandler ()
#16 0x0813196b in WaitForSomething ()
#17 0x0808d25e in Dispatch ()
#18 0x080721bd in main ()

The changes for lp bug 324234 were tested on this machine also, and did not fix the problem.

Can you install the debug symbols for xserver-xorg-video-nv-psb and reproduce the issue? Unfortunately your stacktrace doesn't include details for the last two calls, which are the ones we need the most. :-)

Manoj, your backtrace doesn't match ara's so it appears you may be seeing a different bug. Again, you need to install dbg symbols for -nv and xorg-server. It would probably be best if you would file a new bug report (ubuntu-bug xserver-xorg-video-nv).

Hello Bryce,

Which package contains the debug symbols. In jaunty, after a search this is what I obtain:

ara@sushirider:~$ sudo apt-cache search xserver-xorg-video-nv*
xserver-xorg-video-neomagic - X.Org X server -- Neomagic display driver
xserver-xorg-video-nv - X.Org X server -- NV display driver
xserver-xorg-video-nouveau - X.Org X server -- Nouveau display driver (experimental)
xserver-xorg-video-nsc - X.Org X server -- NSC Geode GX1 display driver

I cannot find the debug symbols package.

my backtrace via ssh

same issue here. after starting the suspen-resume test I have to manually start my system again. Ubuntu is running(I can login via ssh), but X fails to start. I'm using xserver-xorg-video-nv, too.
here my backtrace/dmesg output:

nothing suprising, but for integrity:
suspend/resume runs flawlessly with nvidia-glx-180
btw my hardware: acer aspire 5920g - nvidia 8600m gt

Here is mine.

suspend/resume seems to work with nvidia 180 (whatever the latest version is at this moment), hibernate/resume with either nv OR nvidia (been a while since I tested nvidia driver like that though) fails to resume, it hangs at a completely black screen most of the time, though the consoles switch to unresponsive tty login screens if you press the keys before X comes back up.

Just got done trying suspend/resume with the nvidia binary driver. Since the last time I tried it it actually works! I still have to press enter to get it to keep going at a few points, but it actually suspends and resumes, then can suspend and resume again. Finally, something in 9.04 that's an improvement over 8.10.

Confirmed that 8600gt with the free drivers resumes but the screen stays blank.

Bug 235284 contained information that helped me solve this for my T61p.
I am running Hardy x64 with NVidia binary drivers (180.54) but had the same suspend/resume issue with Jaunty live CD using free nv drivers.

Specifically, I used information from this post:

https://bugs.launchpad.net/ubuntu/+bug/235284/comments/13

Other Lenovo models require different edits to /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi, but most users in that bug discussion report success.

Hope that's a clue for someone!

  - Paul

oops ... make that Intrepid.

Thank you for reporting this issue about xserver-xorg-video-nv. Starting
with Lucid, Ubuntu is transitioning to using the -nouveau video driver
by default instead of -nv. The reason for this change is because
upstream development for the -nv driver has been quite slow. We are
quite pleased with the upstream development speed for -nouveau, and hope
this will translate into swifter bug fixes as well.

Because of this, I'm closing this bug report at this time. I'm marking
it wontfix because what you describe is probably a valid issue, but we
do not have further plans to work on it in Ubuntu. If you would still like
to see this issue investigated, I would encourage you to file it
upstream at http://bugs.freedesktop.org/.