http://bugzilla.novell.com/show_bug.cgi?id=997503 http://bugzilla.novell.com/show_bug.cgi?id=997503#c1 --- Comment #1 from Rich Coe --- Created attachment 691040 --> http://bugzilla.novell.com/attachment.cgi?id=691040&action=edit hwinfo -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=997503 http://bugzilla.novell.com/show_bug.cgi?id=997503#c3 --- Comment #3 from Rich Coe --- Created attachment 691042 --> http://bugzilla.novell.com/attachment.cgi?id=691042&action=edit lspci -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=997503 http://bugzilla.novell.com/show_bug.cgi?id=997503#c5 --- Comment #5 from Rich Coe --- Created attachment 691044 --> http://bugzilla.novell.com/attachment.cgi?id=691044&action=edit xrandr query -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=997503 http://bugzilla.novell.com/show_bug.cgi?id=997503#c7 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstaudt@suse.com, | |tiwai@suse.com --- Comment #7 from Takashi Iwai --- (In reply to Rich Coe from comment #0)

On Saturday I updated from Tumbleweed to the latest Tumbleweed. Among a few things, the kernel upgraded from 4.7.1 to 4.7.2.

Do you mean it being a kernel regression, or did it happen before?

After using the laptop all weekend, I suspended the laptop, moved to the dock, resumed, and used two external monitors with the lid shut. In the afternoon, I suspended, undocked, and resumed in another location. I had no laptop display. If I suspended, and resumed again, the laptop briefly displays the lock screen and then goes blank. I could plug in an external HDMI monitor, and could see my desktop.

I suspended, and moved back to the dock, resumed, and the external displays worked. If I suspended, undocked, and resumed, no display on the laptop.

Could you try remote login at this state, and check xrandr output? (Run "xhost +" beforehand to allow access to the display, and run "export DISPLAY=:0" before running xrandr.) Is the external display still recognized as connected? And what if you run "xrandr --auto" there? Last but not least, boot with drm.debug=0x0e option, try the procedure to reproduce the bug, and attach the kernel messages. It'll show more information. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=997503 http://bugzilla.novell.com/show_bug.cgi?id=997503#c8 --- Comment #8 from Rich Coe --- kernel 4.7.2-1.3 updated last night. I was able to dock, resume, suspend, undock, resume, and have the laptop display. I'll keep testing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=997503 http://bugzilla.novell.com/show_bug.cgi?id=997503#c11 --- Comment #11 from Rich Coe --- I have reproduced the problem without kde, I used lxqt. After suspend/undock/resume, the LVDS is blank. I can switch to fb1 and login, but I can't make the display show up on fb7. The removing power cord and attaching it trick doesn't work. I started another xserver, it ran as :1 on fb1 and that didn't make a difference, but I didn't think it would. If I re-dock, the displays show up again on DP-1 and DP-2. I tried xrandr --output LVDS-1 --primary --auto and other xrandr commands, but it didn't change anything. I may have not done it correctly though. I will switch to lxqt again and try another xrandr command again. -- You are receiving this mail because: You are on the CC list for the bug.