[18.04] [Bionic]drm_kms_helper causes long delay at boot

[Scott Testerman]

System upgraded from 16.04 to 18.04 experiences long delays at boot -- generally 4-5 minutes. The same system experienced no significant delays prior to the upgrade. dmesg reports problems with drm_kms_helper.

Description: Ubuntu 18.04 LTS
Release: 18.04
linux-generic:
  Installed: 4.15.0.20.23
  Candidate: 4.15.0.20.23
  Version table:
 *** 4.15.0.20.23 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Expected to happen:
System boots in reasonable amount of time, consistent with prior LTS release.

What happened:
System is very slow to boot, on the order of several minutes to reach a login screen.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.20.23
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gdm 1012 F.... pulseaudio
                      scott 2346 F.... pulseaudio
Date: Sat May 5 23:19:14 2018
HibernationDevice: RESUME=UUID=a816bb7e-ab3e-49ea-9bbe-0f1d0e016b0e
InstallationDate: Installed on 2017-09-05 (242 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 0769AK8
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=a3217eb0-fa66-4420-9eb3-5f3a38cb1af0 ro splash vt.handoff=1
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 68ET37WW
dmi.board.name: IEL10
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd07/29/2008:svnLENOVO:pn0769AK8:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Lenovo
dmi.product.name: 0769AK8
dmi.product.version: 3000 N200
dmi.sys.vendor: LENOVO
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-09-05 (245 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: bionic
Uname: Linux 4.17.0-041700rc4-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-09-05 (245 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: bionic
Uname: Linux 4.8.0-040800-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-09-05 (245 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: bionic
Uname: Linux 4.7.10-040710-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4

[Scott Testerman (scott-testerman)]

apport information

[Scott Testerman (scott-testerman)]

With mainline kernel 4.17rc4, flip_done is still timing out, so it's exactly the same behavior as the 18.04LTS kernel.

[Scott Testerman (scott-testerman)]

apport information

[Scott Testerman (scott-testerman)]

The problem first appeared in kernel 4.8.0. It is worth noting that the boot delays are not particularly excessive with this kernel version, but increase with each subsequent version to the point of several minutes delay using 4.15.0.20.23 (18.04LTS default kernel).

[Scott Testerman (scott-testerman)]

apport information

[Scott Testerman (scott-testerman)]

Kernel 4.7.10 is the most recent kernel that boots successfully, without delays.

[penalvch (penalvch)]

Scott Testerman, the next step is to fully commit bisect from kernel 4.7.10 to 4.8 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]