search

pop-os / pop

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

Login screen not showing when both monitors are plugged in #1560

Open dewijones92 opened 3 years ago

dewijones92 commented 3 years ago

Distribution (run cat /etc/os-release): 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 GPU=5500XT

Issue/Bug Description: mon1 is display port. mon2 is dvi When I boot up with both monitors plugged in I get this screen instead of the log-in screen https://photos.app.goo.gl/bWMdPJKNhxHdHCX37

When I boot up with either monitor instead of both plugged in then the it successfully shows the login screen. When I boot up with mon1, log in, then plug in mon2 it successfully shows a second desktop

This bug only occurs if I boot up with both monitors plugged in at boot time.

Steps to reproduce (if you know): Plug both monitors. Boot up. This screen shows instead of the login screen https://photos.app.goo.gl/bWMdPJKNhxHdHCX37

Expected behavior: Should show login screen

Other Notes: kernel log https://pastebin.pl/view/af35e936 systemd log https://pastebin.pl/view/71098a10

Many thanks 😊

bflanagin commented 3 years ago

@dewijones92: This might be one of those hardware specific issues that make things hard to track down and test. However, if you could include your Xorg logs that might shed a little more light on the problem.

dewijones92 commented 3 years ago

@bflanagin looks like there are no logs generated when this error occurs.
Interestingly I think it occurs only when I use EXWM on the previous boot. hmmmmm

I noticed a couple of weird messages in that kernel log

Feb 28 18:00:32 pop-os kernel: [   11.059155] VBoxNetFlt: Successfully started.
Feb 28 18:00:32 pop-os kernel: [   11.062383] VBoxNetAdp: Successfully started.
Feb 28 18:00:40 pop-os kernel: [   19.091334] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=270, emitted seq=272
Feb 28 18:00:40 pop-os kernel: [   19.091385] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Feb 28 18:00:40 pop-os kernel: [   19.091390] amdgpu 0000:0b:00.0: amdgpu: GPU reset begin!
Feb 28 18:00:43 pop-os kernel: [   21.456925] amdgpu: failed send message: DisallowGfxOff (42)  param: 0x00000000 response 0xffffffc2
Feb 28 18:00:43 pop-os kernel: [   21.891274] [drm] free PSP TMR buffer
Feb 28 18:00:45 pop-os kernel: [   23.592152] amdgpu 0000:0b:00.0: amdgpu: GPU reset succeeded, trying to resume
Feb 28 18:00:45 pop-os kernel: [   23.592296] [drm] PCIE GART of 512M enabled (table at 0x0000008000E10000).
Feb 28 18:00:45 pop-os kernel: [   23.592325] [drm] VRAM is lost due to GPU reset!
Feb 28 18:00:45 pop-os kernel: [   23.592637] [drm] PSP is resuming...
bflanagin commented 3 years ago

I'll need to pass this along to someone that has a amdgpu. All I have is Intel and NVIDIA machines at the moment. If you can verify it has something to do with EXWM that might eliminate the faulty hardware angle. Of course if its the window manager and you can't replicate the issue in gnome / pop shell you'll need to put in a issue with them as we have little to do with anything outside of our products.