Bug 108826 - [GLK DSI] Black screen after grub - Ubuntu 18.04 - kernel latest tip 21.11.2018
Summary: [GLK DSI] Black screen after grub - Ubuntu 18.04 - kernel latest tip 21.11.2018
Status: NEEDINFO
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-21 23:39 UTC by Miroslaw
Modified: 2018-11-30 13:40 UTC (History)
6 users (show)

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


Attachments
kernel log (285.64 KB, text/plain)
2018-11-21 23:39 UTC, Miroslaw
no flags Details
drm.debug=0x1e (335.55 KB, text/plain)
2018-11-22 23:12 UTC, Miroslaw
no flags Details
igt-gpu-tools - dump i915.modeset=0_dump.txt (17.00 KB, text/plain)
2018-11-28 00:40 UTC, Miroslaw
no flags Details
igt-gpu-tools - dump fully_working_gpu_driver_black_screen_dump.txt (17.00 KB, text/plain)
2018-11-28 00:41 UTC, Miroslaw
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Miroslaw 2018-11-21 23:39:54 UTC
Created attachment 142557 [details]
kernel log

The screen after the grub is getting black ( backlight is still working ).  
System is booting normally - after that backlight screen is working .. and black all the time.
I can control brightness by shortcuts.
If connect HDMI cable then on the new via HDMI the screen works perfect but on the device screen is still black unfortunately .

I attached the kernel.



- edid from windows 10 

Monitor
  Model name............... WLY-10102FHD
  Windows description...... Generic PnP Monitor
  Manufacturer............. AUO
  Plug and Play ID......... AUO17D8
  Serial number............ n/a
  Manufacture date......... 2013, ISO week 11
  Filter driver............ None
  -------------------------
  EDID revision............ 1.4
  Input signal type........ Digital
  Color bit depth.......... 8 bits per primary color
  Color encoding formats... RGB 4:4:4, YCrCb 4:4:4
  Screen size.............. 140 x 220 mm (10,3 in)
  Power management......... Active off/sleep
  Extension blocs.......... None
  -------------------------
  DDC/CI................... n/a

Color characteristics
  Default color space...... sRGB
  Display gamma............ 3,55
  Red chromaticity......... Rx 0,625 - Ry 0,340
  Green chromaticity....... Gx 0,285 - Gy 0,605
  Blue chromaticity........ Bx 0,148 - By 0,063
  White point (default).... Wx 0,281 - Wy 0,309
  Additional descriptors... None



Thanks for any help.
Comment 1 Lakshmi 2018-11-22 07:28:54 UTC
Miroslaw, How often you see this issue? CAn you reproduce this issue?
Can you attach cat /sys/kernel/debug/dri/0/i915_edp_psr_status

Imre, any comments here?
Comment 2 Imre Deak 2018-11-22 07:43:17 UTC
Miroslaw, could you post a dmesg log booting with drm.debug=0x1e ?

I see that there's a suspend followed by a second kernel boot with the nomodeset kernel parameter. Is that some kexec thing? nomodeset will disable the i915 driver:

Nov 21 20:25:43 qq-ETP101WL64 kernel: [  117.478108] [drm:gen9_set_dc_state [i915]] Setting DC state from 01 to 00
Nov 21 20:25:43 qq-ETP101WL64 kernel: [  117.743131] PM: suspend entry (deep)
Nov 21 20:26:59 qq-ETP101WL64 kernel: [    0.000000] microcode: microcode updated early to revision 0x28, date = 2018-05-22
Nov 21 20:26:59 qq-ETP101WL64 kernel: [    0.000000] Linux version 4.20.0-994-generic (kernel@tangerine) (gcc version 8.2.0 (Ubuntu 8.2.0-9ubuntu1)) #201811202101 SMP Wed Nov 21 02:04:29 UTC 2018
Nov 21 20:26:59 qq-ETP101WL64 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.20.0-994-generic root=UUID=c52e7968-edfb-425b-996c-93790fe96a5f ro quiet splash nomodeset vt.handoff=1
Comment 3 Miroslaw 2018-11-22 10:15:06 UTC
I think you see second boot because I had to boot device with the nomodeset parameter second time ( then screen is working but this is software mode )   to copy data log from /var/log ...because without this parameter the screen is black ( only backlight works ) .

I forgot to remove second log data from kernel.log file .
Comment 4 Jani Nikula 2018-11-22 10:53:29 UTC
(In reply to Lakshmi from comment #1)
> Can you attach cat /sys/kernel/debug/dri/0/i915_edp_psr_status

It's a MIPI DSI panel, that file is not relevant.
Comment 5 Jani Saarinen 2018-11-22 10:59:11 UTC
I see our GLK DSI on CI generally happy on BAT:
https://intel-gfx-ci.01.org/tree/drm-tip/fi-glk-dsi.html
Comment 6 Miroslaw 2018-11-22 11:31:22 UTC
This is MIPI DSI panel - yes 
Device is a tablet ..so works on battery - yes
Comment 7 Miroslaw 2018-11-22 15:52:08 UTC
Do you need more details ?
Comment 8 Imre Deak 2018-11-22 15:58:43 UTC
(In reply to Miroslaw from comment #7)
> Do you need more details ?

Could you provide the dmesg log booting with drm.debug=0x1e? Please capture the log right after booting, when the screen is blank.
Comment 9 Miroslaw 2018-11-22 23:12:36 UTC
Created attachment 142580 [details]
drm.debug=0x1e

log with param drm.debug=0x1e
Comment 10 Stanislav Lisovskiy 2018-11-23 07:15:36 UTC
Did that start to happen only with recent kernel? Can you please also attach kernel log with drm.debug with a working kernel?
Comment 11 Miroslaw 2018-11-23 09:58:42 UTC
There is no working kernel .
I tested from 4.15 up to 4.20-rc1 ... akways the same - black screen after grub ( backlight works ) .
Comment 12 Miroslaw 2018-11-23 20:23:23 UTC
Hi

Any ideas how to fix it ?
Comment 13 Jani Nikula 2018-11-26 07:21:49 UTC
One idea for debugging this:

1) boot *without* loading i915
2) get register dump using intel_reg (from the igt-gpu-tools [1])
3) modprobe i915 (presumably screen goes black at this point)
4) repeat the register dump

Alas I think intel_reg dump still falls short for MIPI DSI register dumps. Someone from our side should provide a register spec file to use with intel_reg to include all the relevant registers. (One of the reasons we're not dumping the DSI registers by default is that reading them hangs the machine if DSI isn't properly powered and clocks enabled.)

[1] https://cgit.freedesktop.org/drm/igt-gpu-tools/
Comment 14 Miroslaw 2018-11-27 01:35:52 UTC
Hi

I'm trying to compile igt-gpu-tools for debugging
but have problems with dependencies 

Dependency xmlrpc found: NO
Dependency xmlrpc_util found: NO
Dependency xmlrpc_client found: NO
Dependency xv found: NO
Program rst2man-3 found: NO

I can't find those dependencies ...
I'm trying to build it on Ubuntu 18.04 what system are you using for it ?

Thank for help
Comment 15 Jani Saarinen 2018-11-27 06:37:11 UTC
+ Petri and Arek to comment deps.
Comment 16 Jani Saarinen 2018-11-27 07:01:34 UTC
Miroslaw, have you read README.md. Does it help?
Comment 17 Miroslaw 2018-11-27 10:05:02 UTC
Reading readme was the first thing what I did .
I installed all dependencies from readme.md.

But still missing 

Dependency xmlrpc found: NO
Dependency xmlrpc_util found: NO
Dependency xmlrpc_client found: NO
Dependency xv found: NO
Program rst2man-3 found: NO

I tried installed those missing by myself but can't find it .

As I said - I'm using Ubuntu 18.04 ... maybe is not compatible. What system are you using for build this app ? .
Comment 18 Petri Latvala 2018-11-27 10:13:48 UTC
(In reply to Miroslaw from comment #14)
> Hi
> 
> I'm trying to compile igt-gpu-tools for debugging
> but have problems with dependencies 
> 
> Dependency xmlrpc found: NO
> Dependency xmlrpc_util found: NO
> Dependency xmlrpc_client found: NO
> Dependency xv found: NO
> Program rst2man-3 found: NO
> 
> I can't find those dependencies ...
> I'm trying to build it on Ubuntu 18.04 what system are you using for it ?
> 
> Thank for help


Those dependencies are for Chamelium support (xmlrpc), intel-gpu-overlay (xv) and man pages (rst2man-3).

xmlrpc in Debian and Ubuntu are old enough to not have pkg-config support. The NO you're seeing for them is not finding its pkg-config files. If those fail, the build system is using xmlrpc-config.

Overlay has two variants, with xv or with xlib.

rst2man-3 is a binary in Fedora for its python3 version. On Ubuntu, rst2man is used.

In a nutshell: All those missing dependencies are for particular variants, and even if you don't have the other variants, the disabled build artifacts are not related to the intel_reg tool.

The Debian packages that are used in gitlab CI should also work for Ubuntu, check out Dockerfile.debian.
Comment 19 Miroslaw 2018-11-28 00:40:23 UTC
Created attachment 142638 [details]
igt-gpu-tools - dump i915.modeset=0_dump.txt
Comment 20 Miroslaw 2018-11-28 00:41:06 UTC
Created attachment 142639 [details]
igt-gpu-tools - dump fully_working_gpu_driver_black_screen_dump.txt
Comment 21 Miroslaw 2018-11-28 00:48:24 UTC
I added 2 dumps from igt-gpu-tools

command : intel_reg dump 

Without loaded gpu driver and with working gpu driver.
Of course with working gpu driver I have black screen.

If you need more data please ask.
Thanks
Comment 22 Miroslaw 2018-11-29 21:15:55 UTC
So 
Any ideas ?  ;-)

Thanks
Comment 23 Jani Nikula 2018-11-30 11:54:15 UTC
Just to double check, are you booting in UEFI mode and not in legacy BIOS mode?
Comment 24 Miroslaw 2018-11-30 13:39:19 UTC
I'm sure on 100 % - booting from  UEFI
Comment 25 Miroslaw 2018-11-30 13:40:38 UTC
And no legacy BIOS mode.


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.