Bug 103148 - [BYT] DV8P blackscreen after i915 load
Summary: [BYT] DV8P blackscreen after i915 load
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-08 15:06 UTC by Jan-Michael Brummer
Modified: 2018-04-25 08:14 UTC (History)
1 user (show)

See Also:
i915 platform: BYT
i915 features: display/DSI


Attachments
Normal boot log with debug information (296.82 KB, text/x-log)
2017-10-08 15:06 UTC, Jan-Michael Brummer
no flags Details
Fastboot boot log with debug information (438.01 KB, text/x-log)
2017-10-08 15:06 UTC, Jan-Michael Brummer
no flags Details
Normal boot log with debug information (drm-tip) (313.69 KB, text/x-log)
2017-10-13 10:13 UTC, Jan-Michael Brummer
no flags Details
Fastboot boot log with debug information (drm-tip) (317.67 KB, text/x-log)
2017-10-13 10:14 UTC, Jan-Michael Brummer
no flags Details

Description Jan-Michael Brummer 2017-10-08 15:06:11 UTC
Created attachment 134748 [details]
Normal boot log with debug information

Device: Dell Venue 8 Pro (5830)
OS: Fedora 27
Kernel: 4.13.3-300.fc27.x86_64

Descripton:
Blackscreen with working backlight kicks in during kernel startup (after i915 take over).

A startup with i915.fastboot=1 works, but drops image as soon as screen is rotated.

I'm attaching two log files, one with a normal startup and one with fastboot enabled. Both have drm.debug=0xe enabled.
Comment 1 Jan-Michael Brummer 2017-10-08 15:06:47 UTC
Created attachment 134749 [details]
Fastboot boot log with debug information
Comment 2 Elizabeth 2017-10-09 22:12:14 UTC
From dmesg:
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_hdisplay (expected 0, found 800)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_htotal (expected 0, found 914)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_hblank_start (expected 0, found 800)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_hblank_end (expected 0, found 914)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_hsync_start (expected 0, found 840)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_hsync_end (expected 0, found 844)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_vdisplay (expected 0, found 1280)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_vtotal (expected 0, found 1474)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_vblank_start (expected 0, found 1280)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_vblank_end (expected 0, found 1474)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_vsync_start (expected 0, found 1290)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_vsync_end (expected 0, found 1294)
[drm:pipe_config_err [i915]] mismatch in base.adjusted_mode.crtc_clock (expected 0, found 80840)

Is it possible for you to try with drm-tip branch? Thanks.
Comment 3 Elizabeth 2017-10-09 22:13:16 UTC
(In reply to Elizabeth from comment #2)
> From dmesg...
Not sure if that is relevant.
Comment 4 Elizabeth 2017-10-09 22:15:46 UTC
Raising priority due to 'blackscreen issue'.
Comment 5 Jan-Michael Brummer 2017-10-13 10:13:34 UTC
Created attachment 134828 [details]
Normal boot log with debug information (drm-tip)
Comment 6 Jan-Michael Brummer 2017-10-13 10:14:09 UTC
Created attachment 134829 [details]
Fastboot boot log with debug information (drm-tip)
Comment 7 Jan-Michael Brummer 2017-10-13 10:14:48 UTC
Added traces with drm-tip branch.
Comment 8 Jani Nikula 2017-10-23 13:52:16 UTC
Did you try the kernel config options from bug 96571?
Comment 9 Jan-Michael Brummer 2017-10-29 11:31:19 UTC
Yes sure, it is the same.
Comment 10 Jani Saarinen 2018-03-29 07:10:41 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 11 Jani Saarinen 2018-04-25 08:14:30 UTC
Closing, please re-open is issue still exists.


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.