Bug 111965 - [i915]GDM Login screen doesn't show up on kernel 5.3 or later
Summary: [i915]GDM Login screen doesn't show up on kernel 5.3 or later
Status: NEW
Alias: None
Product: Spam
Classification: Unclassified
Component: Two (show other bugs)
Version: unspecified
Hardware: Other All
: not set not set
Assignee: Spam assignee
QA Contact:
Depends on:
Reported: 2019-10-10 06:59 UTC by Masami Ichikawa
Modified: 2019-10-10 06:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Note You need to log in before you can comment on or make changes to this bug.
Description Masami Ichikawa 2019-10-10 06:59:53 UTC
1. problem

Boot with kernel 5.3 or later, GDM login screen doesn't show up.
Following log is displayed in console.

Starting Show Plymouth Boot Screen...

When I remove rhgb and quiet from kernel command line, it shows gray background screen and blinking.

Kernel 5.2.18 doesn't have such issue.
I checked 5.2.18(fedora kernel) and 5.2.18(stable release) both works fine.

I've tested drm-tip tree(HEAD is ec6a1544198d81f34a367bfb18173e402bbee0fa). The drm-tip tree kernel has same issue.

2. Steps to reproduce the issue. 

Boot with kernel 5.3 or later

3. How often does the steps listed above trigger the issue?


4. The following information about your system:

system architecture: x86_64
kernel versions: 5.4-rc2(mainline), 5.4-rc2(drm-tip), 5.3.2(fedora kernel), 5.3.2(stable release)
Linux distribution: Fedora 30
Display connector: HDMI and DIV
/sys/class/drm/card0/error: I'll attach
dmesg: I'll attach
xrandr output: I'll attatch (taks this output on kernel 5.2.18)
VBIOS dump: I'll attach

5. bisect

If I did bisect correctly, "drm/i915/bios: make child device order the priority order(36a0f92020dc8794d3aa69b7fb4c5d2bf99b0099)" is first bad commit. previous commit "drm/i915: Enable intel_color_get_config()(3633e5116dfb01f98de4c88daf2c673c52290755)" works fines.

I took dmesg, /sys/class/drm/card0/error, VBIOS dump on drm-tip kernel.

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.