Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

graysky · 2020-12-31 15:42:56

As of installing 5.10.4, the monitor wakes up from sleep but only displays black pixels. It's on but nothing is displayed in other words. Changing to text tty has no effect. Rebooting is the only way to get the monitor back.

Journalctl shows the following at the approx time this occurred:

Dec 31 10:19:55 ease kernel: INFO: task Xorg:604 blocked for more than 122 seconds.
Dec 31 10:19:55 ease kernel:       Not tainted 5.10.4-1-minimum #1
Dec 31 10:19:55 ease kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 31 10:19:55 ease kernel: task:Xorg            state:D stack:    0 pid:  604 ppid:   601 flags:0x00004000
Dec 31 10:19:55 ease kernel: Call Trace:
Dec 31 10:19:55 ease kernel:  __schedule+0x295/0x810
Dec 31 10:19:55 ease kernel:  schedule+0x5b/0xc0
Dec 31 10:19:55 ease kernel:  schedule_preempt_disabled+0x11/0x20
Dec 31 10:19:55 ease kernel:  __mutex_lock.constprop.0+0x17d/0x4f0
Dec 31 10:19:55 ease kernel:  ? gen6_write32+0x4b/0x1d0 [i915]
Dec 31 10:19:55 ease kernel:  sync_eld_via_acomp+0x3f/0x350 [snd_hda_codec_hdmi]
Dec 31 10:19:55 ease kernel:  check_presence_and_report+0x57/0x80 [snd_hda_codec_hdmi]
Dec 31 10:19:55 ease kernel:  intel_audio_codec_enable+0x12a/0x1a0 [i915]
Dec 31 10:19:55 ease kernel:  intel_enable_ddi+0x458/0x5a0 [i915]
Dec 31 10:19:55 ease kernel:  intel_encoders_enable+0x80/0xa0 [i915]
Dec 31 10:19:55 ease kernel:  hsw_crtc_enable+0x1ca/0x5d0 [i915]
Dec 31 10:19:55 ease kernel:  intel_enable_crtc+0x53/0x60 [i915]
Dec 31 10:19:55 ease kernel:  intel_commit_modeset_enables+0x53/0x80 [i915]
Dec 31 10:19:55 ease kernel:  intel_atomic_commit_tail+0x309/0x12d0 [i915]
Dec 31 10:19:55 ease kernel:  ? complete+0x2f/0x40
Dec 31 10:19:55 ease kernel:  ? flush_workqueue_prep_pwqs+0x117/0x130
Dec 31 10:19:55 ease kernel:  ? flush_workqueue+0x19d/0x3f0
Dec 31 10:19:55 ease kernel:  intel_atomic_commit+0x333/0x3b0 [i915]
Dec 31 10:19:55 ease kernel:  drm_atomic_connector_commit_dpms+0xda/0x100 [drm]
Dec 31 10:19:55 ease kernel:  drm_mode_obj_set_property_ioctl+0x196/0x3d0 [drm]
Dec 31 10:19:55 ease kernel:  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
Dec 31 10:19:55 ease kernel:  drm_connector_property_set_ioctl+0x39/0x60 [drm]
Dec 31 10:19:55 ease kernel:  drm_ioctl_kernel+0xb2/0x100 [drm]
Dec 31 10:19:55 ease kernel:  drm_ioctl+0x215/0x390 [drm]
Dec 31 10:19:55 ease kernel:  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
Dec 31 10:19:55 ease kernel:  __x64_sys_ioctl+0x83/0xb0
Dec 31 10:19:55 ease kernel:  do_syscall_64+0x33/0x40
Dec 31 10:19:55 ease kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 31 10:19:55 ease kernel: RIP: 0033:0x7f807222cf6b
Dec 31 10:19:55 ease kernel: RSP: 002b:00007ffe8accdde8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Dec 31 10:19:55 ease kernel: RAX: ffffffffffffffda RBX: 00007ffe8accde20 RCX: 00007f807222cf6b
Dec 31 10:19:55 ease kernel: RDX: 00007ffe8accde20 RSI: 00000000c01064ab RDI: 000000000000000e
Dec 31 10:19:55 ease kernel: RBP: 00000000c01064ab R08: 00005618632d39c8 R09: 0000000000000000
Dec 31 10:19:55 ease kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000561863468990
Dec 31 10:19:55 ease kernel: R13: 000000000000000e R14: 0000561863bdaef0 R15: 00000000000062bb
Dec 31 10:19:55 ease kernel: INFO: task kworker/3:2:2181929 blocked for more than 122 seconds.
Dec 31 10:19:55 ease kernel:       Not tainted 5.10.4-1-minimum #1
Dec 31 10:19:55 ease kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 31 10:19:55 ease kernel: task:kworker/3:2     state:D stack:    0 pid:2181929 ppid:     2 flags:0x00004000
Dec 31 10:19:55 ease kernel: Workqueue: events i915_hotplug_work_func [i915]
Dec 31 10:19:55 ease kernel: Call Trace:
Dec 31 10:19:55 ease kernel:  __schedule+0x295/0x810
Dec 31 10:19:55 ease kernel:  schedule+0x5b/0xc0
Dec 31 10:19:55 ease kernel:  schedule_preempt_disabled+0x11/0x20
Dec 31 10:19:55 ease kernel:  __ww_mutex_lock.constprop.0+0x255/0x810
Dec 31 10:19:55 ease kernel:  ? cpuacct_charge+0x32/0x80
Dec 31 10:19:55 ease kernel:  drm_modeset_lock+0x31/0xb0 [drm]
Dec 31 10:19:55 ease kernel:  drm_helper_probe_detect_ctx+0x6e/0x100 [drm_kms_helper]
Dec 31 10:19:55 ease kernel:  intel_encoder_hotplug+0x3d/0xe0 [i915]
Dec 31 10:19:55 ease kernel:  intel_ddi_hotplug+0x7a/0x3e0 [i915]
Dec 31 10:19:55 ease kernel:  ? sched_clock+0x5/0x10
Dec 31 10:19:55 ease kernel:  ? sched_clock_cpu+0xc/0xb0
Dec 31 10:19:55 ease kernel:  i915_hotplug_work_func+0x1db/0x2c0 [i915]
Dec 31 10:19:55 ease kernel:  process_one_work+0x1d6/0x3a0
Dec 31 10:19:55 ease kernel:  worker_thread+0x4d/0x3d0
Dec 31 10:19:55 ease kernel:  ? rescuer_thread+0x410/0x410
Dec 31 10:19:55 ease kernel:  kthread+0x133/0x150
Dec 31 10:19:55 ease kernel:  ? __kthread_bind_mask+0x60/0x60
Dec 31 10:19:55 ease kernel:  ret_from_fork+0x22/0x30
Dec 31 10:21:58 ease kernel: INFO: task Xorg:604 blocked for more than 245 seconds.
Dec 31 10:21:58 ease kernel:       Not tainted 5.10.4-1-minimum #1
Dec 31 10:21:58 ease kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 31 10:21:58 ease kernel: task:Xorg            state:D stack:    0 pid:  604 ppid:   601 flags:0x00004000
Dec 31 10:21:58 ease kernel: Call Trace:
Dec 31 10:21:58 ease kernel:  __schedule+0x295/0x810
Dec 31 10:21:58 ease kernel:  schedule+0x5b/0xc0
Dec 31 10:21:58 ease kernel:  schedule_preempt_disabled+0x11/0x20
Dec 31 10:21:58 ease kernel:  __mutex_lock.constprop.0+0x17d/0x4f0
Dec 31 10:21:58 ease kernel:  ? gen6_write32+0x4b/0x1d0 [i915]
Dec 31 10:21:58 ease kernel:  sync_eld_via_acomp+0x3f/0x350 [snd_hda_codec_hdmi]
Dec 31 10:21:58 ease kernel:  check_presence_and_report+0x57/0x80 [snd_hda_codec_hdmi]
Dec 31 10:21:58 ease kernel:  intel_audio_codec_enable+0x12a/0x1a0 [i915]
Dec 31 10:21:58 ease kernel:  intel_enable_ddi+0x458/0x5a0 [i915]
Dec 31 10:21:58 ease kernel:  intel_encoders_enable+0x80/0xa0 [i915]
Dec 31 10:21:58 ease kernel:  hsw_crtc_enable+0x1ca/0x5d0 [i915]
Dec 31 10:21:58 ease kernel:  intel_enable_crtc+0x53/0x60 [i915]
Dec 31 10:21:58 ease kernel:  intel_commit_modeset_enables+0x53/0x80 [i915]
Dec 31 10:21:58 ease kernel:  intel_atomic_commit_tail+0x309/0x12d0 [i915]
Dec 31 10:21:58 ease kernel:  ? complete+0x2f/0x40
Dec 31 10:21:58 ease kernel:  ? flush_workqueue_prep_pwqs+0x117/0x130
Dec 31 10:21:58 ease kernel:  ? flush_workqueue+0x19d/0x3f0
Dec 31 10:21:58 ease kernel:  intel_atomic_commit+0x333/0x3b0 [i915]
Dec 31 10:21:58 ease kernel:  drm_atomic_connector_commit_dpms+0xda/0x100 [drm]
Dec 31 10:21:58 ease kernel:  drm_mode_obj_set_property_ioctl+0x196/0x3d0 [drm]
Dec 31 10:21:58 ease kernel:  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
Dec 31 10:21:58 ease kernel:  drm_connector_property_set_ioctl+0x39/0x60 [drm]
Dec 31 10:21:58 ease kernel:  drm_ioctl_kernel+0xb2/0x100 [drm]
Dec 31 10:21:58 ease kernel:  drm_ioctl+0x215/0x390 [drm]
Dec 31 10:21:58 ease kernel:  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
Dec 31 10:21:58 ease kernel:  __x64_sys_ioctl+0x83/0xb0
Dec 31 10:21:58 ease kernel:  do_syscall_64+0x33/0x40
Dec 31 10:21:58 ease kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 31 10:21:58 ease kernel: RIP: 0033:0x7f807222cf6b
Dec 31 10:21:58 ease kernel: RSP: 002b:00007ffe8accdde8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Dec 31 10:21:58 ease kernel: RAX: ffffffffffffffda RBX: 00007ffe8accde20 RCX: 00007f807222cf6b
Dec 31 10:21:58 ease kernel: RDX: 00007ffe8accde20 RSI: 00000000c01064ab RDI: 000000000000000e
Dec 31 10:21:58 ease kernel: RBP: 00000000c01064ab R08: 00005618632d39c8 R09: 0000000000000000
Dec 31 10:21:58 ease kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000561863468990
Dec 31 10:21:58 ease kernel: R13: 000000000000000e R14: 0000561863bdaef0 R15: 00000000000062bb
Dec 31 10:21:58 ease kernel: INFO: task kworker/3:2:2181929 blocked for more than 245 seconds.
Dec 31 10:21:58 ease kernel:       Not tainted 5.10.4-1-minimum #1
Dec 31 10:21:58 ease kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 31 10:21:58 ease kernel: task:kworker/3:2     state:D stack:    0 pid:2181929 ppid:     2 flags:0x00004000
Dec 31 10:21:58 ease kernel: Workqueue: events i915_hotplug_work_func [i915]
Dec 31 10:21:58 ease kernel: Call Trace:
Dec 31 10:21:58 ease kernel:  __schedule+0x295/0x810
Dec 31 10:21:58 ease kernel:  schedule+0x5b/0xc0
Dec 31 10:21:58 ease kernel:  schedule_preempt_disabled+0x11/0x20
Dec 31 10:21:58 ease kernel:  __ww_mutex_lock.constprop.0+0x255/0x810
Dec 31 10:21:58 ease kernel:  ? cpuacct_charge+0x32/0x80
Dec 31 10:21:58 ease kernel:  drm_modeset_lock+0x31/0xb0 [drm]
Dec 31 10:21:58 ease kernel:  drm_helper_probe_detect_ctx+0x6e/0x100 [drm_kms_helper]
Dec 31 10:21:58 ease kernel:  intel_encoder_hotplug+0x3d/0xe0 [i915]
Dec 31 10:21:58 ease kernel:  intel_ddi_hotplug+0x7a/0x3e0 [i915]
Dec 31 10:21:58 ease kernel:  ? sched_clock+0x5/0x10
Dec 31 10:21:58 ease kernel:  ? sched_clock_cpu+0xc/0xb0
Dec 31 10:21:58 ease kernel:  i915_hotplug_work_func+0x1db/0x2c0 [i915]
Dec 31 10:21:58 ease kernel:  process_one_work+0x1d6/0x3a0
Dec 31 10:21:58 ease kernel:  worker_thread+0x4d/0x3d0
Dec 31 10:21:58 ease kernel:  ? rescuer_thread+0x410/0x410
Dec 31 10:21:58 ease kernel:  kthread+0x133/0x150
Dec 31 10:21:58 ease kernel:  ? __kthread_bind_mask+0x60/0x60
Dec 31 10:21:58 ease kernel:  ret_from_fork+0x22/0x30

To rule out my custom kernel, I enabled [testing], installed the official kernel, and got the bug to trigger. This time I found no such entries in journalctl. All I see there is myself connecting over ssh to issue the reboot command.

I have since disabled [testing] and downgraded all packages. After downgrading, I am not experiencing this. Seems like something in kernel v 5.10.4 is to blame. Has anyone else experienced this?

[2020-12-31T11:00:18-0500] [PACMAN] Running 'pacman -Suu'
[2020-12-31T11:00:18-0500] [PACMAN] starting full system upgrade
[2020-12-31T11:00:23-0500] [ALPM] running '60-mkinitcpio-remove.hook'...
[2020-12-31T11:00:23-0500] [ALPM] transaction started
[2020-12-31T11:00:23-0500] [ALPM] downgraded gdbm (1.19-1 -> 1.18.1-3)
[2020-12-31T11:00:23-0500] [ALPM] downgraded automake (1.16.3-1 -> 1.16.2-3)
[2020-12-31T11:00:23-0500] [ALPM] downgraded cronie (1.5.5-2 -> 1.5.5-1)
[2020-12-31T11:00:23-0500] [ALPM] downgraded libcap (2.46-1 -> 2.45-2)
[2020-12-31T11:00:23-0500] [ALPM] downgraded libelf (0.182-1 -> 0.181-1)
[2020-12-31T11:00:23-0500] [ALPM] downgraded elfutils (0.182-1 -> 0.181-1)
[2020-12-31T11:00:23-0500] [ALPM] downgraded groff (1.22.4-4 -> 1.22.4-3)
[2020-12-31T11:00:23-0500] [ALPM] downgraded libusb (1.0.24-1 -> 1.0.23-3)
[2020-12-31T11:00:24-0500] [ALPM] downgraded linux (5.10.4.arch1-1 -> 5.10.3.arch1-1)
[2020-12-31T11:00:24-0500] [ALPM] downgraded mesa (20.3.2-1 -> 20.3.1-1)
[2020-12-31T11:00:24-0500] [ALPM] downgraded openresolv (3.12.0-1 -> 3.11.0-1)
[2020-12-31T11:00:24-0500] [ALPM] downgraded psmisc (23.3-3 -> 23.3-2)
[2020-12-31T11:00:24-0500] [ALPM] downgraded python-urllib3 (1.26.2-1 -> 1.26.1-1)
[2020-12-31T11:00:24-0500] [ALPM] downgraded s-nail (14.9.20-1 -> 14.9.19-2)
[2020-12-31T11:00:24-0500] [ALPM] downgraded xfsprogs (5.10.0-1 -> 5.8.0-2)

Last edited by graysky (2020-12-31 18:59:42)

lomov_vl · 2021-01-03 11:57:26

Hello graysky.

Same here. I didn't wait linux-ck update and rebooted into linux-zen 5.10.4 from testing and found that Xorg hangs after monitor goes in power save mode, even keyboard becomes irresponsible, besides that all is working fine, I could ssh to the host. The funny thing is that I have two almost identical systems, one connected to a monitor by DVI-HDMI cable but the other one connected by HDMI-HDMI cable and that second host has a problem: I see almost the same messages in `dmesg` concerning `snd_hda_codec_hdmi`.

Now I'm using linux-ck (custom build) but see the same problem on the second host: it worked fine but as long as the monitor switched off (DMPS on) I see crashes in `dmesg`, Xorg hangs and keyboard is irresponsible.

Here (https://bbs.archlinux.org/viewtopic.php?id=262247) other guy reports the same (?) problem.

This is what I see in dmesg:

[72129.500531] INFO: task Xorg:698 blocked for more than 1228 seconds.
[72129.500533]       Not tainted 5.10.4-1-ck #1
[72129.500533] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[72129.500534] Xorg            D stack:    0 pid:  698 ppid:     1 flags:0x00004084
[72129.500536] Call Trace:
[72129.500540]  __schedule+0x5f7/0xd60
[72129.500542]  schedule+0x5b/0xc0
[72129.500543]  schedule_preempt_disabled+0x11/0x20
[72129.500544]  __mutex_lock.constprop.0+0x17d/0x4f0
[72129.500548]  sync_eld_via_acomp+0x3f/0x350 [snd_hda_codec_hdmi]
[72129.500550]  check_presence_and_report+0x57/0x80 [snd_hda_codec_hdmi]
[72129.500578]  intel_audio_codec_enable+0x11f/0x180 [i915]
[72129.500598]  intel_enable_ddi+0x446/0x5a0 [i915]
[72129.500617]  intel_encoders_enable+0x74/0xa0 [i915]
[72129.500634]  hsw_crtc_enable+0x1c3/0x5c0 [i915]
[72129.500652]  intel_enable_crtc+0x48/0x60 [i915]
[72129.500669]  skl_commit_modeset_enables+0x236/0x4e0 [i915]
[72129.500687]  intel_atomic_commit_tail+0x2c6/0x1230 [i915]
[72129.500689]  ? complete+0x2e/0x40
[72129.500690]  ? flush_workqueue_prep_pwqs+0x11e/0x130
[72129.500692]  ? flush_workqueue+0x19d/0x3f0
[72129.500709]  intel_atomic_commit+0x312/0x390 [i915]
[72129.500721]  drm_atomic_connector_commit_dpms+0xd9/0x100 [drm]
[72129.500729]  drm_mode_obj_set_property_ioctl+0x1bf/0x420 [drm]
[72129.500731]  ? filemap_fault+0x3f3/0x990
[72129.500738]  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
[72129.500744]  drm_connector_property_set_ioctl+0x39/0x60 [drm]
[72129.500749]  drm_ioctl_kernel+0xb3/0x100 [drm]
[72129.500755]  drm_ioctl+0x236/0x3d0 [drm]
[72129.500762]  ? drm_connector_set_obj_prop+0x90/0x90 [drm]
[72129.500765]  __x64_sys_ioctl+0x83/0xb0
[72129.500766]  do_syscall_64+0x33/0x40
[72129.500767]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

lomov_vl · 2021-01-03 12:14:08

Reported to drm/intel: https://gitlab.freedesktop.org/drm/intel/-/issues/2883

graysky · 2021-01-03 13:48:25

I should have posted the bug report I created: https://bugzilla.kernel.org/show_bug.cgi?id=210987

merlock · 2021-01-03 14:42:05

This is interesting. I don't have the specifics (clean my journal monthly); but I've suffered the exact same symptoms (except I'm connected via DVI), but on my AMD 560X,

Question for both of you: is your computer suspending, or is it just the monitor? In my case, I run F@H 24/7, and it's just the monitor that is suspending.

graysky · 2021-01-03 14:57:41

Just the monitor here.

ghen · 2021-01-03 16:37:48

Same here (see https://bbs.archlinux.org/viewtopic.php?pid=1947354), I cannot even kill -9 Xorg, and thus not shut down cleanly.

ghen · 2021-01-03 16:42:16

Fixed with 5.10.4-arch2-1: https://git.archlinux.org/linux.git/com … b011f90099

Last edited by ghen (2021-01-03 16:42:26)

graysky · 2021-01-03 16:48:12

@ghen - On my system, that commit allows the monitor to wake up from sleep, but it results in a kernel oops each time it wakes up. Better than before but something is still not right. I commented in FS#69190.

Last edited by graysky (2021-01-03 16:51:34)

ghen · 2021-01-03 16:52:53

Hm, it works for me though, I can wake the monitor back from sleep;

xset dpms force off; sleep 30; xset dpms force on

ghen · 2021-01-04 19:15:36

Actually now the monitor doesn't (automatically) suspend at all anymore.

bulletmark · 2021-01-04 23:13:38

With both 5.10.4.arch1-1 and 5.10.4.arch2-1 I get exactly the same problem as graysky, i.e. often my screen stays black after resume but I can ssh in to reboot. I've had various bugs with all the 5.10.1/2/3 kernels as they went through testing repo so keep having to go back to 5.9.14.arch1-1.

graysky · 2021-01-05 00:29:26

https://bugs.archlinux.org/task/69190

See loqs' suggestion. Have been running with that for a few days now without errors.

blufinney · 2021-01-07 04:58:19

I had the same issue.

linux-hardened-5.10.5.a-1 was released and fixed the issue.

I'm sure the non-hardened version will be released soon.

thanks!

graysky · 2021-01-07 11:10:07

I tried 5.10.5-rc1 and it did not fix the problem. The Arch patch by hefteg was applied to that. It prevents the monitor dying however, there are kernel oops each time it occurs.

quelcom · 2021-02-22 19:27:39

I had the same issue when I tried to switch to 5.10.17-1-lts (switching from 5.8.X stable).

System is based on an Intel J4105 (Intel UHD Graphics 600) and is plugged to a television through HDMI. If the TV is put on standby (or turn off completely), turning it back on after few minutes does not show anything on screen even though the computer is functional through SSH. Journalctl gives the same error and call trace.

I had to go back to 5.8.X.

graysky · 2021-02-22 21:09:42

The bug is still affecting me on 5.11.0 but only the kernel oops in dmesg. If I apply loqs' patch, it's fine.

Goldman · 2021-10-25 17:29:18

quelcom wrote:

I had the same issue when I tried to switch to 5.10.17-1-lts (switching from 5.8.X stable).
System is based on an Intel J4105 (Intel UHD Graphics 600) and is plugged to a television through HDMI. If the TV is put on standby (or turn off completely), turning it back on after few minutes does not show anything on screen even though the computer is functional through SSH. Journalctl gives the same error and call trace.
I had to go back to 5.8.X.

I have absolutely the same problem on my AsRock with Intel J4105 (Gemini Lake) it also plugged to a television through HDMI.
I tested it on fresh install with xfce and it is also crashed with any kernel above 5.10.

natedennis · 2022-12-22 02:35:51

ive been watching this mess for over 2 years now.. its borked on both my z390 pro with the 9900k and the WRX80 Creator R2.0 with the 5975wx.. it has something to do with the amd gpus... while i saw this issue with the same machines and the nvidia chipsets... it wasnt nearly as common. I REALLY wish someone would figure it out.

Arch Linux

#1 2020-12-31 15:42:56

Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#2 2021-01-03 11:57:26

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#3 2021-01-03 12:14:08

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#4 2021-01-03 13:48:25

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#5 2021-01-03 14:42:05

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#6 2021-01-03 14:57:41

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#7 2021-01-03 16:37:48

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#8 2021-01-03 16:42:16

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#9 2021-01-03 16:48:12

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#10 2021-01-03 16:52:53

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#11 2021-01-04 19:15:36

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#12 2021-01-04 23:13:38

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#13 2021-01-05 00:29:26

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#14 2021-01-07 04:58:19

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#15 2021-01-07 11:10:07

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#16 2021-02-22 19:27:39

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#17 2021-02-22 21:09:42

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#18 2021-10-25 17:29:18

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

#19 2022-12-22 02:35:51

Re: Kernel 5.10.4 - monitor wakes up but black only/no unlock screen

Board footer