Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

jimmy00784 · 2019-06-23 22:10:42

I am running into a weird error and I can't find anything on the Internet or forums that has helped yet.
I have a fully functional installation on my Dell Inspiron with Intel video. Everything seemed to work fine until a few weeks back when I upgraded like I usually do.
At boot time, when the graphical.target loads, the screen goes black, as if unable to render. Keyboard "seems" to be functional. Hitting Caplocks toggles the indicator led, but repeatedly hitting Ctrl+Alt+Del doesn't seem to have any effect and I have to hard reset to reboot.
There are no errors in the system logs or the X logs.
The issue persists in kernel version 5.1.14
The issue doesn't happen in the LTS kernel version 4.19.53
At this time I am able to continue to use my laptop by having the LTS kernel installed and defaulting to load that using systemd-boot.
I've tried all troubleshooting steps for i915 driver as described in the Arch Wiki but nothing seems to fix it.

Now, here is something else that I noticed in my recent troubleshooting attempts that might help point me in the right direction, but I am too frustrated to make anything of it.

If I disable display manager and boot to terminal and manually start display manager, I get a functional desktop and everything works. But from that session, if I re-enable display manager, screen goes black as soon as systemd confirms the change.

What might this behavior mean?

I'd be happy to provide any console output or logs from both login sessions if anyone has any idea what else I can try to resolve this.

TIA

V1del · 2019-06-23 23:27:27

Does it start to work if you hit some other buttons rather than special function ones like caps lock and ctrl+alt+del ? FWIW symptoms sound like the rng issue, so if your cpu supports it (lscpu | grep rdrand gives you output) try appending

random.trust_cpu=on

on your kernel parameters otherwise start and enable haveged

Should that not help post a

sudo journalctl -b #During a reproducing boot, or -b-1 if you were forced to reboot

jimmy00784 · 2019-06-24 15:46:28

@V1del Random Number Generation based solutions didn't help.
Here is the paste bin link for the journalctl -b-1 and Xorg.0.log.old
I hope it helps.

https://pastebin.com/YYdwKi66

seth · 2019-06-24 20:18:30

Jun 24 10:33:50 inspiron kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in dp_m2_n2 (expected tu 64 gmch 15605/32768 link 13871/32768, found tu 1, gmch 0/0 link 0/0)
Jun 24 10:33:50 inspiron kernel: ------------[ cut here ]------------
Jun 24 10:33:50 inspiron kernel: pipe state doesn't match!
Jun 24 10:33:50 inspiron kernel: WARNING: CPU: 0 PID: 8 at drivers/gpu/drm/i915/intel_display.c:12437 intel_atomic_commit_tail+0xe4f/0xec0 [i915]
Jun 24 10:33:50 inspiron kernel: Modules linked in: i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm intel_gtt agpgart
Jun 24 10:33:50 inspiron kernel: CPU: 0 PID: 8 Comm: kworker/u16:0 Not tainted 5.1.14-arch1-1-ARCH #1
Jun 24 10:33:50 inspiron kernel: Hardware name: Dell Inc. Inspiron 7347/0F9PPM, BIOS A00 06/30/2014
Jun 24 10:33:50 inspiron kernel: Workqueue: events_unbound async_run_entry_fn
Jun 24 10:33:50 inspiron kernel: RIP: 0010:intel_atomic_commit_tail+0xe4f/0xec0 [i915]
Jun 24 10:33:50 inspiron kernel: Code: 4c 89 4c 24 10 e8 c1 45 01 00 48 8b 4c 24 18 4c 8b 4c 24 10 e9 63 fb ff ff e8 1c 29 48 c8 0f 0b e9 fa fd ff ff e8 10 29 48 c8 <0f> 0b e9 7d f9 ff ff e8 04 29 48 c8 0f 0b e9 e1 f8 ff ff e8 f8 28
Jun 24 10:33:50 inspiron kernel: RSP: 0018:ffffb4f1c0ccfa60 EFLAGS: 00010286
Jun 24 10:33:50 inspiron kernel: RAX: 0000000000000000 RBX: ffff9d4b12cda000 RCX: 0000000000000000
Jun 24 10:33:50 inspiron kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: 00000000ffffffff
Jun 24 10:33:50 inspiron kernel: RBP: ffff9d4b12e04000 R08: 000000006283ef28 R09: ffffffff8a083c14
Jun 24 10:33:50 inspiron kernel: R10: 000000000000023d R11: 00000000000151f0 R12: ffff9d4b12d9f000
Jun 24 10:33:50 inspiron kernel: R13: ffff9d4b12dc82b0 R14: ffff9d4b12dc8000 R15: ffff9d4b12d99000
Jun 24 10:33:50 inspiron kernel: FS:  0000000000000000(0000) GS:ffff9d4b17000000(0000) knlGS:0000000000000000
Jun 24 10:33:50 inspiron kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 24 10:33:50 inspiron kernel: CR2: 00005638fefeaac0 CR3: 000000022c80e005 CR4: 00000000001606f0
Jun 24 10:33:50 inspiron kernel: Call Trace:
Jun 24 10:33:50 inspiron kernel:  intel_atomic_commit+0x2b3/0x2f0 [i915]
Jun 24 10:33:50 inspiron kernel:  restore_fbdev_mode_atomic+0x1d3/0x1f0 [drm_kms_helper]
Jun 24 10:33:50 inspiron kernel:  drm_fb_helper_restore_fbdev_mode_unlocked+0x49/0xa0 [drm_kms_helper]
Jun 24 10:33:50 inspiron kernel:  drm_fb_helper_set_par+0x2c/0x50 [drm_kms_helper]
Jun 24 10:33:50 inspiron kernel:  intel_fbdev_set_par+0x16/0x50 [i915]
Jun 24 10:33:50 inspiron kernel:  fbcon_init+0x4bd/0x600
Jun 24 10:33:50 inspiron kernel:  visual_init+0xce/0x130
Jun 24 10:33:50 inspiron kernel:  do_bind_con_driver+0x1b8/0x2b0
Jun 24 10:33:50 inspiron kernel:  do_take_over_console+0x115/0x180
Jun 24 10:33:50 inspiron kernel:  do_fbcon_takeover+0x58/0xb0
Jun 24 10:33:50 inspiron kernel:  notifier_call_chain+0x4c/0x70
Jun 24 10:33:50 inspiron kernel:  blocking_notifier_call_chain+0x48/0x60
Jun 24 10:33:50 inspiron kernel:  register_framebuffer+0x20e/0x320
Jun 24 10:33:50 inspiron kernel:  __drm_fb_helper_initial_config_and_unlock+0x2ee/0x430 [drm_kms_helper]
Jun 24 10:33:50 inspiron kernel:  intel_fbdev_initial_config+0x14/0x30 [i915]
Jun 24 10:33:50 inspiron kernel:  async_run_entry_fn+0x37/0x140
Jun 24 10:33:50 inspiron kernel:  process_one_work+0x1d1/0x3e0
Jun 24 10:33:50 inspiron kernel:  worker_thread+0x4a/0x3d0
Jun 24 10:33:50 inspiron kernel:  kthread+0xfb/0x130
Jun 24 10:33:50 inspiron kernel:  ? process_one_work+0x3e0/0x3e0
Jun 24 10:33:50 inspiron kernel:  ? kthread_park+0x90/0x90
Jun 24 10:33:50 inspiron kernel:  ret_from_fork+0x35/0x40
Jun 24 10:33:50 inspiron kernel: ---[ end trace ce5c81a5d9ee94fa ]---

=> https://lkml.org/lkml/2019/6/24/627 ?

jimmy00784 · 2019-06-24 20:30:03

@seth that exception gets logged with Linux LTS boot as well.

seth · 2019-06-24 21:03:33

Cut out sddm - can you boot the multi-user.target and "startx xterm"?

jimmy00784 · 2019-06-24 22:27:35

@seth when I disabled sddm and booted into 5.1.14 and launched entrance display manager (from Enlightenment), I got the graphical environment that allowed me to login using my credentials. Then I was in a graphical session (Plasma Desktop) for a few seconds when the screen went black again.

seth · 2019-06-25 03:03:16

That's not what I asked, but still heavily suggests the issue is w/ sddm and/or plasma/qtquick and or your config thereof, maybe the kwin compositor in case of your GUI session.
Do you still see the mouse cursor when this happens?
Can you revive the output by suspending the compositor (SHIFT+Alt+F12)?

jimmy00784 · 2019-06-25 16:52:25

@seth I do see the mouse pointer for a second before it disappears into the black.
I tried switching from sddm to lxdm and from default plasma desktop to gnome shell and still same behavior with 5.1.14.
Boot up messages on console, with desktop manager trying to load - I see mouse pointer with a black background - only to have the pointer disappear the very next second.

Regarding

Cut out sddm - can you boot the multi-user.target and "startx xterm"?

Systemd gave me the error message stating I couldn't start multi-user.target independently

systemctl start multi-user.target

Is there a different command I must use for that?

Also

startx xterm

results in another error. My guess is because of the prior error with multi-user.target

2ManyDogs · 2019-06-25 17:54:13

jimmy00784 wrote:

Cut out sddm - can you boot the multi-user.target and "startx xterm"?
Systemd gave me the error message stating I couldn't start multi-user.target independently
systemctl start multi-user.target
Is there a different command I must use for that?

https://wiki.archlinux.org/index.php/Sy … _boot_into

jimmy00784 · 2019-06-25 19:04:30

@seth Thanks for the hint about multi-user.target
Do you want me to run startx xterm directly from the terminal or is there another way it needs to be run?

Running starx term results in this error:

X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux inspiron 4.19.55-2-lts #1 SMP Mon Jun 24 10:31:58 UTC 2019 x86_64
Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux-lts.img root=PARTUUID=ddab5397-8841-41c2-b630-7b314788f9de rw
Build Date: 30 May 2019 06:44:40PM
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/karim/.local/share/xorg/Xorg.0.log", Time: Tue Jun 25 13:58:15 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
> Internal error: Could not resolve keysym XF86MonBrightnessCycle
> Internal error: Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
xterm: Explicit shell already was /usr/bin/xterm
xterm: bad command line option "xterm"
usage: xterm [-/+132] [-C] [-Sccn] [-T string] [-/+ah] [-/+ai] [-/+aw]
[-b number] [-baudrate rate] [-/+bc] [-bcf milliseconds]
[-bcn milliseconds] [-bd color] [-/+bdc] [-bg color] [-bw number] [-/+cb]
[-cc classrange] [-/+cjk_width] [-class string] [-/+cm] [-/+cn] [-cr color]
[-/+cu] [-/+dc] [-display displayname] [-e command args ...] [-fa pattern]
[-fb fontname] [-/+fbb] [-/+fbx] [-fd pattern] [-fg color] [-fi fontname]
[-fn fontname] [-fs size] [-/+fullscreen] [-fw fontname] [-fwb fontname]
[-fx fontname] [%geom] [#geom] [-geometry geom] [-help] [-/+hm] [-/+hold]
[-iconic] [-/+ie] [-/+im] [-into windowId] [-/+itc] [-/+j] [-/+k8]
[-kt keyboardtype] [-/+l] [-/+lc] [-lcc path] [-leftbar] [-lf filename]
[-/+ls] [-/+maximized] [-/+mb] [-mc milliseconds] [-/+mesg] [-/+mk_width]
[-ms color] [-n string] [-name string] [-nb number] [-/+nul] [-/+pc]
[-/+pob] [-report-charclass] [-report-colors] [-report-fonts] [-rightbar]
[-/+rv] [-/+rvc] [-/+rw] [-/+s] [-/+samename] [-/+sb] [-selbg color]
[-selfg color] [-/+sf] [-sh number] [-/+si] [-/+sk] [-sl number] [-/+sm]
[-/+sp] [-/+t] [-ti termid] [-title string] [-tm string] [-tn name] [-/+u8]
[-/+uc] [-/+ulc] [-/+ulit] [-/+ut] [-/+vb] [-version] [-/+wc] [-/+wf]
[-xrm resourcestring] [-ziconbeep percent]
Type xterm -help for a full description.
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

seth · 2019-06-25 19:19:23

The hint came from 2ManyDogs
See https://wiki.archlinux.org/index.php/Xinit#xinitrc, create a usable ~/.xinitrc and run just "startx"

Also please use "code" tags for commands, output and text contents, not "quote" tags. Thanks.

jimmy00784 · 2019-06-25 19:36:23

@seth
I was able to run the xterm via the .xinitrc + startx
I used the default xinitrc file

cp /etc/X11/xinit/xinitrc ~/.xinitrc

I observe the same behavior as I do with launching display managers manually from terminal. Under 5.1.14, startx starts the graphical session and I see twm load with mouse pointer function and keyboard working and then in a couple seconds the screen goes black.

seth · 2019-06-25 19:58:41

1st step: purge xf86-video-intel (you'll be using the modesetting driver, but make sure no intel config is lingering in /{etc,usr/share}/X11/xorg.conf.d )

jimmy00784 · 2019-06-25 20:41:18

Same behavior with modesetting driver as well.
I confirmed the driver was loading in the Xorg logs

[    86.540] (II) LoadModule: "modesetting"
[    86.540] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    86.541] (II) Module modesetting: vendor="X.Org Foundation"

jimmy00784 · 2019-06-25 21:21:59

Upgrading to Linux Kernel 5.1.15 seems to fix the issue.
I stumbled upon an earlier kernel regression with 5.0 that resulted in a similar issue that was fixed in 5.0.8.
https://bugs.freedesktop.org/show_bug.cgi?id=110193
Something else must have broken since.
I'll leave linux-lts installed as a backup for now and see how long 5.1.x lasts before I run into another issue with the display.
Thanks for all the help.

Arch Linux

#1 2019-06-23 22:10:42

Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#2 2019-06-23 23:27:27

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#3 2019-06-24 15:46:28

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#4 2019-06-24 20:18:30

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#5 2019-06-24 20:30:03

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#6 2019-06-24 21:03:33

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#7 2019-06-24 22:27:35

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#8 2019-06-25 03:03:16

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#9 2019-06-25 16:52:25

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#10 2019-06-25 17:54:13

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#11 2019-06-25 19:04:30

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#12 2019-06-25 19:19:23

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#13 2019-06-25 19:36:23

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#14 2019-06-25 19:58:41

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#15 2019-06-25 20:41:18

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

#16 2019-06-25 21:21:59

Re: Black screen when X starts with kernel 5.X - LTS kernel 4.19 works

Board footer