Score:0

no screen at 3rd or 4th wakeup ( ubuntu 20.04 )

sz flag
  • since I plugged an HDMI monitor to my DELL laptop, it no longer wants to display elsewhere, even if no plug connected ( but for the boot sequence ). ( xrandr doesn't see the laptop screen. )
  • every 3rd or 4th wakeup, I get no display at all, despite activity is restarting ( fan, disk, ... ).

here are excerpts of syslog that seem to show suspicious things:

sleep:

Feb 22 09:28:56 vortex2 systemd[1]: nvidia-suspend.service: Succeeded.
Feb 22 09:28:56 vortex2 systemd[1]: Finished NVIDIA system suspend actions.
Feb 22 09:28:56 vortex2 systemd[1]: Starting Suspend...
Feb 22 09:28:56 vortex2 systemd-sleep[27921]: Suspending system...
Feb 22 09:28:56 vortex2 kernel: [13256.266448] PM: suspend entry (deep)



wake up:

Feb 22 20:40:22 vortex2 kernel: [13256.679851] Filesystems sync: 0.413 seconds
...
Feb 22 20:40:35 vortex2 kernel: [13271.501572] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
Feb 22 20:40:35 vortex2 kernel: [13271.501868] NVRM: GPU at PCI:0000:01:00: GPU-955b6485-f807-7430-f096-da535ffc5530
Feb 22 20:40:35 vortex2 kernel: [13271.501869] NVRM: Xid (PCI:0000:01:00): 56, pid=28023, CMDre 00000000 00000088 0001000a 00000007 00000000
Feb 22 20:40:35 vortex2 kernel: [13271.506160] NVRM: Xid (PCI:0000:01:00): 56, pid=28023, CMDre 00000000 0000008c 00000000 00000005 0000102b
Feb 22 20:40:45 vortex2 nm-applet[2422]: Failed to show notification: Le délai d’attente est dépassé
Feb 22 20:41:33 vortex2 kernel: [13329.527216] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000917d:0:0:428
Feb 22 20:42:56 vortex2 kernel: [13413.044102] INFO: task nvidia-modeset/:271 blocked for more than 120 seconds.
Feb 22 20:42:56 vortex2 kernel: [13413.044147]       Tainted: P           OE     5.4.0-100-generic #113-Ubuntu
Feb 22 20:42:56 vortex2 kernel: [13413.044180] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 22 20:42:56 vortex2 kernel: [13413.044218] nvidia-modeset/ D    0   271      2 0x80004000
Feb 22 20:42:56 vortex2 kernel: [13413.044221] Call Trace:
Feb 22 20:42:56 vortex2 kernel: [13413.044230]  __schedule+0x2e3/0x740
Feb 22 20:42:56 vortex2 kernel: [13413.044233]  schedule+0x42/0xb0
Feb 22 20:42:56 vortex2 kernel: [13413.044236]  rwsem_down_read_slowpath+0x16c/0x4a0
Feb 22 20:42:56 vortex2 kernel: [13413.044238]  down_read+0x85/0xa0
Feb 22 20:42:56 vortex2 kernel: [13413.044260]  nvkms_kthread_q_callback+0x6a/0x100 [nvidia_modeset]
Feb 22 20:42:56 vortex2 kernel: [13413.044273]  _main_loop+0x8c/0x140 [nvidia_modeset]
Feb 22 20:42:56 vortex2 kernel: [13413.044277]  kthread+0x104/0x140
Feb 22 20:42:56 vortex2 kernel: [13413.044290]  ? _raw_q_schedule+0x70/0x70 [nvidia_modeset]
Feb 22 20:42:56 vortex2 kernel: [13413.044292]  ? kthread_park+0x90/0x90
Feb 22 20:42:56 vortex2 kernel: [13413.044294]  ret_from_fork+0x35/0x40
Feb 22 20:43:23 vortex2 systemd[1]: systemd-suspend.service: State 'stop-sigterm' timed out. Killing.
Feb 22 20:43:23 vortex2 systemd[1]: systemd-suspend.service: Killing process 28023 (nvidia-sleep.sh) with signal SIGKILL.
Feb 22 20:44:53 vortex2 systemd[1]: systemd-suspend.service: State 'stop-final-sigterm' timed out. Killing.
Feb 22 20:44:53 vortex2 systemd[1]: systemd-suspend.service: Killing process 28023 (nvidia-sleep.sh) with signal SIGKILL.
Feb 22 20:44:53 vortex2 ModemManager[1229]: <info>  [sleep-monitor] system is resuming
Feb 22 20:44:53 vortex2 systemd[1]: systemd-suspend.service: Failed with result 'timeout'.
Feb 22 20:44:53 vortex2 suspend: nvidia-resume.service
Feb 22 20:44:53 vortex2 logger[28137]: <13>Feb 22 20:44:53 suspend: nvidia-resume.service
Feb 22 20:44:53 vortex2 systemd[1]: Failed to start Suspend.
Feb 22 20:44:53 vortex2 systemd[1]: Dependency failed for Suspend.
Feb 22 20:44:53 vortex2 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Feb 22 20:44:53 vortex2 systemd[1]: Stopped target Sleep.
Feb 22 20:44:53 vortex2 systemd[1]: Starting NVIDIA system resume actions...

Feb 22 20:44:53 vortex2 NetworkManager[1043]: <info>  [1645559093.5194] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Feb 22 20:44:53 vortex2 NetworkManager[1043]: <info>  [1645559093.5195] device (eno1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 22 20:44:53 vortex2 NetworkManager[1043]: <info>  [1645559093.5985] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Feb 22 20:44:53 vortex2 kernel: [13530.054866] e1000e: eno1 NIC Link is Down
Feb 22 20:44:53 vortex2 NetworkManager[1043]: <info>  [1645559093.7905] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Feb 22 20:44:54 vortex2 NetworkManager[1043]: <info>  [1645559094.0527] device (p2p-dev-wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Feb 22 20:44:54 vortex2 NetworkManager[1043]: <info>  [1645559094.0534] manager: NetworkManager state is now DISCONNECTED
Feb 22 20:44:54 vortex2 NetworkManager[1043]: <info>  [1645559094.5092] sup-iface[0x561bdd2bc300,wlp3s0]: supports 5 scan SSIDs
Feb 22 20:44:54 vortex2 NetworkManager[1043]: <info>  [1645559094.5099] device (wlp3s0): supplicant interface state: starting -> ready
Feb 22 20:44:54 vortex2 NetworkManager[1043]: <info>  [1645559094.5100] device (p2p-dev-wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Feb 22 20:44:54 vortex2 NetworkManager[1043]: <info>  [1645559094.5103] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Feb 22 20:44:56 vortex2 ModemManager[1229]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Feb 22 20:44:56 vortex2 ModemManager[1229]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0': not supported by any plugin
Feb 22 20:44:57 vortex2 kernel: [13533.878856] INFO: task nvidia-modeset/:271 blocked for more than 241 seconds.
Feb 22 20:44:57 vortex2 kernel: [13533.878900]       Tainted: P           OE     5.4.0-100-generic #113-Ubuntu
Feb 22 20:44:57 vortex2 kernel: [13533.878933] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 22 20:44:57 vortex2 kernel: [13533.878971] nvidia-modeset/ D    0   271      2 0x80004000
Feb 22 20:44:57 vortex2 kernel: [13533.878973] Call Trace:
Feb 22 20:44:57 vortex2 kernel: [13533.878982]  __schedule+0x2e3/0x740
Feb 22 20:44:57 vortex2 kernel: [13533.878985]  schedule+0x42/0xb0
Feb 22 20:44:57 vortex2 kernel: [13533.878988]  rwsem_down_read_slowpath+0x16c/0x4a0
Feb 22 20:44:57 vortex2 kernel: [13533.878991]  down_read+0x85/0xa0
Feb 22 20:44:57 vortex2 kernel: [13533.879015]  nvkms_kthread_q_callback+0x6a/0x100 [nvidia_modeset]
Feb 22 20:44:57 vortex2 kernel: [13533.879029]  _main_loop+0x8c/0x140 [nvidia_modeset]
Feb 22 20:44:57 vortex2 kernel: [13533.879033]  kthread+0x104/0x140
Feb 22 20:44:57 vortex2 kernel: [13533.879045]  ? _raw_q_schedule+0x70/0x70 [nvidia_modeset]
Feb 22 20:44:57 vortex2 kernel: [13533.879047]  ? kthread_park+0x90/0x90
Feb 22 20:44:57 vortex2 kernel: [13533.879049]  ret_from_fork+0x35/0x40
...
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.