Screen off after undocking

fANZYo · 2019-09-13 08:28:06

Hi, I am not that new to arch but feel like i don't know much about it either.

I have a Dell Latitude 5591 which I am using for work, I hook it in the morning to two screens via both usb-c and hdmi and use xrandr to toggle them on or off. I'm running i3 and use these for the toggle.

exec --no-startup-id "xrandr --output HDMI1 --auto --primary --output DP1 --auto --right-of HDMI1"

exec --no-startup-id "xrandr --output HDMI1 --off --output DP1 --off --output eDP1 --primary"

In the evening when leaving the office I turn the screens off, undock and shut the lid of my laptop. When I open my laptop again the screen won't turn on no matter what I do, I don't believe it to be in hibernation as the power button isn't responsive. I have to hold the power button to shut it down and then on again.

To be clear this problem only appears in relation to docking and undocking. This problem is not present when I just shut the lid and open it again outside of docking.

I am not sure where to find logs for this as when the problem is there I don't have a screen (and my debugging knowledge of Arch is close to nonexistent)

Hope you can help
Thanks in advance

jasonwryan · 2019-09-13 08:35:07

Compare the journal for a successful resume and a failed one...

Moving to NC.

fANZYo · 2019-09-13 08:41:05

How do i get the unsuccessful resume with no screen?

jasonwryan · 2019-09-13 08:45:28

https://wiki.archlinux.org/index.php/Sy … ing_output

fANZYo · 2019-09-13 09:18:40

Oh awesome, Thanks for that.

So it seems the laptop just doesn't wake up from sleep after opening the lid after undocking. The last message of the previous boot is:

Sep 11 17:21:35 frankenstein systemd[1]: Reached target Sleep.
-- Subject: A start job for unit sleep.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit sleep.target has finished successfully.
-- 
-- The job identifier is 2809.
Sep 11 17:21:35 frankenstein systemd[1]: Starting Suspend...
-- Subject: A start job for unit systemd-suspend.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-suspend.service has begun execution.
-- 
-- The job identifier is 2806.
Sep 11 17:21:35 frankenstein systemd-sleep[1998582]: Suspending system...
-- Subject: System sleep state suspend entered
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The system has now entered the suspend sleep state.
Sep 11 17:21:35 frankenstein kernel: PM: suspend entry (deep)

PS: the power button is completely unresponsive though so it is a problem

Last edited by fANZYo (2019-09-13 10:27:45)

seth · 2019-09-13 13:38:25

This seems contradictive?

I turn the screens off, undock and shut the lid of my laptop

problem is not present when I just shut the lid and open it again outside of docking

fANZYo · 2019-09-13 14:26:28

What I mean is that, in the scenario where is shut the lid after undocking and then open my laptop again, the screen wont turn back on (it's in hibernation and nothing seem to wake it up). In the scenario where is didn't undock previously shutting the lid and opening it again wakes the laptop with no issues. So currently every time I undock i have to reboot the laptop.

seth · 2019-09-13 14:41:43

In either case the notebook is not docked when you S3, does it maybe rather matter whether the notebook is docked during the boot?

fANZYo · 2019-09-13 14:48:44

It's never docked when I boot. Before I started this job my laptop would be permanently on.

seth · 2019-09-13 14:59:37

The dock/undock maneuver will trigger something, likely power management related - and that ultimately screws the S3.
=> Check the journal right and after before the first dock and undock actions for what happens at this point.
In case you intend to post that, please omit the "-x"

fANZYo · 2019-09-17 17:17:20

This is what I get from the previous boot when the screen stays off

Sep 17 16:46:42 frankenstein kernel: PM: suspend entry (deep)
Sep 17 16:46:43 frankenstein kernel: PM: Syncing filesystems ... done.
Sep 17 16:46:43 frankenstein kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Sep 17 16:46:43 frankenstein kernel: OOM killer disabled.
Sep 17 16:46:43 frankenstein kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Sep 17 16:46:43 frankenstein kernel: Suspending console(s) (use no_console_suspend to debug)
Sep 17 16:46:43 frankenstein kernel: wlo1: deauthenticating from 02:19:3b:0c:57:cb by local choice (Reason: 3=DEAUTH_L>
Sep 17 16:46:43 frankenstein kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Sep 17 16:46:43 frankenstein kernel: sd 1:0:0:0: [sda] Stopping disk
Sep 17 16:46:43 frankenstein kernel: e1000e: EEE TX LPI TIMER: 00000011
Sep 17 16:46:43 frankenstein kernel: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
Sep 17 16:46:43 frankenstein kernel: dpm_run_callback(): pci_pm_suspend+0x0/0x120 returns -16
Sep 17 16:46:43 frankenstein kernel: PM: Device 0000:00:14.0 failed to suspend async: error -16
Sep 17 16:46:43 frankenstein kernel: PM: Some devices failed to suspend, or early wake event detected
Sep 17 16:46:43 frankenstein kernel: ACPI: button: The lid device is not compliant to SW_LID.
Sep 17 16:46:43 frankenstein kernel: sd 1:0:0:0: [sda] Starting disk
Sep 17 16:46:43 frankenstein kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
Sep 17 16:46:43 frankenstein kernel: acpi LNXPOWER:04: Turning OFF
Sep 17 16:46:43 frankenstein kernel: OOM killer enabled.
Sep 17 16:46:43 frankenstein kernel: Restarting tasks ... done.
Sep 17 16:46:43 frankenstein kernel: ata3: SATA link down (SStatus 4 SControl 300)
Sep 17 16:46:43 frankenstein dhcpcd[1956884]: sending signal TERM to pid 394851
Sep 17 16:46:43 frankenstein dhcpcd[1956884]: waiting for pid 394851 to exit
Sep 17 16:46:43 frankenstein dhcpcd[394851]: received SIGTERM, stopping
Sep 17 16:46:43 frankenstein dhcpcd[394851]: wlo1: removing interface
Sep 17 16:46:43 frankenstein dhcpcd[394851]: dhcpcd exited

seth · 2019-09-17 22:00:04

Sep 17 16:46:43 frankenstein kernel: PM: Device 0000:00:14.0 failed to suspend async: error -16

And what is Device 0000:00:14.0 ?

lspci

seth wrote:

Check the journal right and after before the first dock and undock actions for what happens at this point.

The idea was not to investigate on the failure but what un/docking does that might alter the system in a way to break S3.

fANZYo · 2019-09-18 07:36:14

I'll check the un/docking differences.

In the meantime, device 00:14.0 seem to be

00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)

Which I believe is the USB port to which the screen USB hub is connected which allows me to connect my keyboard and mouse to the screen rather than the laptop so that i don't have to unplug them everytime I leave the office

PS: Undocking seem to produce a few errors:

Sep 18 08:32:10 frankenstein ifplugd[413]: Program executed successfully.
Sep 18 08:32:22 frankenstein systemd-timesyncd[405]: Synchronized to time server for the first time 87.242.168.84:123 >
Sep 18 08:36:48 frankenstein systemd-udevd[379928]: 2-3.1: Failed to process device, ignoring: No such file or directo>
Sep 18 08:36:48 frankenstein systemd-udevd[379928]: 2-3: Failed to process device, ignoring: No such file or directory
Sep 18 08:36:48 frankenstein kernel: usb 1-2: USB disconnect, device number 5
Sep 18 08:36:48 frankenstein kernel: usb 1-2.1: USB disconnect, device number 6
Sep 18 08:36:48 frankenstein kernel: usb 1-2.1.1: USB disconnect, device number 8
Sep 18 08:36:48 frankenstein kernel: usb 2-3: USB disconnect, device number 4
Sep 18 08:36:48 frankenstein kernel: usb 2-3.1: USB disconnect, device number 5
Sep 18 08:36:48 frankenstein systemd-udevd[379928]: 1-2.1.1: Failed to process device, ignoring: No such file or direc>
Sep 18 08:36:48 frankenstein kernel: usb 1-2.1.4: USB disconnect, device number 9
Sep 18 08:36:49 frankenstein systemd-udevd[379928]: 1-2.1.4: Failed to process device, ignoring: No such file or direc>
Sep 18 08:36:49 frankenstein systemd-udevd[379987]: 1-2.1.5: Failed to process device, ignoring: No such file or direc>
Sep 18 08:36:49 frankenstein kernel: usb 1-2.1.5: USB disconnect, device number 10
Sep 18 08:36:49 frankenstein kernel: usb 1-2.5: USB disconnect, device number 7
Sep 18 08:36:49 frankenstein systemd-udevd[379928]: 1-2.5: Failed to process device, ignoring: No such file or directo>
Sep 18 08:36:49 frankenstein systemd-udevd[379987]: 1-2.1: Failed to process device, ignoring: No such file or directo>
Sep 18 08:36:49 frankenstein systemd-udevd[379928]: 1-2: Failed to process device, ignoring: No such file or directory

Last edited by fANZYo (2019-09-18 14:34:36)

Arch Linux

#1 2019-09-13 08:28:06

Screen off after undocking

#2 2019-09-13 08:35:07

Re: Screen off after undocking

#3 2019-09-13 08:41:05

Re: Screen off after undocking

#4 2019-09-13 08:45:28

Re: Screen off after undocking

#5 2019-09-13 09:18:40

Re: Screen off after undocking

#6 2019-09-13 13:38:25

Re: Screen off after undocking

#7 2019-09-13 14:26:28

Re: Screen off after undocking

#8 2019-09-13 14:41:43

Re: Screen off after undocking

#9 2019-09-13 14:48:44

Re: Screen off after undocking

#10 2019-09-13 14:59:37

Re: Screen off after undocking

#11 2019-09-17 17:17:20

Re: Screen off after undocking

#12 2019-09-17 22:00:04

Re: Screen off after undocking

#13 2019-09-18 07:36:14

Re: Screen off after undocking

Board footer