Bug 110415 - drivers/gpu/drm/i915/intel_display.c:13761 skl_max_scale+0x9a/0xb0 [i915]
Summary: drivers/gpu/drm/i915/intel_display.c:13761 skl_max_scale+0x9a/0xb0 [i915]
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-12 21:02 UTC by Dimitar Atanasov
Modified: 2019-04-16 09:48 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features:

Attachments
dmesg (115.55 KB, text/plain)
2019-04-12 21:02 UTC, Dimitar Atanasov 		no flags Details
View All

Description Dimitar Atanasov 2019-04-12 21:02:44 UTC 
Created attachment 143955 [details]
dmesg

Kabylake  8706G, if you disable fastboot, there is no problem. Kernel 5.x
Comment 1 Lakshmi 2019-04-15 16:12:17 UTC 
Reporter, Can you please elaborate what is the issue? 
What is the impact of the issue and how often you see the issue?
Also, can you please attach the dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M?

All the above details are needed to investigate this issue.
Comment 2 Dimitar Atanasov 2019-04-15 16:41:00 UTC 
It can be observed every boot with fastboot enable. Effects is double mouse cursor and then black screen. If then suspend and restore, graphics are working again.
Comment 3 Dimitar Atanasov 2019-04-15 16:51:42 UTC 
Well it will no longer appear in 5.1 rc 5
Comment 4 Lakshmi 2019-04-15 19:40:21 UTC 
(In reply to Dimitar Atanasov from comment #3)
> Well it will no longer appear in 5.1 rc 5

Do you mean the issue is fixed in 5.1 RC5?
Comment 5 Dimitar Atanasov 2019-04-15 19:42:58 UTC 
Yes I have installed it just before your message
Comment 6 Lakshmi 2019-04-16 09:48:38 UTC 
Thanks for the feedback. Closing this bug.

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.