resume from suspend freezes system (GTX 970, Arch Linux, Kernel 4.4/4.7, NVIDIA 370)

mlaggner · September 3, 2016, 3:19pm

Resume from suspend freezes my system now and then since swapping from a GeForce GTX 750 to a GeForce GTX 970 (same driver/kernel/os as before) - the monitor gets waked up but stays black and the system gets completely unresponsive.

System specs:

OS: Arch Linux
Kernel: 4.7.2-1-ARCH
NVIDIA driver: 370.23-4
NVIDIA card: 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
Monitor: Hitachi/HINT W240D (connected via DVI)

Because the system gets unresponsive after resuming from suspend, I could not get a log from nvidia-bug-report.log.gz after the problem occurred.
Here are a few lines from journalctl shortly before the problem occurs (you find the whole log from today in the attachment as well as a nvidia-bug-report.log.gz after rebooting the system):

Sep 03 15:34:57 Antiphon avahi-daemon[352]: New relevant interface eno1.IPv6 for mDNS.
Sep 03 15:34:57 Antiphon avahi-daemon[352]: Registering new address record for fe80::6031:f025:6f21:b469 on eno1.*.
Sep 03 15:34:58 Antiphon ntpd[378]: Listen normally on 12 eno1 192.168.1.102:123
Sep 03 15:34:58 Antiphon ntpd[378]: Listen normally on 13 eno1 [fe80::6031:f025:6f21:b469%2]:123
Sep 03 15:34:58 Antiphon ntpd[378]: new interface(s) found: waking up resolver
Sep 03 15:34:59 Antiphon kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 03 15:34:59 Antiphon kernel: ata4.00: configured for UDMA/133
Sep 03 15:35:11 Antiphon acpid[346]: client connected from 379[0:0]
Sep 03 15:35:11 Antiphon acpid[346]: 1 client rule loaded
Sep 03 15:35:12 Antiphon root[3948]: ACPI group/action undefined: jack/lineout / LINEOUT
Sep 03 15:35:12 Antiphon root[3950]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Sep 03 15:35:31 Antiphon root[3952]: ACPI group/action undefined: jack/lineout / LINEOUT
Sep 03 15:35:31 Antiphon root[3954]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Sep 03 15:36:11 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000957d:0:0:0x00000040
Sep 03 15:36:15 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917e:0:0:0x00000001
Sep 03 15:36:19 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000927c:0:0:0x00000001
Sep 03 15:36:23 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917e:1:0:0x00000001
Sep 03 15:36:27 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000927c:1:0:0x00000001
Sep 03 15:36:31 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917e:2:0:0x00000001
Sep 03 15:36:35 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000927c:2:0:0x00000001
Sep 03 15:36:39 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917e:3:0:0x00000001
Sep 03 15:36:43 Antiphon kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000927c:3:0:0x00000001
-- Reboot --

As I did not find a way to add an attachment, I’ve put the files on an external hoster:
journalctl.log from the whole day http://pastebin.com/2R4JMxrc
nvidia-bug-report.log.gz http://s000.tinyupload.com/index.php?file_id=08086779656445978052

JonathanAnderson · September 3, 2016, 7:33pm

Have you tried downgrading?
I dont think it will solve your problem, but I had the feeling that drivers around version 350 left the system so responsive that I could ssh in and try to diagnose the problem.
Do you have Skylake?

popq · September 3, 2016, 8:13pm

I am experiencing the same exact issue and my system is quite similar to yours.

OS: Arch Linux
Kernel: 4.7.2-1-ARCH
NVIDIA driver: 370.23-4
NVIDIA card: NVIDIA GTX 1060
Monitor: Dell U2515H (connected via DP)

To reproduce this, I simply had to suspend and resume, simple enough trigger this issue.

Although I was able to access my system through ssh and noticed some tracebacks in dmesg. Not sure if this is helping.

Sep 03 21:50:07 testk kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0:0x00000040
Sep 03 21:50:09 testk kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0:0x00000040
Sep 03 21:51:32 testk systemd[655]: Time has been changed
Sep 03 21:51:32 testk systemd[1]: Time has been changed
Sep 03 21:51:32 testk systemd-timesyncd[475]: Synchronized to time server 178.63.73.143:123 (0.arch.pool.ntp.org).
Sep 03 21:53:09 testk kernel: INFO: task kworker/0:0:4 blocked for more than 120 seconds.
Sep 03 21:53:09 testk kernel:       Tainted: P           O    4.7.2-1-ARCH #1
Sep 03 21:53:09 testk kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 03 21:53:09 testk kernel: kworker/0:0     D ffff8808527dbcb8     0     4      2 0x00000000
Sep 03 21:53:09 testk kernel: Workqueue: events nvkms_workqueue_callback [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  ffff8808527dbcb8 00ffffff810c3b46 ffff88084f3d1e80 ffff8808526eadc0
Sep 03 21:53:09 testk kernel:  ffff880876416bb0 ffff8808527dc000 ffffffffa15f27d0 ffff8808526eadc0
Sep 03 21:53:09 testk kernel:  0000000000000000 ffff88083ee943c0 ffff8808527dbcd0 ffffffff815daacc
Sep 03 21:53:09 testk kernel: Call Trace:
Sep 03 21:53:09 testk kernel:  [<ffffffff815daacc>] schedule+0x3c/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff815dd803>] schedule_timeout+0x1d3/0x260
Sep 03 21:53:09 testk kernel:  [<ffffffff810a328e>] ? check_preempt_curr+0x7e/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff810abdec>] ? set_next_entity+0x4c/0x930
Sep 03 21:53:09 testk kernel:  [<ffffffff810b0955>] ? put_prev_entity+0x35/0x8b0
Sep 03 21:53:09 testk kernel:  [<ffffffff815dc556>] __down+0x76/0xc0
Sep 03 21:53:09 testk kernel:  [<ffffffff810e771e>] ? try_to_del_timer_sync+0x5e/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff810c3ff1>] down+0x41/0x50
Sep 03 21:53:09 testk kernel:  [<ffffffffa154a7ee>] nvkms_workqueue_callback+0x6e/0xf0 [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  [<ffffffff81093615>] process_one_work+0x1e5/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938f8>] worker_thread+0x48/0x4e0
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff81099598>] kthread+0xd8/0xf0
Sep 03 21:53:09 testk kernel:  [<ffffffff815de9bf>] ret_from_fork+0x1f/0x40
Sep 03 21:53:09 testk kernel:  [<ffffffff810994c0>] ? kthread_worker_fn+0x170/0x170
Sep 03 21:53:09 testk kernel: INFO: task kworker/0:2:224 blocked for more than 120 seconds.
Sep 03 21:53:09 testk kernel:       Tainted: P           O    4.7.2-1-ARCH #1
Sep 03 21:53:09 testk kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 03 21:53:09 testk kernel: kworker/0:2     D ffff88084f77bcb8     0   224      2 0x00000000
Sep 03 21:53:09 testk kernel: Workqueue: events nvkms_workqueue_callback [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  ffff88084f77bcb8 00ffffff810c3b46 ffffffff8180d500 ffff88084f58bd00
Sep 03 21:53:09 testk kernel:  ffff880876416bb0 ffff88084f77c000 ffffffffa15f27d0 ffff88084f58bd00
Sep 03 21:53:09 testk kernel:  0000000000000000 ffff88083ee94180 ffff88084f77bcd0 ffffffff815daacc
Sep 03 21:53:09 testk kernel: Call Trace:
Sep 03 21:53:09 testk kernel:  [<ffffffff815daacc>] schedule+0x3c/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff815dd803>] schedule_timeout+0x1d3/0x260
Sep 03 21:53:09 testk kernel:  [<ffffffff810e7eb1>] ? mod_timer+0x111/0x220
Sep 03 21:53:09 testk kernel:  [<ffffffff810abdec>] ? set_next_entity+0x4c/0x930
Sep 03 21:53:09 testk kernel:  [<ffffffff810b0955>] ? put_prev_entity+0x35/0x8b0
Sep 03 21:53:09 testk kernel:  [<ffffffff815dc556>] __down+0x76/0xc0
Sep 03 21:53:09 testk kernel:  [<ffffffff810c3ff1>] down+0x41/0x50
Sep 03 21:53:09 testk kernel:  [<ffffffffa154a7ee>] nvkms_workqueue_callback+0x6e/0xf0 [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  [<ffffffff81093615>] process_one_work+0x1e5/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938f8>] worker_thread+0x48/0x4e0
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff81099598>] kthread+0xd8/0xf0
Sep 03 21:53:09 testk kernel:  [<ffffffff815de9bf>] ret_from_fork+0x1f/0x40
Sep 03 21:53:09 testk kernel:  [<ffffffff810994c0>] ? kthread_worker_fn+0x170/0x170
Sep 03 21:53:09 testk kernel: INFO: task kworker/0:1:2241 blocked for more than 120 seconds.
Sep 03 21:53:09 testk kernel:       Tainted: P           O    4.7.2-1-ARCH #1
Sep 03 21:53:09 testk kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 03 21:53:09 testk kernel: kworker/0:1     D ffff88085187fcb8     0  2241      2 0x00000000
Sep 03 21:53:09 testk kernel: Workqueue: events nvkms_workqueue_callback [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  ffff88085187fcb8 00ffffff810c3b46 ffffffff8180d500 ffff880845080f40
Sep 03 21:53:09 testk kernel:  ffff880876416bb0 ffff880851880000 ffffffffa15f27d0 ffff880845080f40
Sep 03 21:53:09 testk kernel:  0000000000000000 ffff88083ee94300 ffff88085187fcd0 ffffffff815daacc
Sep 03 21:53:09 testk kernel: Call Trace:
Sep 03 21:53:09 testk kernel:  [<ffffffff815daacc>] schedule+0x3c/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff815dd803>] schedule_timeout+0x1d3/0x260
Sep 03 21:53:09 testk kernel:  [<ffffffffa0df7ee4>] ? _nv015020rm+0x54/0x140 [nvidia]
Sep 03 21:53:09 testk kernel:  [<ffffffff810abdec>] ? set_next_entity+0x4c/0x930
Sep 03 21:53:09 testk kernel:  [<ffffffffa093659a>] ? os_release_spinlock+0x1a/0x20 [nvidia]
Sep 03 21:53:09 testk kernel:  [<ffffffff810b0955>] ? put_prev_entity+0x35/0x8b0
Sep 03 21:53:09 testk kernel:  [<ffffffff815dc556>] __down+0x76/0xc0
Sep 03 21:53:09 testk kernel:  [<ffffffff810c3ff1>] down+0x41/0x50
Sep 03 21:53:09 testk kernel:  [<ffffffffa154a7ee>] nvkms_workqueue_callback+0x6e/0xf0 [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  [<ffffffff81093615>] process_one_work+0x1e5/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938f8>] worker_thread+0x48/0x4e0
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff81099598>] kthread+0xd8/0xf0
Sep 03 21:53:09 testk kernel:  [<ffffffff815de9bf>] ret_from_fork+0x1f/0x40
Sep 03 21:53:09 testk kernel:  [<ffffffff810994c0>] ? kthread_worker_fn+0x170/0x170
Sep 03 21:53:09 testk kernel: INFO: task kworker/0:6:2333 blocked for more than 120 seconds.
Sep 03 21:53:09 testk kernel:       Tainted: P           O    4.7.2-1-ARCH #1
Sep 03 21:53:09 testk kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 03 21:53:09 testk kernel: kworker/0:6     D ffff8807dba23cb8     0  2333      2 0x00000000
Sep 03 21:53:09 testk kernel: Workqueue: events nvkms_workqueue_callback [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  ffff8807dba23cb8 00ffffff810c3b46 ffff8808526eadc0 ffff880824269e80
Sep 03 21:53:09 testk kernel:  ffff880876416bb0 ffff8807dba24000 ffffffffa15f27d0 ffff880824269e80
Sep 03 21:53:09 testk kernel:  0000000000000000 ffff88083ee94000 ffff8807dba23cd0 ffffffff815daacc
Sep 03 21:53:09 testk kernel: Call Trace:
Sep 03 21:53:09 testk kernel:  [<ffffffff815daacc>] schedule+0x3c/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff815dd803>] schedule_timeout+0x1d3/0x260
Sep 03 21:53:09 testk kernel:  [<ffffffff810e7eb1>] ? mod_timer+0x111/0x220
Sep 03 21:53:09 testk kernel:  [<ffffffff810abdec>] ? set_next_entity+0x4c/0x930
Sep 03 21:53:09 testk kernel:  [<ffffffff810b0955>] ? put_prev_entity+0x35/0x8b0
Sep 03 21:53:09 testk kernel:  [<ffffffff815dc556>] __down+0x76/0xc0
Sep 03 21:53:09 testk kernel:  [<ffffffff810e771e>] ? try_to_del_timer_sync+0x5e/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff810c3ff1>] down+0x41/0x50
Sep 03 21:53:09 testk kernel:  [<ffffffffa154a7ee>] nvkms_workqueue_callback+0x6e/0xf0 [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  [<ffffffff81093615>] process_one_work+0x1e5/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938f8>] worker_thread+0x48/0x4e0
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff81099598>] kthread+0xd8/0xf0
Sep 03 21:53:09 testk kernel:  [<ffffffff815de9bf>] ret_from_fork+0x1f/0x40
Sep 03 21:53:09 testk kernel:  [<ffffffff810994c0>] ? kthread_worker_fn+0x170/0x170
Sep 03 21:53:09 testk kernel: INFO: task kworker/0:9:2336 blocked for more than 120 seconds.
Sep 03 21:53:09 testk kernel:       Tainted: P           O    4.7.2-1-ARCH #1
Sep 03 21:53:09 testk kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 03 21:53:09 testk kernel: kworker/0:9     D ffff880807a43cb8     0  2336      2 0x00000000
Sep 03 21:53:09 testk kernel: Workqueue: events nvkms_workqueue_callback [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  ffff880807a43cb8 00ffffff810c3b46 ffff88084f3d1e80 ffff880824273d00
Sep 03 21:53:09 testk kernel:  ffff880876416bb0 ffff880807a44000 ffffffffa15f27d0 ffff880824273d00
Sep 03 21:53:09 testk kernel:  0000000000000000 ffff88083ee94240 ffff880807a43cd0 ffffffff815daacc
Sep 03 21:53:09 testk kernel: Call Trace:
Sep 03 21:53:09 testk kernel:  [<ffffffff815daacc>] schedule+0x3c/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff815dd803>] schedule_timeout+0x1d3/0x260
Sep 03 21:53:09 testk kernel:  [<ffffffff810e7eb1>] ? mod_timer+0x111/0x220
Sep 03 21:53:09 testk kernel:  [<ffffffff810abdec>] ? set_next_entity+0x4c/0x930
Sep 03 21:53:09 testk kernel:  [<ffffffff810b0955>] ? put_prev_entity+0x35/0x8b0
Sep 03 21:53:09 testk kernel:  [<ffffffff815dc556>] __down+0x76/0xc0
Sep 03 21:53:09 testk kernel:  [<ffffffff810e771e>] ? try_to_del_timer_sync+0x5e/0x90
Sep 03 21:53:09 testk kernel:  [<ffffffff810c3ff1>] down+0x41/0x50
Sep 03 21:53:09 testk kernel:  [<ffffffffa154a7ee>] nvkms_workqueue_callback+0x6e/0xf0 [nvidia_modeset]
Sep 03 21:53:09 testk kernel:  [<ffffffff81093615>] process_one_work+0x1e5/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938f8>] worker_thread+0x48/0x4e0
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff810938b0>] ? process_one_work+0x480/0x480
Sep 03 21:53:09 testk kernel:  [<ffffffff81099598>] kthread+0xd8/0xf0
Sep 03 21:53:09 testk kernel:  [<ffffffff815de9bf>] ret_from_fork+0x1f/0x40
Sep 03 21:53:09 testk kernel:  [<ffffffff810994c0>] ? kthread_worker_fn+0x170/0x170

For some random reason I was also able to trigger this issue by starting a virtual machine (Complete system froze and became unresponsive, after a restart I couldn’t reproduce this)

mlaggner · September 3, 2016, 9:22pm

I was able to reproduce this issue with a handful of suspend/resume iterations.
I did run the nvidia-bug-report.sh via ssh and got some information for you (one time the script hung and I restarted it with safe-mode on)

nvidia-bug-report.sh (hung) - [url]http://s000.tinyupload.com/index.php?file_id=09643186671116632816[/url]
nvidia-bug-report.sh (–safe-mode) - [url]http://s000.tinyupload.com/index.php?file_id=00948459188648949925[/url]

sandipt · September 6, 2016, 3:20pm

Hi all, Is any earlier driver worked on your setup and don’t have this issue?

mlaggner · September 6, 2016, 3:30pm

just switched to that graphics card a week ago - haven’t used this card with another (older) driver.

@JonathanAnderson: sorry, haven’t seen your post until now… I’ve a haswell setup (H97 board and i5-4690)

Protoss1 · September 6, 2016, 10:46pm

I am suffering from the same issue after upgrading to the 370 release.
I just finished downgrading to the 367.35 release, and so far so good; I am able to both suspend the entire system as well as use DPMS and the display wakes up without issue in both instances.

Unfortunately it seems like DPMS breaks with almost every other driver release, I can only assume due to the ongoing KMS work.

Tip for those willing to downgrade on Arch: I needed to downgrade my kernel release to 4.7.1-1 as well.

sandipt · September 7, 2016, 10:36am

Do you mean this issue is specific to kernel 4.7.2-1-ARCH ? just downgrading nvidia driver will not resolve the issue?

Protoss1 · September 7, 2016, 5:08pm

No sorry for the confusion. I had to downgrade the kernel alongside the Nvidia driver just to get the old driver working properly. Xorg and the Nvidia driver did not work at all before I downgraded my kernel as well. I am not sure whether it was an issue with the Nvidia 367.35 not liking kernel 4.7.2, or vice versa.

eyalzek · September 8, 2016, 12:33am

OS: Ubuntu 16.04
Kernel: 4.4.0-36-generic
NVIDIA driver: 367.35
NVIDIA card: GeForce GTX 970
Monitors: Samsung S24D391, Samsung SMBX2335, Acer S22OHQL

I’m experiencing the exact same behavior described in the original post. Happening erratically.

popq · September 8, 2016, 8:39pm

This issue is still present in 370.28 using the same specs as specified above.

Mounir · September 9, 2016, 9:50pm

Hi devs & users

Voilà what i have :

Desktop PC Ubuntu mate
kernel 4.3 rc1
xorg 1.18
nvidia-370.28 GT-610

nouveau is blacklisted .
suspend not working correctly , the LED is illuminated and and PC won’t resume after pushing LED button .

PS : it is not amazing to switch off the PC 5 or 8 times in a day .

GOD MAY HELP TO FIND A FINAL SOLUTION 4 THIS PROBLEM …

AMEN

sandipt · September 10, 2016, 3:32pm

Make sure to blacklist nouveau driver while using nvidia driver. You can add Nouveau Driver in /etc/modprobe.d/blacklist.conf file. OR create file like /etc/modprobe.d/disable-nouveau.conf with below entries
blacklist nouveau
options nouveau modeset=0

And add kernel parameter : vga=0 rdblacklist=nouveau nouveau.modeset=0
Reboot

Hi all, Please attach nvidia bug report as soon as issue reproduced and also reproduction steps, What desktop env you are running kde, gnome, unity, mate etc…?, Is the issue reproduce with bare X ? [you are start bare X with xinit or X or Xorg command] , What nvidia related error did you see when issue reproduce in log? Is the issue with DP or DVI or HDMI monitors ?

JonathanAnderson · September 11, 2016, 12:33am

Great to see some action on this.

Have you reported the bug anywhere else?
launchpad?
bugzilla.kernel.org?

popq · September 12, 2016, 10:59pm

@sandipt Yes, I tried that since I’ve noticed that nouveau was loaded for some reason although it was blacklisted by archlinux’s nvidia-dkms package. However, after using the kernel parameters, nouveau is completely blacklisted. This didn’t solved the freezes though.

The reproduction is very easy: Simply suspend your system (“systemctl suspend”) and wake it it.
This makes the whole system unresponsive, hence it’s probably hard to attach any logs (Hard shutdown).

I am using Gnome 3.20 with Xorg (Starting from xinit/startx; Linux 4.7.3-ARCH; NVIDIA 370.28; GTX 1060 6GB) on a DP monitor.

Well, I am not sure why you guys can’t reproduce this issue as you can see, clearly there are lot’s of people having this exact same problem (And it’s quite depressing that I had to switch back to intel graphics because this simply sucks ;)).

That said, I am happy to help further.

sandipt · September 16, 2016, 8:01am

Hi Protoss1, Mounir, eyalzek,

Can I get nvidia bug report as soon as issue reproduced on your setup? Please note all “resume from suspend freezes system” issue can’t be have same root cause. make sure you get below error messages in log or dmesg :

[ 631.393127] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000957d:0:0:0x00000040
[ 635.392711] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917e:0:0:0x00000001
[ 639.392399] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000927c:0:0:0x00000001

Hi all, Any earlier or latest driver have not affected with this issue?

Mounir · September 16, 2016, 11:30am

Hi sandip
This error appears.and I would to notice that CTL+alt+F7(F8) do not bring back to GUI .it remains black unresponsive…maybe something is wrong in nv.c with the IRQ threading .
Regards
Mounir

sandipt · September 16, 2016, 12:37pm

Hi Mounir, Can I get nvidia bug report as soon as issue reproduced on your setup?

Mounir · September 16, 2016, 12:41pm

cannot access to deskto via ssh , when this is suspended .how i can launch the bug report script ?

Protoss1 · September 17, 2016, 3:28pm

I just managed to reproduce my issue, after roughly a week of uptime and sleeping/resuming without issue.

Linux kernel 4.7.2-1-ARCH
Nvidia driver version 370.28-1

My machine did not fully lock up thankfully, so I was able to SSH in and run nvidia-bug-report.sh: https://es.gy/d/nvidia-bug-report.log.gz

Please let me know if I could be of further assistance, I’d love to find a solution.

Topic		Replies	Views
Kernel 5.6: system freeze when resuming from suspend or hibernate Linux	28	7387	October 12, 2021
Screen/system is dead on resume (unable to resume with all current drivers) Linux	57	19983	February 25, 2017
Issues resuming from hybrid-sleep Linux	9	2831	June 13, 2024
Trouble suspending with 510.39.01, Linux 5.16.0: Freezing of tasks failed after 20.009 seconds Linux wayland	22	10988	August 30, 2024
Problem with resume from suspend (Ubuntu 16.04, GT 940MX) Linux	171	60377	August 2, 2021
[Regression 460 series] Black screen on boot: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer Linux	64	20767	January 7, 2024
Suspend corrupts window manager (?) after upgrade to 378.09 Linux	68	18835	October 12, 2021
Device driver crash (unable to handle page fault) after suspend-&-resume with version 555.58.02 on Linux kernel v6.9.9 Linux kernel	13	1383	October 17, 2024
Resume issue after suspend Ubuntu 20.04 Linux	3	3746	November 12, 2021
Corrupted graphics upon resume (Gnome 41, X.org, 495.44 driver) Linux	22	5636	June 22, 2022

resume from suspend freezes system (GTX 970, Arch Linux, Kernel 4.4/4.7, NVIDIA 370)

Related topics