Screen/system is dead on resume (unable to resume with all current drivers)
With the latest drivers (NVIDIA 319.23) and kernel 3.9.4, my system is unable to resume from suspend. X.org log on resume contains this: [code](II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select{}" (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x0000fa10, 0x0000202c) (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x0000fa10, 0x0000202c)[/code] Ctrl+Alt+Backspace doesn't help because the keyboard is seemingly dead - I'm only able to SysRq+S/U/B. This is from dmesg: [code]Jun 25 00:06:12 localhost kernel: [12687.804267] Restarting tasks ... done. Jun 25 00:06:12 localhost kernel: [12687.853262] NVRM: GPU at 0000:01:00: GPU-136382c0-06fa-2c0f-977a-4f04b1755070 Jun 25 00:06:12 localhost kernel: [12687.853266] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000088 0100cb4f 00000007 00000000 Jun 25 00:06:12 localhost kernel: [12687.853299] NVRM: Xid (0000:01:00): 56, CMDre 00000000 0000008c 00000000 00000005 0000102b Jun 25 00:06:13 localhost kernel: [12688.852064] NVRM: Xid (0000:01:00): 31, Ch 00000000, engmask 00000101, intr 10000000 Jun 25 00:06:15 localhost kernel: [12690.852480] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00001005 Jun 25 00:06:52 localhost kernel: [12727.355961] SysRq : Emergency Sync Jun 25 00:06:52 localhost kernel: [12727.359121] Emergency Sync complete Jun 25 00:06:53 localhost kernel: [12728.733663] SysRq : Emergency Remount R/O[/code] My GPU is [b]not[/b] overclocked, it's an NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1). [b]This only seems to happen if the computer has been suspended for a reasonably long time; anything less than a quarter of an hour will usually resume successfully. [/b]
With the latest drivers (NVIDIA 319.23) and kernel 3.9.4, my system is unable to resume from suspend.

X.org log on resume contains this:

(II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select{}"
(WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x0000fa10, 0x0000202c)
(WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x0000fa10, 0x0000202c)


Ctrl+Alt+Backspace doesn't help because the keyboard is seemingly dead - I'm only able to SysRq+S/U/B.

This is from dmesg:

Jun 25 00:06:12 localhost kernel: [12687.804267] Restarting tasks ... done.
Jun 25 00:06:12 localhost kernel: [12687.853262] NVRM: GPU at 0000:01:00: GPU-136382c0-06fa-2c0f-977a-4f04b1755070
Jun 25 00:06:12 localhost kernel: [12687.853266] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000088 0100cb4f 00000007 00000000
Jun 25 00:06:12 localhost kernel: [12687.853299] NVRM: Xid (0000:01:00): 56, CMDre 00000000 0000008c 00000000 00000005 0000102b
Jun 25 00:06:13 localhost kernel: [12688.852064] NVRM: Xid (0000:01:00): 31, Ch 00000000, engmask 00000101, intr 10000000
Jun 25 00:06:15 localhost kernel: [12690.852480] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00001005
Jun 25 00:06:52 localhost kernel: [12727.355961] SysRq : Emergency Sync
Jun 25 00:06:52 localhost kernel: [12727.359121] Emergency Sync complete
Jun 25 00:06:53 localhost kernel: [12728.733663] SysRq : Emergency Remount R/O


My GPU is not overclocked, it's an NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1).

This only seems to happen if the computer has been suspended for a reasonably long time; anything less than a quarter of an hour will usually resume successfully.
Attachments

nvidia-bug-report.7z

Artem S. Tashkinov
Linux and Open Source advocate

#1
Posted 06/24/2013 06:22 PM   
No problems on 9500GT and 9800GT. I guess i'll stay with them and my next GPU will be an ATI with opensource drivers as soon as they implement Power managment, seriously.
No problems on 9500GT and 9800GT.
I guess i'll stay with them and my next GPU will be an ATI with opensource drivers as soon as they implement Power managment, seriously.

#2
Posted 06/25/2013 09:34 AM   
I'd test this problem with the 8800GT that I have but I'm too lazy to swap GPUs ;-) - but something tells me this problem concerns only GTX 660.
I'd test this problem with the 8800GT that I have but I'm too lazy to swap GPUs ;-) - but something tells me this problem concerns only GTX 660.

Artem S. Tashkinov
Linux and Open Source advocate

#3
Posted 06/25/2013 10:08 AM   
This bug is probably resolved in 319.32 (edit: it's not) - the first resume has been successful, I'll recheck it in the next few days.
This bug is probably resolved in 319.32 (edit: it's not) - the first resume has been successful, I'll recheck it in the next few days.

Artem S. Tashkinov
Linux and Open Source advocate

#4
Posted 06/25/2013 05:10 PM   
No, this bug is not fixed. [code][ 3053.800] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x00001ce8, 0x00003dd4) [ 3060.800] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x00001ce8, 0x00003dd4) Jun 28 00:02:27 localhost kernel: [ 3041.592980] NVRM: GPU at 0000:01:00: GPU-136382c0-06fa-2c0f-977a-4f04b1755070 Jun 28 00:02:27 localhost kernel: [ 3041.592984] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000088 0100cb4f 00000007 00000000 Jun 28 00:02:27 localhost kernel: [ 3041.593018] NVRM: Xid (0000:01:00): 56, CMDre 00000000 0000008c 00000000 00000005 0000102b Jun 28 00:02:28 localhost kernel: [ 3042.591107] NVRM: Xid (0000:01:00): 31, Ch 00000000, engmask 00000101, intr 10000000 Jun 28 00:02:30 localhost kernel: [ 3044.591920] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00001005[/code]
No, this bug is not fixed.

[  3053.800] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x00001ce8, 0x00003dd4)
[ 3060.800] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x00001ce8, 0x00003dd4)

Jun 28 00:02:27 localhost kernel: [ 3041.592980] NVRM: GPU at 0000:01:00: GPU-136382c0-06fa-2c0f-977a-4f04b1755070
Jun 28 00:02:27 localhost kernel: [ 3041.592984] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000088 0100cb4f 00000007 00000000
Jun 28 00:02:27 localhost kernel: [ 3041.593018] NVRM: Xid (0000:01:00): 56, CMDre 00000000 0000008c 00000000 00000005 0000102b
Jun 28 00:02:28 localhost kernel: [ 3042.591107] NVRM: Xid (0000:01:00): 31, Ch 00000000, engmask 00000101, intr 10000000
Jun 28 00:02:30 localhost kernel: [ 3044.591920] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00001005

Artem S. Tashkinov
Linux and Open Source advocate

#5
Posted 06/27/2013 06:09 PM   
Beta 325.08 is also faulty. NVIDIA drivers 313.30 are also faulty. Damn, what's going on? [code][ 5045.039] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select" [ 5051.042] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x000051e8, 0x000072d4) [ 5058.042] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x000051e8, 0x000072d4) Jul 5 13:46:08 localhost kernel: [ 5037.337229] Restarting tasks ... done. Jul 5 13:46:08 localhost kernel: [ 5037.393659] NVRM: GPU at 0000:01:00: GPU-136382c0-06fa-2c0f-977a-4f04b1755070 Jul 5 13:46:08 localhost kernel: [ 5037.393663] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000088 0100cc5f 00000004 00000008 Jul 5 13:46:08 localhost kernel: [ 5037.393696] NVRM: Xid (0000:01:00): 56, CMDre 00000000 0000008c 00000000 00000005 0000102b Jul 5 13:46:09 localhost kernel: [ 5038.391555] NVRM: Xid (0000:01:00): 31, Ch 00000000, engmask 00000101, intr 10000000 Jul 5 13:46:11 localhost kernel: [ 5040.393052] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00001005 Jul 5 13:46:29 localhost kernel: [ 5057.439806] SysRq : Emergency Sync Jul 5 13:46:29 localhost kernel: [ 5057.442617] Emergency Sync complete Jul 5 13:46:33 localhost kernel: [ 5061.922726] SysRq : Emergency Remount R/O[/code] That's is with [b]VGA console[/b] - so no framebuffer at all.
Beta 325.08 is also faulty.

NVIDIA drivers 313.30 are also faulty. Damn, what's going on?

[  5045.039] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[ 5051.042] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x000051e8, 0x000072d4)
[ 5058.042] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x000051e8, 0x000072d4)

Jul 5 13:46:08 localhost kernel: [ 5037.337229] Restarting tasks ... done.
Jul 5 13:46:08 localhost kernel: [ 5037.393659] NVRM: GPU at 0000:01:00: GPU-136382c0-06fa-2c0f-977a-4f04b1755070
Jul 5 13:46:08 localhost kernel: [ 5037.393663] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000088 0100cc5f 00000004 00000008
Jul 5 13:46:08 localhost kernel: [ 5037.393696] NVRM: Xid (0000:01:00): 56, CMDre 00000000 0000008c 00000000 00000005 0000102b
Jul 5 13:46:09 localhost kernel: [ 5038.391555] NVRM: Xid (0000:01:00): 31, Ch 00000000, engmask 00000101, intr 10000000
Jul 5 13:46:11 localhost kernel: [ 5040.393052] NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00001005
Jul 5 13:46:29 localhost kernel: [ 5057.439806] SysRq : Emergency Sync
Jul 5 13:46:29 localhost kernel: [ 5057.442617] Emergency Sync complete
Jul 5 13:46:33 localhost kernel: [ 5061.922726] SysRq : Emergency Remount R/O


That's is with VGA console - so no framebuffer at all.

Artem S. Tashkinov
Linux and Open Source advocate

#6
Posted 07/02/2013 09:50 PM   
Bump.
Bump.

Artem S. Tashkinov
Linux and Open Source advocate

#7
Posted 07/05/2013 08:08 AM   
I have the same problem. 3.9.9-301.fc19.x86_64 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] After a kernel upgrade I am not able to resume from suspend.
I have the same problem.

3.9.9-301.fc19.x86_64
NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition]

After a kernel upgrade I am not able to resume from suspend.

#8
Posted 07/08/2013 12:08 PM   
Can you post your X.org/dmesg messages? or just append [code]sudo nvidia-bug-report.sh[/code]
Can you post your X.org/dmesg messages?

or just append
sudo nvidia-bug-report.sh

Artem S. Tashkinov
Linux and Open Source advocate

#9
Posted 07/08/2013 12:33 PM   
Wow, I've found a person with the exact same problem. His report is [url=https://devtalk.nvidia.com/default/topic/546481/linux/x-hangs-when-resuming-from-suspend-ubuntu-13-04-319-23-/]here[/url].
Wow, I've found a person with the exact same problem.

His report is here.

Artem S. Tashkinov
Linux and Open Source advocate

#10
Posted 07/08/2013 12:34 PM   
I would love to, but I have to find out how get into my machine after failed resume. I have no idea where to find SysRq+S/U/B key on my Mac keyboard :).
I would love to, but I have to find out how get into my machine after failed resume.
I have no idea where to find SysRq+S/U/B key on my Mac keyboard :).

#11
Posted 07/08/2013 03:11 PM   
slune, Take a look at this: http://bobcopeland.com/blog/2008/10/sysrq-on-macbook/ http://ubuntuforums.org/showthread.php?t=762665 http://0pointer.de/lennart/projects/keyfuzz/

Artem S. Tashkinov
Linux and Open Source advocate

#12
Posted 07/08/2013 05:14 PM   
How did you get those logs. I am just not able to get into the machine and after hard reset no signs of an error in X logs or dmsg or ..... . Btw I am always not able to resume.
How did you get those logs. I am just not able to get into the machine and after hard reset no signs of an error in X logs or dmsg or ..... .

Btw I am always not able to resume.

#13
Posted 07/10/2013 05:10 PM   
Have you set up SysRq? It's one way of dumping logs - you could also try serial console, but it's too much hassle.
Have you set up SysRq? It's one way of dumping logs - you could also try serial console, but it's too much hassle.

Artem S. Tashkinov
Linux and Open Source advocate

#14
Posted 07/11/2013 06:26 AM   
I use nVidia driver version 319.32 and kernel 3.7.10-1.16-desktop on openSUSE 12.3. No problems here, I can resume from suspend to RAM and from suspend to DISK. Though, openSUSE uses pm-utils / suspend packages and not the kernel ACPI code for suspending.
I use nVidia driver version 319.32 and kernel 3.7.10-1.16-desktop on openSUSE 12.3. No problems here, I can resume from suspend to RAM and from suspend to DISK. Though, openSUSE uses pm-utils / suspend packages and not the kernel ACPI code for suspending.

#15
Posted 07/11/2013 10:34 PM   
Scroll To Top

Add Reply