Bug 102312

Summary: [HSW] no output on HDMI until Xorg starts after upgrade to kernel 4.12.5
Product: DRI Reporter: Dominik 'Rathann' Mierzejewski <dominik>
Component: DRM/IntelAssignee: Radhakrishna Sripada <radhakrishna.sripada>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, ricardo.vega
Version: unspecifiedKeywords: bisect_pending
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard: ReadyForDev
i915 platform: HSW i915 features: display/HDMI
Attachments:
Description Flags
dmesg with drm.debug=0x1e log_buf_len=1M
none
kernel-4.12.8.fc26.x86_64 dmesg with drm.debug=0x1e log_buf_len=1M none

Description Dominik 'Rathann' Mierzejewski 2017-08-19 23:40:59 UTC
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.
Comment 1 Dominik 'Rathann' Mierzejewski 2017-08-20 00:08:48 UTC
Created attachment 133636 [details]
dmesg with drm.debug=0x1e log_buf_len=1M
Comment 2 Elizabeth 2017-08-21 22:09:39 UTC
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
Comment 3 Dominik 'Rathann' Mierzejewski 2017-08-23 15:01:31 UTC
Same issue with Fedora kernel 4.12.8-300.fc26.x86_64. Please note that I'm using the modesetting driver in Xorg.
Comment 4 Dominik 'Rathann' Mierzejewski 2017-08-23 22:24:49 UTC
Created attachment 133729 [details]
kernel-4.12.8.fc26.x86_64 dmesg with drm.debug=0x1e log_buf_len=1M

New dmesg attached.
Comment 5 Radhakrishna Sripada 2017-08-30 00:35:18 UTC
Does it happen with drm-tip? Can you do a bisect and provide the blame commit?
Comment 6 Dominik 'Rathann' Mierzejewski 2017-09-04 07:51:16 UTC
(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.
Comment 7 Dominik 'Rathann' Mierzejewski 2017-09-04 07:55:42 UTC
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.
Comment 8 Dominik 'Rathann' Mierzejewski 2017-09-04 14:22:55 UTC
(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?
Comment 9 Jani Nikula 2017-09-06 10:29:40 UTC
(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.
Comment 10 Dominik 'Rathann' Mierzejewski 2017-09-06 22:03:36 UTC
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.
Comment 11 Dominik 'Rathann' Mierzejewski 2017-10-06 11:56:07 UTC
Sorry, it looks like it might be Fedora-specific. Fedora's 4.13.4-200.fc26.x86_64 exhibits the same problem.
Comment 12 Dominik 'Rathann' Mierzejewski 2017-10-11 12:59:33 UTC
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.
Comment 13 vladimir.campos 2017-10-11 21:54:17 UTC
According to Bug Scrubbing Meeting on ww41, this bug got a decreased severity. more info see notes on Bug Scrubbing Minutes.
Comment 14 Elizabeth 2017-10-17 14:19:41 UTC
(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.
Comment 15 Jani Saarinen 2018-03-29 07:12:00 UTC
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.
Comment 16 Jani Saarinen 2018-04-20 14:21:18 UTC
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.