Screens "Lose" Connection Upon Lock & Display Turning Off

[Arszilla]

Screens "Lose" Connection Upon Lock & Display Turning Off

[SebTM]

I would try something like xset dpms 1 && i3lock-color -i <composed image from betterlockscreen-cache> then (if it happens still) we would have sorted out that it mostly is an dpms/power management issue.

(Later you would need to manually reset dpms to 300 (5min) default with xset dpms 300)

If you notice, only 1 monitor is 16x9 while the other two are 9x16. The photo layouts for these 2 images are different, hence me specifying it in the arguments for betterlockscreen.

You got me on this, to early to small difference ;)

[Arszilla]

I am indeed connecting via USB-C, as the laptop in question is a Dell XPS 15, thus it has 3 USB-C inputs only, and all 3 monitors are connected via USB-C.

I'll see if the new upstream kernel for Kali (6.0.0-kali5-amd64) solves this issue and report back. Thanks for the post @SebTM!

[SebTM]

Guess it was a kernel issue with USB-C connections all along...

Sounds like it - so are you okay closing it for now?

[SebTM]

Do you really need the different images set normally Betterlockscreen detects the displays and uses the one provided image for all needed resolutions?

Also, does this issue happen if you you only lock your screen with i3lock-color and the generated image from .cache/betterlockscreen/? If yes it is a i3lock-color issue you should probably report upstream there.

On my 3 Monitor (2x Dell 27" and 1x eDP) with i3-gaps (NixOS), everything works fine with the external displays (even eDP-1 is inactive) on/after sleep. How do you connect these external Monitors? Is there some Kind of docking/displaylink-driver involved?

[Arszilla]

lso, does this issue happen if you you only lock your screen with i3lock-color and the generated image from .cache/betterlockscreen/? If yes it is a i3lock-color issue you should probably report upstream there.

I am a bit unsure how to replicate the issue on i3lock-color, but regardless, the latest release of i3lock-color is 2.13.c.4, which is the same version present in Kali Linux repositories:

$ sudo apt info i3lock-color
Package: i3lock-color
Version: 2.13.c.4-0kali1
Priority: optional
Section: utils
Maintainer: Kali Developers <[email protected]>
Installed-Size: 150 kB
Depends: libc6 (>= 2.33), libcairo2 (>= 1.6.4-5~), libev4 (>= 1:4.04), libfontconfig1 (>= 2.12.6), libjpeg62-turbo (>= 1.3.1), libpam0g (>= 0.99.7.1), libxcb-composite0, libxcb-image0 (>= 0.2.1), libxcb-randr0 (>= 1.12), libxcb-util1 (>= 0.4.0), libxcb-xinerama0, libxcb-xkb1, libxcb-xrm0 (>= 0.0.0), libxcb1, libxkbcommon-x11-0 (>= 0.5.0), libxkbcommon0 (>= 0.5.0)
Homepage: https://github.com/Raymo111/i3lock-color
Download-Size: 50.8 kB
APT-Manual-Installed: no
APT-Sources: http://http.kali.org/kali kali-rolling/main amd64 Packages
Description: Improved screen locker
 A modern version of i3lock with color functionality
 .
 i3lock is a simple screen locker like slock. After starting it, you will see a
 white screen (you can configure the color/an image).  You can return to your
 screen by entering your password.

Given that I was one of the people who helped the Kali Linux package betterlockscreen and i3lock-color alongside a few other packages used in Kali i3-gaps, I tend to watch out if the packages are outdated when compared to the mainstream. Thus I feel i3lock-color is not the cause, but I am happy to test it and prove it.

Do you really need the different images set normally Betterlockscreen detects the displays and uses the one provided image for all needed resolutions?

If you notice, only 1 monitor is 16x9 while the other two are 9x16. The photo layouts for these 2 images are different, hence me specifying it in the arguments for betterlockscreen.

[Arszilla]

So as soon as I can xset dpms 1 && i3lock -i .cache/betterlockscreen/current (when I had the i3lock-color command incorrectly specified), the screen acting crazy, maybe because I messed with dpms). As a result, I just ran i3lock -i .cache/betterlockscreen/current and let it idle for 5-10 mins. Screen went black after a while, moved my mouse/touched a key in my keyboard and my displays came back up normally.

Maybe it's dpms acting up all this time? However, I've set Kali i3-gaps (since release) to use xfce4-power-manager (which is at v4.16.0-1) since I started working on the project 2-3 years ago, since IIRC Manjaro i3-gaps used xfce4-power-manager as well.

However, I use a custom xfce4-power-manager setting, where my displays are never turned off or become inactive etc. The only thing turning my displays off at a given time is betterlockscreen due to the default 5 minute timer. I tried setting --off to 86400 seconds (i.e. a day), but I came to my office the next day to notice my displays turned off regardless. 🤔

[SebTM]

Could you maybe retry the test with a value >10|<100 because it is seconds I could see some cases where 1 cause this behavior.

Maybe it's dpms acting up all this time?
. I tried setting --off to 86400 seconds (i.e. a day), but I came to my office the next day to notice my displays turned off regardless. thinking

It seems so, from the code DPMS is enabled if the device says it's supported, you could comment out the prelock/postlock code to disable it. We could implement a config-option to manual disable DPMS for such cases if we can't find the problems source/fix it.

[Arszilla]

Could you maybe retry the test with a value >10|<100 because it is seconds I could see some cases where 1 cause this behavior.

I just tried it with xset dpms 15 && i3lock -i .cache/betterlockscreen/current. First, after 15 seconds, all displays turned off, and when I moved my mouse, all of them came back. Repeating the test again, only DP-1 came back to life, so it is related to dpms from what I can see.

If possible I'd appreciate a fix that is universal, so I can push the changes to Kali's package. I have no issues doing a local fix, but I feel it'll be better for everyone (down the line) if it's a universal fix, in case someone else experiences the same issue.

[SebTM]

Okay, I see could you check your journalctl / syslog / systemd-logs for errors/unexpected messages / maybe DMPS, maybe power-managment related?

Yeah we can do but for me it's a last resort, the better solution would be to find the source of the problem and fix this :)

[Arszilla]

Apologies for the radio silence. Due to the workload, it might take me a day or two to get the journalctl logs. I'll also make sure they are available (or at least the relevant bits) via gist or my next reply.

[Arszilla]

So I was just made aware that i3-gaps and i3 are merging, thus this may take a little bit longer: https://www.reddit.com/r/i3wm/comments/yjeoc9/psa_i3gaps_has_been_merged_into_i3/. I'll take a look at my journalctl regardless in a bit.

[Arszilla]

So, taking a look, I saw this highlighted in yellow:

Nov 03 09:21:48 kali-dell kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_mode != TC_PORT_DISCONNECTED)
Nov 03 09:21:48 kali-dell kernel: WARNING: CPU: 15 PID: 351284 at drivers/gpu/drm/i915/display/intel_tc.c:710 intel_tc_po>
Nov 03 09:21:48 kali-dell kernel: Modules linked in: hid_logitech_hidpp hid_logitech_dj r8153_ecm cdc_ether usbnet r8152 >
Nov 03 09:21:48 kali-dell kernel:  coretemp btrtl snd_hda_intel btbcm vmwgfx btintel snd_intel_dspcfg btmtk kvm_intel snd>
Nov 03 09:21:48 kali-dell kernel:  rfkill ecc int3403_thermal soc_button_array int340x_thermal_zone evdev int3400_thermal>
Nov 03 09:21:48 kali-dell kernel: CPU: 15 PID: 351284 Comm: kworker/u32:67 Tainted: P        W  O      5.19.0-kali2-amd64>
Nov 03 09:21:48 kali-dell kernel: Hardware name: Dell Inc. XPS 15 9510/01V4T3, BIOS 1.7.0 12/09/2021
Nov 03 09:21:48 kali-dell kernel: Workqueue: events_unbound async_run_entry_fn
Nov 03 09:21:48 kali-dell kernel: RIP: 0010:intel_tc_port_sanitize+0x2c1/0x4d0 [i915]
Nov 03 09:21:48 kali-dell kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 78 16 db cd 48 c7 c1 88 08 dc c0 4c 89 ea >
Nov 03 09:21:48 kali-dell kernel: RSP: 0018:ffffb6d5c513bbf8 EFLAGS: 00010282
Nov 03 09:21:48 kali-dell kernel: RAX: 0000000000000000 RBX: ffff891dcc848000 RCX: 0000000000000000
Nov 03 09:21:48 kali-dell kernel: RDX: 0000000000000001 RSI: ffffffff8f56f34b RDI: 00000000ffffffff
Nov 03 09:21:48 kali-dell kernel: RBP: ffff891e0390a000 R08: 0000000000000049 R09: 0000000090535022
Nov 03 09:21:48 kali-dell kernel: R10: ffffffffffffffff R11: ffffffff8fcc6040 R12: ffff891e0390af80
Nov 03 09:21:48 kali-dell kernel: R13: ffff891dc2181ef0 R14: ffffffffc0dd76e6 R15: 0000000000000000
Nov 03 09:21:48 kali-dell kernel: FS:  0000000000000000(0000) GS:ffff89252f7c0000(0000) knlGS:0000000000000000
Nov 03 09:21:48 kali-dell kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 03 09:21:48 kali-dell kernel: CR2: 00005604c0106300 CR3: 000000082ba10002 CR4: 0000000000770ee0
Nov 03 09:21:48 kali-dell kernel: PKRU: 55555554
Nov 03 09:21:48 kali-dell kernel: Call Trace:
Nov 03 09:21:48 kali-dell kernel:  <TASK>
Nov 03 09:21:48 kali-dell kernel:  intel_ddi_sync_state+0x40/0x90 [i915]
Nov 03 09:21:48 kali-dell kernel:  intel_modeset_setup_hw_state+0x408/0x1680 [i915]
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_lock_irq+0x19/0x40
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_unlock_irq+0x1b/0x35
Nov 03 09:21:48 kali-dell kernel:  ? __wait_for_common+0x19f/0x1d0
Nov 03 09:21:48 kali-dell kernel:  ? usleep_range_state+0x90/0x90
Nov 03 09:21:48 kali-dell kernel:  ? ww_mutex_lock+0x15/0x80
Nov 03 09:21:48 kali-dell kernel:  ? __intel_display_resume+0x1c/0xf0 [i915]
Nov 03 09:21:48 kali-dell kernel:  __intel_display_resume+0x1c/0xf0 [i915]
Nov 03 09:21:48 kali-dell kernel:  intel_display_resume+0x8d/0x110 [i915]
Nov 03 09:21:48 kali-dell kernel:  i915_drm_resume+0xcc/0x130 [i915]
Nov 03 09:21:48 kali-dell kernel:  ? pci_legacy_resume+0x80/0x80
Nov 03 09:21:48 kali-dell kernel:  dpm_run_callback+0x47/0x150
Nov 03 09:21:48 kali-dell kernel:  device_resume+0x8b/0x190
Nov 03 09:21:48 kali-dell kernel:  async_resume+0x19/0x30
Nov 03 09:21:48 kali-dell kernel:  async_run_entry_fn+0x2d/0x130
Nov 03 09:21:48 kali-dell kernel:  process_one_work+0x1e2/0x3b0
Nov 03 09:21:48 kali-dell kernel:  worker_thread+0x50/0x3a0
Nov 03 09:21:48 kali-dell kernel:  ? rescuer_thread+0x390/0x390
Nov 03 09:21:48 kali-dell kernel:  kthread+0xe5/0x110
Nov 03 09:21:48 kali-dell kernel:  ? kthread_complete_and_exit+0x20/0x20
Nov 03 09:21:48 kali-dell kernel:  ret_from_fork+0x1f/0x30
Nov 03 09:21:48 kali-dell kernel:  </TASK>
Nov 03 09:21:48 kali-dell kernel: ---[ end trace 0000000000000000 ]---
Nov 03 09:21:48 kali-dell kernel: ------------[ cut here ]------------
Nov 03 09:21:48 kali-dell kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_lock_wakeref)
Nov 03 09:21:48 kali-dell kernel: WARNING: CPU: 15 PID: 351284 at drivers/gpu/drm/i915/display/intel_tc.c:711 intel_tc_po>
Nov 03 09:21:48 kali-dell kernel: Modules linked in: hid_logitech_hidpp hid_logitech_dj r8153_ecm cdc_ether usbnet r8152 >
Nov 03 09:21:48 kali-dell kernel:  coretemp btrtl snd_hda_intel btbcm vmwgfx btintel snd_intel_dspcfg btmtk kvm_intel snd>
Nov 03 09:21:48 kali-dell kernel:  rfkill ecc int3403_thermal soc_button_array int340x_thermal_zone evdev int3400_thermal>
Nov 03 09:21:48 kali-dell kernel: CPU: 15 PID: 351284 Comm: kworker/u32:67 Tainted: P        W  O      5.19.0-kali2-amd64>
Nov 03 09:21:48 kali-dell kernel: Hardware name: Dell Inc. XPS 15 9510/01V4T3, BIOS 1.7.0 12/09/2021
Nov 03 09:21:48 kali-dell kernel: Workqueue: events_unbound async_run_entry_fn
Nov 03 09:21:48 kali-dell kernel: RIP: 0010:intel_tc_port_sanitize+0x2ff/0x4d0 [i915]
Nov 03 09:21:48 kali-dell kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 3a 16 db cd 48 c7 c1 c0 08 dc c0 4c 89 ea >
Nov 03 09:21:48 kali-dell kernel: RSP: 0018:ffffb6d5c513bbf8 EFLAGS: 00010282
Nov 03 09:21:48 kali-dell kernel: RAX: 0000000000000000 RBX: ffff891dcc848000 RCX: 0000000000000000
Nov 03 09:21:48 kali-dell kernel: RDX: 0000000000000001 RSI: ffffffff8f56f34b RDI: 00000000ffffffff
Nov 03 09:21:48 kali-dell kernel: RBP: ffff891e0390a000 R08: 0000000000000039 R09: 000000009053659a
Nov 03 09:21:48 kali-dell kernel: R10: ffffffffffffffff R11: ffffffff8fcba1a8 R12: ffff891e0390af80
Nov 03 09:21:48 kali-dell kernel: R13: ffff891dc2181ef0 R14: ffffffffc0dd76e6 R15: 0000000000000000
Nov 03 09:21:48 kali-dell kernel: FS:  0000000000000000(0000) GS:ffff89252f7c0000(0000) knlGS:0000000000000000
Nov 03 09:21:48 kali-dell kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 03 09:21:48 kali-dell kernel: CR2: 00005604c0106300 CR3: 000000082ba10002 CR4: 0000000000770ee0
Nov 03 09:21:48 kali-dell kernel: PKRU: 55555554
Nov 03 09:21:48 kali-dell kernel: Call Trace:
Nov 03 09:21:48 kali-dell kernel:  <TASK>
Nov 03 09:21:48 kali-dell kernel:  intel_ddi_sync_state+0x40/0x90 [i915]
Nov 03 09:21:48 kali-dell kernel:  intel_modeset_setup_hw_state+0x408/0x1680 [i915]
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_lock_irq+0x19/0x40
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_lock_irq+0x19/0x40
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_unlock_irq+0x1b/0x35
Nov 03 09:21:48 kali-dell kernel:  ? __wait_for_common+0x19f/0x1d0
Nov 03 09:21:48 kali-dell kernel:  ? usleep_range_state+0x90/0x90
Nov 03 09:21:48 kali-dell kernel:  ? ww_mutex_lock+0x15/0x80
Nov 03 09:21:48 kali-dell kernel:  ? __intel_display_resume+0x1c/0xf0 [i915]
Nov 03 09:21:48 kali-dell kernel:  __intel_display_resume+0x1c/0xf0 [i915]
Nov 03 09:21:48 kali-dell kernel:  intel_display_resume+0x8d/0x110 [i915]
Nov 03 09:21:48 kali-dell kernel:  i915_drm_resume+0xcc/0x130 [i915]
Nov 03 09:21:48 kali-dell kernel:  ? pci_legacy_resume+0x80/0x80
Nov 03 09:21:48 kali-dell kernel:  dpm_run_callback+0x47/0x150
Nov 03 09:21:48 kali-dell kernel:  device_resume+0x8b/0x190
Nov 03 09:21:48 kali-dell kernel:  async_resume+0x19/0x30
Nov 03 09:21:48 kali-dell kernel:  async_run_entry_fn+0x2d/0x130
Nov 03 09:21:48 kali-dell kernel:  process_one_work+0x1e2/0x3b0
Nov 03 09:21:48 kali-dell kernel:  worker_thread+0x50/0x3a0
Nov 03 09:21:48 kali-dell kernel:  ? rescuer_thread+0x390/0x390
Nov 03 09:21:48 kali-dell kernel:  kthread+0xe5/0x110
Nov 03 09:21:48 kali-dell kernel:  ? kthread_complete_and_exit+0x20/0x20
Nov 03 09:21:48 kali-dell kernel:  ret_from_fork+0x1f/0x30
Nov 03 09:21:48 kali-dell kernel:  </TASK>
Nov 03 09:21:48 kali-dell kernel: ---[ end trace 0000000000000000 ]---
Nov 03 09:21:48 kali-dell kernel: ------------[ cut here ]------------
Nov 03 09:21:48 kali-dell kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_lock_wakeref)
Nov 03 09:21:48 kali-dell kernel: WARNING: CPU: 15 PID: 351284 at drivers/gpu/drm/i915/display/intel_tc.c:711 intel_tc_po>
Nov 03 09:21:48 kali-dell kernel: Modules linked in: hid_logitech_hidpp hid_logitech_dj r8153_ecm cdc_ether usbnet r8152 >
Nov 03 09:21:48 kali-dell kernel:  coretemp btrtl snd_hda_intel btbcm vmwgfx btintel snd_intel_dspcfg btmtk kvm_intel snd>
Nov 03 09:21:48 kali-dell kernel:  rfkill ecc int3403_thermal soc_button_array int340x_thermal_zone evdev int3400_thermal>
Nov 03 09:21:48 kali-dell kernel: CPU: 15 PID: 351284 Comm: kworker/u32:67 Tainted: P        W  O      5.19.0-kali2-amd64>
Nov 03 09:21:48 kali-dell kernel: Hardware name: Dell Inc. XPS 15 9510/01V4T3, BIOS 1.7.0 12/09/2021
Nov 03 09:21:48 kali-dell kernel: Workqueue: events_unbound async_run_entry_fn
Nov 03 09:21:48 kali-dell kernel: RIP: 0010:intel_tc_port_sanitize+0x2ff/0x4d0 [i915]
Nov 03 09:21:48 kali-dell kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 3a 16 db cd 48 c7 c1 c0 08 dc c0 4c 89 ea >
Nov 03 09:21:48 kali-dell kernel: RSP: 0018:ffffb6d5c513bbf8 EFLAGS: 00010282
Nov 03 09:21:48 kali-dell kernel: RAX: 0000000000000000 RBX: ffff891dcc848000 RCX: 0000000000000000
Nov 03 09:21:48 kali-dell kernel: RDX: 0000000000000001 RSI: ffffffff8f56f34b RDI: 00000000ffffffff
Nov 03 09:21:48 kali-dell kernel: RBP: ffff891e0390a000 R08: 0000000000000039 R09: 000000009053659a
Nov 03 09:21:48 kali-dell kernel: R10: ffffffffffffffff R11: ffffffff8fcba1a8 R12: ffff891e0390af80
Nov 03 09:21:48 kali-dell kernel: R13: ffff891dc2181ef0 R14: ffffffffc0dd76e6 R15: 0000000000000000
Nov 03 09:21:48 kali-dell kernel: FS:  0000000000000000(0000) GS:ffff89252f7c0000(0000) knlGS:0000000000000000
Nov 03 09:21:48 kali-dell kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 03 09:21:48 kali-dell kernel: CR2: 00005604c0106300 CR3: 000000082ba10002 CR4: 0000000000770ee0
Nov 03 09:21:48 kali-dell kernel: PKRU: 55555554
Nov 03 09:21:48 kali-dell kernel: Call Trace:
Nov 03 09:21:48 kali-dell kernel:  <TASK>
Nov 03 09:21:48 kali-dell kernel:  intel_ddi_sync_state+0x40/0x90 [i915]
Nov 03 09:21:48 kali-dell kernel:  intel_modeset_setup_hw_state+0x408/0x1680 [i915]
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_lock_irq+0x19/0x40
Nov 03 09:21:48 kali-dell kernel:  ? _raw_spin_unlock_irq+0x1b/0x35
Nov 03 09:21:48 kali-dell kernel:  ? __wait_for_common+0x19f/0x1d0
Nov 03 09:21:48 kali-dell kernel:  ? usleep_range_state+0x90/0x90
Nov 03 09:21:48 kali-dell kernel:  ? ww_mutex_lock+0x15/0x80
Nov 03 09:21:48 kali-dell kernel:  ? __intel_display_resume+0x1c/0xf0 [i915]
Nov 03 09:21:48 kali-dell kernel:  __intel_display_resume+0x1c/0xf0 [i915]
Nov 03 09:21:48 kali-dell kernel:  intel_display_resume+0x8d/0x110 [i915]
Nov 03 09:21:48 kali-dell kernel:  i915_drm_resume+0xcc/0x130 [i915]
Nov 03 09:21:48 kali-dell kernel:  ? pci_legacy_resume+0x80/0x80
Nov 03 09:21:48 kali-dell kernel:  dpm_run_callback+0x47/0x150
Nov 03 09:21:48 kali-dell kernel:  device_resume+0x8b/0x190
Nov 03 09:21:48 kali-dell kernel:  async_resume+0x19/0x30
Nov 03 09:21:48 kali-dell kernel:  async_run_entry_fn+0x2d/0x130
Nov 03 09:21:48 kali-dell kernel:  process_one_work+0x1e2/0x3b0
Nov 03 09:21:48 kali-dell kernel:  worker_thread+0x50/0x3a0
Nov 03 09:21:48 kali-dell kernel:  ? rescuer_thread+0x390/0x390
Nov 03 09:21:48 kali-dell kernel:  kthread+0xe5/0x110
Nov 03 09:21:48 kali-dell kernel:  ? kthread_complete_and_exit+0x20/0x20
Nov 03 09:21:48 kali-dell kernel:  ret_from_fork+0x1f/0x30
Nov 03 09:21:48 kali-dell kernel:  </TASK>
Nov 03 09:21:48 kali-dell kernel: ---[ end trace 0000000000000000 ]---

Besides this, there are issues regarding my pulseaudio or iwlwifi that I know about. However, all of the logs from my wake from suspend are available here. I'll also take a look at the one from boot when I can.

[SebTM]

Sorry for the delay, seems to be something kernel/driver related nothing I can really help/solve here.
I would suggest try to get the newest kernel/driver as possible and otherwise try to report the issue upstream to you distro/the driver. (If you are connecting via usb-c I found something which could be related: https://patchwork.kernel.org/project/intel-gfx/patch/[email protected]/)

[Arszilla]

An update: Been on 6.0.0 kernel for the better part of 2+ weeks:

$ uname -r
6.0.0-kali6-amd64

Despite the --off 86400 flag for betterlockscreen, I've noticed the display does not stay on 24 hours and suspends (I usually lock my laptop before I leave my office and come back 16 hours later to see it suspended). But I've noticed that when waking from suspend, the issue doesn't replicate anymore lately.

Guess it was a kernel issue with USB-C connections all along...