You are not logged in.

Pages: 1

#1 2020-01-20 18:44:08

Tharbad
Member
Registered: 2016-02-27
Posts: 270

[SOLVED] Black screen when returning from suspend

Hi all,

Since I upgraded my GPU (from GTX 670 to RTX 2060 Super) I'm getting a black screen when returning from suspend and must reboot.

In the log:

Jan 20 19:47:06 <PC Name> kernel: ata10: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata9: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata12: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata11: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata8: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata14: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata7: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata13: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata5: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata6: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata4: link is slow to respond, please be patient (ready=0)
Jan 20 19:47:06 <PC Name> kernel: ata3: link is slow to respond, please be patient (ready=0)

And some lines after:

Jan 20 19:47:06 <PC Name> kernel: ata9: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata12: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata11: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata8: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata14: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata7: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata13: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata10: COMRESET failed (errno=-16)
Jan 20 19:47:06 <PC Name> kernel: ata3: COMRESET failed (errno=-16)

As far as I understand it means something about bad HDDs. But all my HDDs are sd#. So it's just strange.

And than we have the nvidia crushing stuff.

Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Unsupported base display class
Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine base channels
Jan 20 19:47:06 <PC Name> kernel: ------------[ cut here ]------------
Jan 20 19:47:06 <PC Name> kernel: Trying to vfree() bad address (00000000b3b878f3)
Jan 20 19:47:06 <PC Name> kernel: WARNING: CPU: 0 PID: 153073 at mm/vmalloc.c:2234 __vunmap+0x20b/0x230
Jan 20 19:47:06 <PC Name> kernel: Modules linked in: nls_utf8 cifs libarc4 dns_resolver fscache libdes cfg80211 msr rfkill 8021q garp it87 mrp stp llc hwmon_vid mousedev joydev input_leds intel_rapl_msr intel_rapl_common nls_iso8859_1 nls_cp437 vfat fat x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel fuse kvm irqbypass snd_hda_codec_hdmi snd_hda_codec_via crct10dif_pclmul crc32_pclmul ucsi_ccg mei_hdcp snd_hda_codec_generic typec_ucsi ghash_clmulni_intel typec ledtrig_audio iTCO_wdt iTCO_vendor_support mxm_wmi aesni_intel snd_hda_intel crypto_simd snd_intel_nhlt cryptd snd_hda_codec glue_helper intel_cstate intel_uncore intel_rapl_perf snd_hda_core snd_hwdep snd_pcm snd_timer pcspkr i2c_i801 snd mei_me mei soundcore atl1c i2c_nvidia_gpu lpc_ich ie31200_edac evdev wmi intel_smartconnect mac_hid nf_log_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp
Jan 20 19:47:06 <PC Name> kernel:  nf_conntrack_ftp tcp_bbr vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) vboxvideo drm_vram_helper ttm vboxsf(OE) vboxguest usbip_host usbip_core iptable_security iptable_raw iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_filter sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid sd_mod ahci libahci libata xhci_pci crc32c_intel scsi_mod xhci_hcd ehci_pci ehci_hcd nvidia_drm(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart nvidia_uvm(OE) nvidia_modeset(POE) nvidia(POE) ipmi_devintf ipmi_msghandler bcache crc64
Jan 20 19:47:06 <PC Name> kernel: CPU: 0 PID: 153073 Comm: kworker/u16:55 Tainted: P           OE     5.4.12-1-ck-ivybridge #1
Jan 20 19:47:06 <PC Name> kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77X-UD3H, BIOS F20e 01/06/2014
Jan 20 19:47:06 <PC Name> kernel: Workqueue: events_unbound async_run_entry_fn
Jan 20 19:47:06 <PC Name> kernel: RIP: 0010:__vunmap+0x20b/0x230
Jan 20 19:47:06 <PC Name> kernel: Code: 6b 01 49 8b 7d 20 e8 f4 d8 fc ff 4c 89 ef 5b 5d 41 5c 41 5d 41 5e e9 44 d4 02 00 48 89 fe 48 c7 c7 80 61 6e 96 e8 33 4c e6 ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e c3 4c 89 e6 48 c7 c7 a8 61 6e 96 e8
Jan 20 19:47:06 <PC Name> kernel: RSP: 0018:ffffb6c3cdaefce0 EFLAGS: 00010282
Jan 20 19:47:06 <PC Name> kernel: RAX: 0000000000000000 RBX: ffffa3e03ad17008 RCX: 0000000000000000
Jan 20 19:47:06 <PC Name> kernel: RDX: 0000000000000001 RSI: 0000000000000092 RDI: 00000000ffffffff
Jan 20 19:47:06 <PC Name> kernel: RBP: 0000000000000b40 R08: 000027724bb79dc8 R09: ffffffff96eb7db4
Jan 20 19:47:06 <PC Name> kernel: R10: 000000000017e912 R11: 0000000000005e74 R12: ffffa3e034a3bb40
Jan 20 19:47:06 <PC Name> kernel: R13: 0000000000000004 R14: ffffa3e0349e5008 R15: ffffa3e03ad17008
Jan 20 19:47:06 <PC Name> kernel: FS:  0000000000000000(0000) GS:ffffa3e03ea00000(0000) knlGS:0000000000000000
Jan 20 19:47:06 <PC Name> kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 20 19:47:06 <PC Name> kernel: CR2: 00007fe800a4ac96 CR3: 0000000178c0a001 CR4: 00000000001606f0
Jan 20 19:47:06 <PC Name> kernel: Call Trace:
Jan 20 19:47:06 <PC Name> kernel:  _nv002415kms+0xea/0x150 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv000327kms+0x2d/0x1d0 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv002225kms+0x2d5/0x6d0 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? nvKmsResume+0x60/0x80 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? nvkms_resume+0x1b/0x40 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? nvidia_resume+0x67/0x70 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? pci_pm_thaw+0x80/0x80
Jan 20 19:47:06 <PC Name> kernel:  ? nv_pmops_resume+0xf/0x20 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? dpm_run_callback+0x4f/0x180
Jan 20 19:47:06 <PC Name> kernel:  ? device_resume+0xb0/0x200
Jan 20 19:47:06 <PC Name> kernel:  ? async_resume+0x19/0x30
Jan 20 19:47:06 <PC Name> kernel:  ? async_run_entry_fn+0x37/0x140
Jan 20 19:47:06 <PC Name> kernel:  ? process_one_work+0x1e2/0x3b0
Jan 20 19:47:06 <PC Name> kernel:  ? worker_thread+0x4a/0x3c0
Jan 20 19:47:06 <PC Name> kernel:  ? kthread+0xfb/0x130
Jan 20 19:47:06 <PC Name> kernel:  ? process_one_work+0x3b0/0x3b0
Jan 20 19:47:06 <PC Name> kernel:  ? kthread_park+0x90/0x90
Jan 20 19:47:06 <PC Name> kernel:  ? ret_from_fork+0x35/0x40
Jan 20 19:47:06 <PC Name> kernel: ---[ end trace f0255cc8d86131dc ]---
Jan 20 19:47:06 <PC Name> kernel: ------------[ cut here ]------------
Jan 20 19:47:06 <PC Name> kernel: Trying to vfree() bad address (00000000b3b878f3)
Jan 20 19:47:06 <PC Name> kernel: WARNING: CPU: 0 PID: 153073 at mm/vmalloc.c:2234 __vunmap+0x20b/0x230
Jan 20 19:47:06 <PC Name> kernel: Modules linked in: nls_utf8 cifs libarc4 dns_resolver fscache libdes cfg80211 msr rfkill 8021q garp it87 mrp stp llc hwmon_vid mousedev joydev input_leds intel_rapl_msr intel_rapl_common nls_iso8859_1 nls_cp437 vfat fat x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel fuse kvm irqbypass snd_hda_codec_hdmi snd_hda_codec_via crct10dif_pclmul crc32_pclmul ucsi_ccg mei_hdcp snd_hda_codec_generic typec_ucsi ghash_clmulni_intel typec ledtrig_audio iTCO_wdt iTCO_vendor_support mxm_wmi aesni_intel snd_hda_intel crypto_simd snd_intel_nhlt cryptd snd_hda_codec glue_helper intel_cstate intel_uncore intel_rapl_perf snd_hda_core snd_hwdep snd_pcm snd_timer pcspkr i2c_i801 snd mei_me mei soundcore atl1c i2c_nvidia_gpu lpc_ich ie31200_edac evdev wmi intel_smartconnect mac_hid nf_log_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp
Jan 20 19:47:06 <PC Name> kernel:  nf_conntrack_ftp tcp_bbr vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) vboxvideo drm_vram_helper ttm vboxsf(OE) vboxguest usbip_host usbip_core iptable_security iptable_raw iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_filter sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid sd_mod ahci libahci libata xhci_pci crc32c_intel scsi_mod xhci_hcd ehci_pci ehci_hcd nvidia_drm(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart nvidia_uvm(OE) nvidia_modeset(POE) nvidia(POE) ipmi_devintf ipmi_msghandler bcache crc64
Jan 20 19:47:06 <PC Name> kernel: CPU: 0 PID: 153073 Comm: kworker/u16:55 Tainted: P        W  OE     5.4.12-1-ck-ivybridge #1
Jan 20 19:47:06 <PC Name> kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77X-UD3H, BIOS F20e 01/06/2014
Jan 20 19:47:06 <PC Name> kernel: Workqueue: events_unbound async_run_entry_fn
Jan 20 19:47:06 <PC Name> kernel: RIP: 0010:__vunmap+0x20b/0x230
Jan 20 19:47:06 <PC Name> kernel: Code: 6b 01 49 8b 7d 20 e8 f4 d8 fc ff 4c 89 ef 5b 5d 41 5c 41 5d 41 5e e9 44 d4 02 00 48 89 fe 48 c7 c7 80 61 6e 96 e8 33 4c e6 ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e c3 4c 89 e6 48 c7 c7 a8 61 6e 96 e8
Jan 20 19:47:06 <PC Name> kernel: RSP: 0018:ffffb6c3cdaefb80 EFLAGS: 00010282
Jan 20 19:47:06 <PC Name> kernel: RAX: 0000000000000000 RBX: ffffa3e03ad17008 RCX: 0000000000000000
Jan 20 19:47:06 <PC Name> kernel: RDX: 0000000000000001 RSI: 0000000000000092 RDI: 00000000ffffffff
Jan 20 19:47:06 <PC Name> kernel: RBP: 0000000000000b40 R08: 000027724bc15f3c R09: ffffffff96eb7db4
Jan 20 19:47:06 <PC Name> kernel: R10: 000000000017e939 R11: 0000000000004e74 R12: ffffa3e034a3bb40
Jan 20 19:47:06 <PC Name> kernel: R13: 0000000000000004 R14: ffffa3e0349e5008 R15: ffffa3e03ad17008
Jan 20 19:47:06 <PC Name> kernel: FS:  0000000000000000(0000) GS:ffffa3e03ea00000(0000) knlGS:0000000000000000
Jan 20 19:47:06 <PC Name> kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 20 19:47:06 <PC Name> kernel: CR2: 00007fe800a4ac96 CR3: 0000000178c0a001 CR4: 00000000001606f0
Jan 20 19:47:06 <PC Name> kernel: Call Trace:
Jan 20 19:47:06 <PC Name> kernel:  _nv002415kms+0xea/0x150 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _raw_spin_lock_irqsave+0x26/0x50
Jan 20 19:47:06 <PC Name> kernel:  ? _nv000327kms+0x2d/0x1d0 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv002409kms+0x85/0xf0 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv033264rm+0xc/0x20 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? _raw_spin_unlock_irqrestore+0x20/0x40
Jan 20 19:47:06 <PC Name> kernel:  ? _nv036755rm+0xac/0x170 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv034129rm+0x67/0x100 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv007468rm+0x40/0x50 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? nvkms_call_rm+0x5b/0x80 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv002387kms+0x4fd/0x8d0 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv002576kms+0x51/0x60 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv002577kms+0x60/0x60 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv002609kms+0x45/0x90 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? _nv000576kms+0x38/0x50 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? nvKmsResume+0x43/0x80 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? nvkms_resume+0x1b/0x40 [nvidia_modeset]
Jan 20 19:47:06 <PC Name> kernel:  ? nvidia_resume+0x67/0x70 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? pci_pm_thaw+0x80/0x80
Jan 20 19:47:06 <PC Name> kernel:  ? nv_pmops_resume+0xf/0x20 [nvidia]
Jan 20 19:47:06 <PC Name> kernel:  ? dpm_run_callback+0x4f/0x180
Jan 20 19:47:06 <PC Name> kernel:  ? device_resume+0xb0/0x200
Jan 20 19:47:06 <PC Name> kernel:  ? async_resume+0x19/0x30
Jan 20 19:47:06 <PC Name> kernel:  ? async_run_entry_fn+0x37/0x140
Jan 20 19:47:06 <PC Name> kernel:  ? process_one_work+0x1e2/0x3b0
Jan 20 19:47:06 <PC Name> kernel:  ? worker_thread+0x4a/0x3c0
Jan 20 19:47:06 <PC Name> kernel:  ? kthread+0xfb/0x130
Jan 20 19:47:06 <PC Name> kernel:  ? process_one_work+0x3b0/0x3b0
Jan 20 19:47:06 <PC Name> kernel:  ? kthread_park+0x90/0x90
Jan 20 19:47:06 <PC Name> kernel:  ? ret_from_fork+0x35/0x40
Jan 20 19:47:06 <PC Name> kernel: ---[ end trace f0255cc8d86131dd ]---
Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Unsupported base display class
Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine base channels
Jan 20 19:47:06 <PC Name> kernel: ------------[ cut here ]------------
Jan 20 19:47:06 <PC Name> kernel: Trying to vfree() bad address (00000000b3b878f3)
Jan 20 19:47:06 <PC Name> kernel: WARNING: CPU: 0 PID: 153073 at mm/vmalloc.c:2234 __vunmap+0x20b/0x230
Jan 20 19:47:06 <PC Name> kernel: Modules linked in: nls_utf8 cifs libarc4 dns_resolver fscache libdes cfg80211 msr rfkill 8021q garp it87 mrp stp llc hwmon_vid mousedev joydev input_leds intel_rapl_msr intel_rapl_common nls_iso8859_1 nls_cp437 vfat fat x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel fuse kvm irqbypass snd_hda_codec_hdmi snd_hda_codec_via crct10dif_pclmul crc32_pclmul ucsi_ccg mei_hdcp snd_hda_codec_generic typec_ucsi ghash_clmulni_intel typec ledtrig_audio iTCO_wdt iTCO_vendor_support mxm_wmi aesni_intel snd_hda_intel crypto_simd snd_intel_nhlt cryptd snd_hda_codec glue_helper intel_cstate intel_uncore intel_rapl_perf snd_hda_core snd_hwdep snd_pcm snd_timer pcspkr i2c_i801 snd mei_me mei soundcore atl1c i2c_nvidia_gpu lpc_ich ie31200_edac evdev wmi intel_smartconnect mac_hid nf_log_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp
Jan 20 19:47:06 <PC Name> kernel:  nf_conntrack_ftp tcp_bbr vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) vboxvideo drm_vram_helper ttm vboxsf(OE) vboxguest usbip_host usbip_core iptable_security iptable_raw iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_filter sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid sd_mod ahci libahci libata xhci_pci crc32c_intel scsi_mod xhci_hcd ehci_pci ehci_hcd nvidia_drm(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart nvidia_uvm(OE) nvidia_modeset(POE) nvidia(POE) ipmi_devintf ipmi_msghandler bcache crc64

Ideas?

edit: Solved as of kernel v5.5.1 with nvidia v440.48.02. ata power errors still present.

Thanks

Last edited by Tharbad (2020-02-05 16:45:21)

Offline

#2 2020-01-21 02:49:23

DeletedUser2111043
Banned
Registered: 2018-03-24
Posts: 2

Re: [SOLVED] Black screen when returning from suspend

Tharbad wrote:

Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Unsupported base display class
Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine base channels

What graphics driver are you using? It's probably a bug.
By the way, try to boot with the nomodeset kernel parameter to see if returning from suspend works.

Last edited by DeletedUser2111043 (2020-01-21 02:51:25)

Offline

#3 2020-01-21 09:03:42

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: [SOLVED] Black screen when returning from suspend

https://download.nvidia.com/XFree86/Lin … ement.html

nvidia wrote:

To save potentially large copies of video memory, the NVIDIA driver uses unnamed temporary files. By default, these files are created in /tmp, but this location can be changed with the TemporaryFilePath kernel module parameter, e.g. TemporaryFilePath=/run. The destination file system needs to support unnamed temporary files, and it needs to be large enough to accommodate all video memory copies for the duration of power management cycles.

When determining a suitable size for the video memory backing store, it is recommended to start with the overall amount of video memory supported by the GPUs installed in the system. For example: nvidia-smi -q -d MEMORY |grep 'FB Memory Usage' -A1. Each Total line returned by this command reflects one GPU's video memory capacity, in MiB. The sum of these numbers, plus 5% of margin, is a conservative starting point for the size of video memory save area.

Please note that file systems such as /tmp and /run are often of the type tmpfs, and potentially relatively small. Most commonly, the size of the type of the file system used is controlled by systemd. For more information, see https://www.freedesktop.org/wiki/Softwa … ileSystems. To achieve the best performance, file system types other than tmpfs are recommended at this time.

Additionally, to unlock the full functionality of the interface, the NVIDIA Linux kernel module needs to be loaded with the NVreg_PreserveVideoMemoryAllocations=1 module parameter. This changes the default video memory save/restore strategy to save and restore all video memory allocations.

However, the ata errors (while out of context) could suggest a power issue (all devices wake up and draw power at the same time) - does the new GPU draw much more power than the old one?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#4 2020-01-21 17:56:33

Tharbad
Member
Registered: 2016-02-27
Posts: 270

Re: [SOLVED] Black screen when returning from suspend

seth wrote:

https://download.nvidia.com/XFree86/Lin … ement.html

nvidia wrote:

To save potentially large copies of video memory, the NVIDIA driver uses unnamed temporary files. By default, these files are created in /tmp, but this location can be changed with the TemporaryFilePath kernel module parameter, e.g. TemporaryFilePath=/run. The destination file system needs to support unnamed temporary files, and it needs to be large enough to accommodate all video memory copies for the duration of power management cycles.

When determining a suitable size for the video memory backing store, it is recommended to start with the overall amount of video memory supported by the GPUs installed in the system. For example: nvidia-smi -q -d MEMORY |grep 'FB Memory Usage' -A1. Each Total line returned by this command reflects one GPU's video memory capacity, in MiB. The sum of these numbers, plus 5% of margin, is a conservative starting point for the size of video memory save area.

Please note that file systems such as /tmp and /run are often of the type tmpfs, and potentially relatively small. Most commonly, the size of the type of the file system used is controlled by systemd. For more information, see https://www.freedesktop.org/wiki/Softwa … ileSystems. To achieve the best performance, file system types other than tmpfs are recommended at this time.

Additionally, to unlock the full functionality of the interface, the NVIDIA Linux kernel module needs to be loaded with the NVreg_PreserveVideoMemoryAllocations=1 module parameter. This changes the default video memory save/restore strategy to save and restore all video memory allocations.

However, the ata errors (while out of context) could suggest a power issue (all devices wake up and draw power at the same time) - does the new GPU draw much more power than the old one?

A bit more but my PSU is 800w which is 300w more than the recommended.

tmp is located on my RAM. The GPU mem is 8GB and the tmp is 16GB so it should be OK.

I've added the following kernel module option:
options nvidia NVreg_PreserveVideoMemoryAllocations=1
I hope nvidia is the right module. Another option is nvidia_drm.

Offline

#5 2020-01-26 16:32:29

Tharbad
Member
Registered: 2016-02-27
Posts: 270

Re: [SOLVED] Black screen when returning from suspend

After a few days of testing: it's neither modset nor the suspend stuff.
But nomodset removed those lines from the log. Now there is no entries in the journal after the resume.

Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Unsupported base display class
Jan 20 19:47:06 <PC Name> kernel: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine base channels

Offline

#6 2020-02-02 12:47:43

Tharbad
Member
Registered: 2016-02-27
Posts: 270

Re: [SOLVED] Black screen when returning from suspend

Culprit found: linux. PC can return from suspend perfectly with linux-lts.
Where do I report this bug?

Offline

#7 2020-02-02 17:16:09

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: [SOLVED] Black screen when returning from suspend

https://bugzilla.kernel.org/

To be sure: you did install nvidia-lts w/ linux-lts, did you? Cause otherwise you'll have used the nouveau kernel module.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2020-02-02 19:47:59

Tharbad
Member
Registered: 2016-02-27
Posts: 270

Re: [SOLVED] Black screen when returning from suspend

seth wrote:

https://bugzilla.kernel.org/

To be sure: you did install nvidia-lts w/ linux-lts, did you? Cause otherwise you'll have used the nouveau kernel module.

nvidia-dkms

You scared me smile so I check the journal of the current boot:

nvidia: loading out-of-tree module taints kernel.
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  440.44  Sun Dec  8 03:38:56 UTC 2019

Seem OK.

Offline

Pages: 1

Board footer

Powered by FluxBB