302.07 no resume from suspend

[theDOC]

Originally Posted by theClassicMan27

Same problem here, after resume, screen stay black, CapsLock led blink, keyboard stuck, can not switch to tty, any other is normal.
What can we do now?

downgrade and wait

[Evilandi666]

Can confirm this Bug on Archlinux x64 3.4.4-2-ARCH and 302.17 driver. Afaik: No non-VGA console is used.

lspci:
NVIDIA Corporation GT218 [GeForce 210] (rev a2).

Random freezes while going into standby or while waking up from standby. No ethernet connection or keyboard presses are possible, only a long press on the powerbutton stops the system then.

typical logs:
NVRM: Xid (0000:01:00): 6, PE0001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

Solution: Downgrade to 295.49 with 3.4.x patch from here.

I tried to create a bug report with nvidia-bug-report.sh Version: 11669588, but it does not work. It only creates one short textfile (inside the .log.gz) with the output of uname -a included .. sry. no bug report this time .

[olejon]

Also, on my HTPC with NVIDIA ION gnome-settings-daemon crashed every few hours, removing my appearance settings (ugly grey GTK theme & icons). Fixed by downgrading the NVIDIA driver.

[Tsu Jan]

I also confirm this bug for Debian.

After upgrading to nvidia 302.17, resuming from (TuxOnIce) hibernation from Gnome-Shell results in a black screen with my pf-kernel 3.4.2. Downgrading to nvidia 295.59 fixes the issue (as there was no issue at all before upgrading).

[AaronP]

Could you please try the 304.22 beta release?

[artem]

AaronP

Wait a sec, downloading and checking.

Edit: 8800GT here, it's now fixed and even VesaFB still works. Thank you!

I've hot replaced 290.10 with these beta drivers, I will report again when I reboot and start with the new drivers.

Edit II: I've rebooted and

VesaFB works! Resume from suspend also works. Hooray!! Thank you, Aaron! Thank you, NVIDIA!

[Lemmiwinks]

Originally Posted by artem

AaronP

Edit II: I've rebooted and

VesaFB works! Resume from suspend also works. Hooray!! Thank you, Aaron! Thank you, NVIDIA!

Hmm unfortunately it does not work for me
I still have no TTY, just a purple bar on top of the screen and also when resuming from suspend I only get this purple bar. Then I have to hard-reset my laptop.

I am using Ubuntu 12.04 with an Geforce 8600M GT (driver 304.22) and the kernel 3.2.23 from the mainline kernel PPA.
Before installing the new beta driver I removed every tiny bit of leftovers of any older nvidia driver. Nouveau driver is blacklisted but I tested it before and it worked like a charm (TTY and resume from suspend).

Maybe anybody has an idea what is going wrong?

[danix]

Originally Posted by Lemmiwinks

Hmm unfortunately it does not work for me
I still have no TTY, just a purple bar on top of the screen and also when resuming from suspend I only get this purple bar. Then I have to hard-reset my laptop.

Lemmiwinks, in your case is this issue a regression since the 295.xx drivers?

The issue that we identified was caused by a change that took place between the 295.xx and 302.xx driver series. It's possible that suspend/resume is failing on your system for an entirely different reason.

[Lemmiwinks]

@danix: You are right! It does indeed fail for an entirely different reason. It does not have anything to do with the Nvidia drivers but with grub/plymouth/Ubuntu.

I found out that selecting recovery mode in grub but then resuming the normal boot, there aren't any issues at all anymore. So what are the differences between normal boot and recovery boot except for no "quiet splash" but "recovery in the grub command line?
The answer is, some weird Ubuntu stuff in /etc/grub.d/10_linux, "Native boot entries", especially the line "gfxmode \$linux_gfx_mode". What it does: makes the boot process beautiful with plymouth, which works great as long as you use the default ubuntu kernel from the repos. When you have issues with that kernel and want to try a different one you run into serious problems like I described in the post above. Thank you Canonical!

But really thanks to nvidia for their new driver, its awesome to have dkms support inculuded.

[ltmon]

I'm now getting reliable suspend and resume (without framebuffer). When enabling the framebuffer it's mostly good, but I've had one or two failures to suspend -- just hanging -- but that is potentially not a nvidia issue (e.g. plymouth).

Thanks for the fix.

[Lemmiwinks]

Other solution: Nvidia makes the driver behave correctly even with the gfxmode \$linux_gfx_mode setting

[oyvind]

Resume from suspend looks OK in 304.22, where previous 302.X failed. Dell Latitude E6510 with NVS 3100M GPU and Ubuntu 12.04 x86-64. (No special framebuffer modes for VTs.)