Created attachment 143690 [details] The complete output of dmesg Hello! Let me state right now that this is my first bug report and I am a little bit lost about what criteria I have to fulfill and whether I am reporting for the correct component. My system: I am using Arch Linux with the 5.0.1 Linux kernel. I have a Thinkpad P1 laptop with an Intel 8750H and an NVidia Quadro P1000. What happens: Before I turn on my laptop, I connected my external display via HDMI. Then I turn on my laptop and reach the bare tty (I am not using any Login Manager). While the tty is displayed, a lot of kernel messages are printed to the standard output about nouveau having some problems. As soon as I try to login (which starts my Window Manager, Sway), the system freezes and I have to hard reset my Laptop. Workaround: When I disconnect the HDMI cable before booting and connect it AFTER I logged into my system, then my external display works correctly. I dumped my whole dmesg output into the attached 'system.log' file, and I also retrieved the VBIOS information for my external display, I think. Let me know, if I can provide any further information and again, excuse any noob mistakes.
Created attachment 143691 [details] The VBIOS information of the external display?
Oh, I forgot to mention that in previous Kernel versions (at least up to 4.8), I had the same problem, but it was worse, since when reaching the tty with the HDMI connected, the system immediately froze. This was different, because with 5.0.1 I can at least able to reach tty and fetch the dmesg output, as the system only freezes if I actually try to login on tty
Hello, I have to add now that at some point this was fixed. Not a problem anymore
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.