Bug 100250 - [KBL] Flicker and sometimes no image with Dell XPS 13 9360
Summary: [KBL] Flicker and sometimes no image with Dell XPS 13 9360
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high major
Assignee: Paul Menzel
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-17 12:53 UTC by Paul Menzel
Modified: 2017-06-30 21:00 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: firmware/huc


Attachments
Linux messages (output of `journalctl -k -o short-precice`) (327.50 KB, text/plain)
2017-03-17 12:53 UTC, Paul Menzel
no flags Details
Linux configuration (185.83 KB, text/x-mpsub)
2017-03-17 12:55 UTC, Paul Menzel
no flags Details

Description Paul Menzel 2017-03-17 12:53:29 UTC
Created attachment 130286 [details]
Linux messages (output of `journalctl -k -o short-precice`)

Since building Linux 4.10 release candidates up to Linux 4.11-rc2+, the screen of the Kaby Lake device Dell XPS 13 9360 heavily flickers during start-up on the console, and sometimes the screen isn’t turned on at all after the driver i915 is loaded. The backlight seems to be on though. Often, a workaround is to suspend the system by pressing the power button, and resuming it. Then the display is turned on.

Please find a log attached.
Comment 1 Paul Menzel 2017-03-17 12:55:51 UTC
Created attachment 130287 [details]
Linux configuration
Comment 2 Paul Menzel 2017-03-17 12:59:22 UTC
To clarify, the flicker consists of three or four flashes, which lasts a good second or so.
Comment 3 Paul Menzel 2017-03-17 13:01:46 UTC
(In reply to Paul Menzel from comment #0)

[…]

> Since building Linux 4.10 release candidates up to Linux 4.11-rc2+,

I am also able to reproduce this with Linux 4.9.x shipped by Debian 9 (Stretch/testing).

[…]
Comment 4 Jari Tahvanainen 2017-04-03 11:03:31 UTC
Hello Paul, There seem to be firmware related problem ...
Mar 17 13:23:11.783611 xps13 kernel: i915 0000:00:02.0: Direct firmware load for i915/kbl_huc_ver02_00_1810.bin failed with error -2
Mar 17 13:23:11.783727 xps13 kernel: [drm] Failed to fetch valid uC firmware from i915/kbl_huc_ver02_00_1810.bin (error -2)
Do you have the ver02_00 firmware installed in your system? 
If not then please update firmware from https://01.org/linuxgraphics/downloads/kabylake-huc-2.0 and see if problem still persist.
Comment 5 Paul Menzel 2017-04-03 12:14:30 UTC
(In reply to Jari Tahvanainen from comment #4)
> Hello Paul, There seem to be firmware related problem ...
> Mar 17 13:23:11.783611 xps13 kernel: i915 0000:00:02.0: Direct firmware load
> for i915/kbl_huc_ver02_00_1810.bin failed with error -2
> Mar 17 13:23:11.783727 xps13 kernel: [drm] Failed to fetch valid uC firmware
> from i915/kbl_huc_ver02_00_1810.bin (error -2)
>
> Do you have the ver02_00 firmware installed in your system? 
> If not then please update firmware from
> https://01.org/linuxgraphics/downloads/kabylake-huc-2.0 and see if problem
> still persist.

The description of the firmware seems totally unrelated.

> HuC is a dedicated firmware for usage in media HEVC (High Efficiency Video
> Coding) operations. Userspace can use the firmware capabilities by adding HuC
> specific commands to batch buffers.

How can this be related?
Comment 6 Jari Tahvanainen 2017-04-10 08:50:20 UTC
Sorry Paul, about the delay for getting back to you. HuC loading was the only thing that was jumping out from dmesg. 
Does problem still persist with latest drm-tip? If yes, please attach dmesg and Xorg.0.log from the system and change the status to REOPENED.
Comment 7 Jari Tahvanainen 2017-05-23 12:32:57 UTC
Paul - please help us here and give update: Still valid with the latest kernels (preferable from drm-tip)? If yes, please attach dmesg and Xorg.0.log from the system and change the status to REOPENED. If not reproducible then please mark this as resolved.
Comment 8 Elizabeth 2017-06-30 21:00:17 UTC
(In reply to Jari Tahvanainen from comment #7)
> Paul - please help us here and give update: Still valid with the latest
> kernels (preferable from drm-tip)? If yes, please attach dmesg and
> Xorg.0.log from the system and change the status to REOPENED. If not
> reproducible then please mark this as resolved.

Hello,
Still no answer on this case, so I'm closing the bug. If the problem persist with the latest kernel version, please open a new bug and share the information. Thanks.


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.