Created attachment 137520 [details] Kernel Dmesg Logs for single display LFP boot. The system configuration is as follows Laptop - Hp pro-book 440 g3 SKU - SKL GT2 OS - Failed in same way for Elementary OS, Ubuntu 17.04 Native Resolution - 1366x768 System boots without flickers if we put nomodset, but not otherwise. Already tried almost latest drm-intel-next. Dmesg attached(for Ubuntu single display boot). Some experiments done which do not have any impact - disable rc6, FBC, DC states Connecting an HDMI in dual display config, has HDMI working but thats on 10x7 config and not in its native 14x9. Local eDP still continues to flicker like crazy. Don't see any under run error logs. Any patches to try just let me know and I can get the testing done. Right now short on time and resources to debug myself and any help/pointers will be very much appreciated. Thanks.
Jani, can you help ?
Hi Shobhit, to double check, you also see this problem with single display setup? i.e. this is not specific to dual display. Please try a new kernel and/or i915.edp_vswing=1 or i915.edp_vswing=2 settings. Could be the DDI buffer translation settings, all I can think of now (since you already tried without fbc, psr, etc, and there are no underrun errors).
Hi Jani, Thanks for helping out on this. This problem happens in single display only. I just connected dual display for HDMI test and that worked but not at native resolution. I will get your suggestions tested and update the results here. Regards Shobhit
So the tests with edp_vswing=1 or 2 both failed with similar flickering. Got it tested on drm-intel-next of two weeks ago. Do you think testing on latest will make a difference ?
(In reply to Shobhit Kumar from comment #4) > So the tests with edp_vswing=1 or 2 both failed with similar flickering. Got > it tested on drm-intel-next of two weeks ago. > > Do you think testing on latest will make a difference ? I don't think so. But do try without the parameter on that same kernel.
Without the parameters on same kernel anyways has the issue.
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 is issue still exists.
(In reply to Jani Saarinen from comment #8) > Closing, please re-open is issue still exists. Okay, no issues. will test on latest drm-tip and if persists will open again
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.