search

pop-os / pop

A project for managing all Pop!_OS sources
https://system76.com/pop
2.48k stars 87 forks source link

Unplugging external display with laptop shut results in laptop's screen staying turned off when opened #358

Open hankjacobs opened 6 years ago

hankjacobs commented 6 years ago

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

Issue/Bug Description:

When I have an external display connected (using Thunderbolt 3 / usb-c port) and the laptop display shut, unplugging the external display while the laptop is still shut results in the laptop's display remaining off when laptop is opened. Screen stays off no matter what buttons are pressed or if the laptop is closed and opened again. A hard shutdown (via holding the power button) resolves the issue. Laptop is a Galago Pro.

Any help would be greatly appreciated. Thanks!

Steps to reproduce (if you know):

Expected behavior:

Other Notes:

Opening the laptop, waiting for the laptop display to turn on and then unplugging the external display works as expected.

hankjacobs commented 6 years ago

After doing some digging, I noticed the following repeated periodically in syslog when I'm encountering the issue:

i915 0000:00:02.0: Resetting rcs0 after gpu hang
ahoneybun commented 6 years ago

I did test this in our lab unit and I did recreate it here. It seems to happen if you disconnect the USB C port fast enough and open the lid pretty fast from what I can tell. You can bring the display back by reconnecting the USB C cable to the port. It does not seem to come back if I kill Xorg and try to bring it back and instead creates a login loop.

wenzeslaus commented 3 years ago

I have the same issue with 20.04 and Lemur Pro. Same "display won't turn on after disconnecting USB-C while sleeping" behavior as OP. I don't think I'm opening the lid quickly as @ahoneybun, but that's hard to tell. Debugging suggestions welcome.

patrykkubiela commented 3 years ago

Hey! Exactly the same issue with my ThinkPad Carbon X1 gen 5 and LG monitor connected with USB-C. Unpluging the monitor and open the lid doesn't turn display ON.

NAME="Pop!_OS" VERSION="20.10" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 20.10" VERSION_ID="20.10" HOME_URL="https://pop.system76.com" SUPPORT_URL="https://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy LOGO=distributor-logo-pop-os

alexandre-janniaux commented 2 years ago

Hi, same here on lemp10 with up-to-date Pop!_OS and a thunderbolt displayport external screen, replugging also fixes the black screen.

Nothing worrying in the journal regarding eDP-1:

╰─$ grep eDP < logs_system76_journal | cut -d: -f5 | sort -u
02
07
 EDID for output eDP-1
 Output eDP-1 connected
 Output eDP-1 has no monitor section
 Output eDP-1 using initial mode 1920x1080 +0+0
 Printing probed modes for output eDP-1

Some gnome-shell errors:

nov. 30 09:19:42 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 06:12:29 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 05:21:41 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 05:10:59 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 04:51:49 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 04:28:55 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 03:11:15 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 30 01:35:10 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
nov. 29 23:10:30 pop-os gnome-shell[3047]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

Some DRM / intel errors which seems to happen when the issue also arise: 

nov. 29 22:13:34 pop-os kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

But I don't find a lot of incriminating logs.

knorquist commented 2 years ago

I suspect this is something upstream, because I get the same issue on vanilla Ubuntu 22.04 on my HP Zbook 14u G5, and this is with a clean reinstall and the latest displaylink drivers.