Monitors cannot be woken up from sleep mode

Graphics / Linux Linux
1

Hi,

the machine in question has two monitors attached.
Both monitors were in sleep mode, we tried to wake up the monitors by moving the mouse, pressing the up and down keys and pressing enter. One monitor (the left one) woke up from sleep mode, the other one stayed in sleep mode. We turned the right monitor off and on. Then the left monitor went immediately into sleep mode and we were not able to wake up both monitors from sleep mode.

/var/log/messages:
…
Nov 27 14:06:40 journal: htnr1 : * 20 SndWuMsg 4 -1 1
Nov 27 14:09:20 kernel: snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 0
Nov 27 14:09:20 journal: Can not determine workarea, guessing at layout
Nov 27 14:09:31 dbus-daemon: dbus[928]: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’
Nov 27 14:09:31 dbus[928]: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’
Nov 27 14:09:31 systemd: Starting Hostname Service…
Nov 27 14:09:31 dbus-daemon: dbus[928]: [system] Successfully activated service ‘org.freedesktop.hostname1’
Nov 27 14:09:31 dbus[928]: [system] Successfully activated service ‘org.freedesktop.hostname1’
Nov 27 14:09:31 systemd: Started Hostname Service.
Nov 27 14:10:43 kernel: NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [X:1756]
Nov 27 14:10:43 kernel: Modules linked in: fuse nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 tun bridge stp llc ebtable_filter ebtables ip6_tables nf_log_ipv4 nf_log_common xt_LOG iptable_filter sb_edac edac_core intel_powerclamp coretemp intel_rapl iosf_mbi kvm_intel kvm irqbypass crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper iTCO_wdt dell_smbios iTCO_vendor_support mei_wdt ablk_helper dcdbas sparse_keymap cryptd sg i2c_i801 pcspkr snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd
Nov 27 14:10:43 kernel: mei_me soundcore mei lpc_ich shpchp nfsd auth_rpcgss nfs_acl lockd grace binfmt_misc sunrpc ip_tables ext4 mbcache jbd2 sr_mod sd_mod cdrom crc_t10dif crct10dif_generic nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea mxm_wmi sysfillrect sysimgblt fb_sys_fops drm ahci libahci igb e1000e libata megaraid_sas crct10dif_pclmul crct10dif_common crc32c_intel serio_raw dca i2c_algo_bit i2c_core ptp pps_core wmi dm_mirror dm_region_hash dm_log dm_mod
Nov 27 14:10:43 kernel: CPU: 2 PID: 1756 Comm: X Tainted: P OE ------------ 3.10.0-693.5.2.el7.x86_64 #1
Nov 27 14:10:43 kernel: Hardware name: Dell Inc. Precision Tower 7910/0NK5PH, BIOS A17 02/28/2017
Nov 27 14:10:43 kernel: task: ffff880fcc68eeb0 ti: ffff880fcc25c000 task.ti: ffff880fcc25c000
Nov 27 14:10:43 kernel: RIP: 0010:[] [] _nv001150kms+0x4c/0x70 [nvidia_modeset]
Nov 27 14:10:43 kernel: RSP: 0018:ffff880fcc25f8c0 EFLAGS: 00000292
Nov 27 14:10:43 kernel: RAX: ffff880d2270a408 RBX: 0000000000019bc0 RCX: 0000000034d7a490
Nov 27 14:10:43 kernel: RDX: ffff8806c1224588 RSI: ffff880d2270a408 RDI: ffff880c2a114640
Nov 27 14:10:43 kernel: RBP: ffff880c2a114608 R08: 0000000000019bc0 R09: ffffffffc101d475
Nov 27 14:10:43 kernel: R10: ffff88102fc99bc0 R11: ffffea003747a940 R12: ffff88102fc99bc0
Nov 27 14:10:43 kernel: R13: ffffea003747a940 R14: 0000000000000000 R15: ffff880d2270a408
Nov 27 14:10:43 kernel: FS: 00007fdbeaa18a40(0000) GS:ffff88102fc80000(0000) knlGS:0000000000000000
Nov 27 14:10:43 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 27 14:10:43 kernel: CR2: 00007f5dd0f3a000 CR3: 0000000fca2b1000 CR4: 00000000003407e0
Nov 27 14:10:43 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 27 14:10:43 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Nov 27 14:10:43 kernel: Stack:
Nov 27 14:10:43 kernel: ffffffffc107553f 0000000000000000 0000000000000000 ffff880fd4e2b838
Nov 27 14:10:43 kernel: ffff880fd4e2b808 ffff880fd4e2bb78 ffff880fdfbdc008 ffff880fd4e2b840
Nov 27 14:10:43 kernel: ffffffffc10679d4 0000000000000000 0000000000000000 ffff880fd4e2b808
Nov 27 14:10:43 kernel: Call Trace:
Nov 27 14:10:43 kernel: [] ? _nv000769kms+0x20f/0x2f0 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv001830kms+0x44/0x90 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv000009kms+0x457/0x470 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? nvidia_modeset_rm_ops_free_stack+0x1d/0x20 [nvidia]
Nov 27 14:10:43 kernel: [] ? nvkms_call_rm+0x67/0x70 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv002055kms+0x47/0x60 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv001845kms+0xa7/0x150 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? nvkms_memset+0x12/0x20 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv002094kms+0x1954/0x2340 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv019516rm+0x1c/0xc0 [nvidia]
Nov 27 14:10:43 kernel: [] ? _nv006651rm+0x7a/0xe0 [nvidia]
Nov 27 14:10:43 kernel: [] ? _nv030752rm+0xc/0x20 [nvidia]
Nov 27 14:10:43 kernel: [] ? _nv019758rm+0xf3/0x130 [nvidia]
Nov 27 14:10:43 kernel: [] ? nvkms_alloc+0x65/0x70 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv000226kms+0x40/0x40 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? _nv000398kms+0x2e/0x40 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? nvKmsIoctl+0x163/0x1e0 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? nvkms_ioctl_common+0x45/0x80 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? nvkms_ioctl+0x71/0xb0 [nvidia_modeset]
Nov 27 14:10:43 kernel: [] ? nvidia_frontend_unlocked_ioctl+0x41/0x50 [nvidia]
Nov 27 14:10:43 kernel: [] ? do_vfs_ioctl+0x33d/0x540
Nov 27 14:10:43 kernel: [] ? file_has_perm+0x9f/0xb0
Nov 27 14:10:43 kernel: [] ? __sb_end_write+0x31/0x60
Nov 27 14:10:43 kernel: [] ? SyS_ioctl+0xa1/0xc0
Nov 27 14:10:43 kernel: [] ? system_call_fastpath+0x16/0x1b
Nov 27 14:10:43 kernel: Code: 3d 48 3b 6a 18 48 89 d0 75 0b eb 20 0f 1f 00 48 3b 6a 18 74 17 48 8b 52 08 48 39 d3 0f 1f 00 75 ee 48 8b 40 18 48 83 c4 08 5b 5d 48 8b 42 08 48 39 d8 75 ec 48 83 c4 08 31 c0 5b 5d c3 48 89
…

The machine is a Dell Prescision Tower 7910 with a Quadro K1200, the nvidia driver 384.98 is currently installed. We use RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64.

I actually wanted to create a bug report at This site is undergoing maintenance but our IP address is blocked.

Br,
Jens
nvidia-bug-report.log.gz (334 KB)

2

Hi,

The steps to reproduce the error are:
Boot the machine
Login to gnome desktop
Start our application, the machine is therefore under some load
Leave the machine untouched
The machine locks the user and the monitors go into sleep mode
Try to wake up the monitors by clicking the arrow keys, enter key or moving the mouse
Now either both or just one monitor wakes up and goes back to sleep mode and then stays in sleep mode, no matter how many keys you press on the keyboard

This issue is reproducible, but it does not happen 100% of the time.

I already sent this information together with the nvidia-bug-report.log.gz file to nvidia-bugs@nvidia.com, but I did not receive an answer yet. I attached the nvidia-bug-report.log.gz file to the original post.

Br,
Jens

3

Did you get anywhere on this? I have similar behavior. If my screens ever suspend, they enter power save mode and never wake. The only message to appear in my syslog is

snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 0

How audio could matter I can’t fathom, especially on my (unused) hdmi ports, but it’s the only message I get.

I’ve found others saying it’s tied to DisplayPort… are you connected via DP?

I use Ubuntu 16.04.3 LTS (freshly installed)

$ uname -r
4.13.0-31-generic

$ lspci -nn | grep -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2)

4

Not really, as far as I know the issue vanished on its own. But the display configuration was changed in the meantime (two monitors were added), so that might have something to do with the issue vanishing.

Did you try activating the debug mode in /etc/gdm/custom.conf? You might get more useful error messages when you do.

I have a similar problem on a different machine [1], but it looks like the issue was, that the monitors were not configured in Settings->Displays (the file ~/.config/monitors.xml was missing).

[1] [url]384.98 - monitors only show black screen after being turned off and on while logged in as non-root user - Linux - NVIDIA Developer Forums

5

I’m surprised that guy’s monitors.xml mattered. I read elsewhere that only Nouveau used monitors.xml so when I switched to the nVIDIA drivers I removed mine. I’ll try reinstating that file and see if that affects anything…