[Bug 106933] New: [CHV] On Dell 5855 boot process stuck for three-five minutes on Plymouth->Xorg hand off since Linux 4.17.0rc2
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Jun 16 12:19:58 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106933
Bug ID: 106933
Summary: [CHV] On Dell 5855 boot process stuck for three-five
minutes on Plymouth->Xorg hand off since Linux
4.17.0rc2
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: russianneuromancer at ya.ru
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 140178
--> https://bugs.freedesktop.org/attachment.cgi?id=140178&action=edit
debug dmesg
Hello!
With Linux 4.17.0rc2 - Linux 4.17.1 boot process always stuck for three-five
minutes at the stage when gdm3 is ready to start Xorg (cursor appear on the
screen, Plymouth splash disappear, Gnome Shell desktop loads).
With Linux drm-tip (cod/tip/drm-tip/2018-06-16,
02d8db1a894b0e646b2debd64ce24b8e99fd2ffd) couple of times system started
normally, but after that I getting same behaviour as with Linux 4.17.0rc2 -
Linux 4.17.1.
systemd-analyze:
Startup finished in 7.524s (firmware) + 8.012s (loader) + 7.960s (kernel) +
4min 11.905s (userspace) = 4min 35.403s
graphical.target reached after 4min 9.959s in userspace
systemd-analyze blame:
4min 4.390s plymouth-quit-wait.service
2.406s NetworkManager-wait-online.service
1.510s plymouth-start.service
1.351s systemd-journal-flush.service
1.325s dev-mmcblk0p2.device
822ms networkd-dispatcher.service
719ms udisks2.service
debug dmesg is attached
Hardware:
Dell Venue 8 Pro tablet with Intel Atom x5-Z8500,
Integrated display is connected via DSI.
Software:
Ubuntu 18.04 with Linux 4.18.0rc2 and newer.
Boot with both of Intel DDX and modesettingd DDX was tested.
X.org Server 1.19.6, Mesa 18.0.0rc5, libdrm 2.4.91
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180616/fca2df9c/attachment.html>
More information about the intel-gfx-bugs
mailing list