10s delay after grub, before kernel messages start

Bug #1882159 reported by bughit on 2020-06-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

- fresh install of 20.04 X64 in a vmware vm
- "quiet splash" kernel args have been removed
- the kernel messages should start immediately after grub menu selection
- but there's a 10s delay

grub config
```
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
```

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: me 912 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 4 20:34:38 2020
InstallationDate: Installed on 2020-06-03 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IwConfig:
 lo no wireless extensions.

 ens32 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:

Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=606fed4f-11b6-4349-803e-69c555177718 ro
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-33-generic N/A
 linux-backports-modules-5.4.0-33-generic N/A
 linux-firmware 1.187
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

bughit (bughit) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
You-Sheng Yang (vicamo) wrote :

Please try booting with "initcall_debug earlycon=efifb" and see if kernel starts printing without that delay. Note this would usually slow done the boot process quite a lot, and I'm not sure if it actually works on a VMware virtual machine.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
You-Sheng Yang (vicamo) wrote :

The second way: please insert one line "debug=all" in the grub boot entry before "linux ....". This would turn on grub debug messages. So if it's still printing, it's not under linux kernel's control yet. Please clarify the origin of the delay first.

bughit (bughit) wrote :

Please be specific about what you want me to modify.

> try booting with "initcall_debug earlycon=efifb"

GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug earlycon=efifb" ?

> please insert one line "debug=all" in the grub boot entry

?

bughit (bughit) wrote :

the pause is during grub output, attaching two captured frames, pause start and resume

bughit (bughit) wrote :
bughit (bughit) wrote :

> Please clarify the origin of the delay first.

I've done that, why is this still Incomplete?

Francis Ginther (fginther) wrote :

Moved to grub2 as the submitter indicates the 10s delay occurs while grub is still outputing debug messages (see #6 and #7).

affects: linux (Ubuntu) → grub2 (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
bughit (bughit) wrote :

I submitted the info that was requested, so this should not be incomplete, nor expire

Changed in grub2 (Ubuntu):
status: Expired → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers