This is on a Sony Vaio Pro 13 (Haswell) running Fedora 26. After upgrading from kernel-4.11.11-300.fc26.x86_64 to 4.12.5-300.fc26.x86_64, I no longer get any video output (in particular: the LUKS password prompt) on the external monitor connected to the HDMI port. It's only displayed on the internal LCD. The external monitor shows the expected video output only after Xorg starts.
Created attachment 133636 [details] dmesg with drm.debug=0x1e log_buf_len=1M
Hello, changing priority since it seems to be a regression w/ workaround. Thanks. Adding tag into "Whiteboard" field - ReadyForDev *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included
Same issue with Fedora kernel 4.12.8-300.fc26.x86_64. Please note that I'm using the modesetting driver in Xorg.
Created attachment 133729 [details] kernel-4.12.8.fc26.x86_64 dmesg with drm.debug=0x1e log_buf_len=1M New dmesg attached.
Does it happen with drm-tip? Can you do a bisect and provide the blame commit?
(In reply to Radhakrishna Sripada from comment #5) > Does it happen with drm-tip? I don't know. I assume you mean https://cgit.freedesktop.org/drm-tip . I'll try to build the kernel from that repo and report back. > Can you do a bisect and provide the blame commit? I can try but it'll take quite some time as this is my main machine.
One additional data point: if I remove 'rhgb' and 'quiet' from the kernel command line, I can see kernel messages scrolling up the screen after booting the kernel, but very soon, the screen goes blank. I assume this happens around the same time as the LUKS prompt appears, because if I type the password blindly, the system continues to start and I get the X login screen soon afterwards. The external monitor connected via HDMI remains in sleep mode until Xorg starts.
(In reply to Dominik 'Rathann' Mierzejewski from comment #6) > (In reply to Radhakrishna Sripada from comment #5) > > Does it happen with drm-tip? > > I don't know. I assume you mean https://cgit.freedesktop.org/drm-tip . I'll > try to build the kernel from that repo and report back. Ok, I tried the drm-tip kernel (commit 69c8e7a57ac940f8b392b23a23dcdd61e727efd3) and I cannot reproduce the issue. > > Can you do a bisect and provide the blame commit? Considering the above, is this necessary?
(In reply to Dominik 'Rathann' Mierzejewski from comment #8) > (In reply to Dominik 'Rathann' Mierzejewski from comment #6) > > (In reply to Radhakrishna Sripada from comment #5) > > > Does it happen with drm-tip? > > > > I don't know. I assume you mean https://cgit.freedesktop.org/drm-tip . I'll > > try to build the kernel from that repo and report back. > > Ok, I tried the drm-tip kernel (commit > 69c8e7a57ac940f8b392b23a23dcdd61e727efd3) and I cannot reproduce the issue. Great. > > > Can you do a bisect and provide the blame commit? > > Considering the above, is this necessary? It's not necessary... but either that, or a reverse bisect from v4.12 to drm-tip, would be helpful. Otherwise we'll just close the bug as fixed upstream, but we'll have no idea if we should backport something to stable kernels. Because based on this bug report, we have no clue what this is about.
I fully understand and I may do a bisect if time permits, but since I know this is fixed in 4.13, it's much lower priority now. It'd be great if someone else could reproduce this, too.
Sorry, it looks like it might be Fedora-specific. Fedora's 4.13.4-200.fc26.x86_64 exhibits the same problem.
I was told that drm-tip got merged into 4.14 and indeed, with 4.14.0-0.rc4.git0.1.fc28.x86_64 installed I no longer see the problem. I don't have time to do a git-bisect, sorry.
According to Bug Scrubbing Meeting on ww41, this bug got a decreased severity. more info see notes on Bug Scrubbing Minutes.
(In reply to Dominik 'Rathann' Mierzejewski from comment #12) > I was told that drm-tip got merged into 4.14 and indeed, with > 4.14.0-0.rc4.git0.1.fc28.x86_64 installed I no longer see the problem. I > don't have time to do a git-bisect, sorry. Decreasing priority/severity due to this issue being fixed on 4.14.0-0.rc4. This case will be closed soon if bisecting is not possible. Thank you.
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open if still occurs.
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.